Strange .NET Runtime 2.0 error thrown in a WPF application

  • Thread starter Thread starter voutmaster
  • Start date Start date
V

voutmaster

Has anyone seen a similar exception? This is a WPF application
installed via ClickOnce and we have one user who gets it consistently
on startup. We've also seen it occasionally while the applicaiton is
running. We've instrumented the application with exception handling in
most methods we have control over, but due to the nature of a WPF
application startup wiring (or our lack of knowledge), we haven't been
able to implement a 'catch all' handler, so we have no idea where this
is coming from.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 10/4/2007
Time: 6:23:32 AM
User: N/A
Description:
EventType clr20r3, P1 ivory portal.exe, P2 1.0.2832.29459, P3
47043226, P4 presentationframework, P5 3.0.0.0, P6 45398c20, P7 6496,
P8 be, P9 system.windows.markup.xamlparse, P10 NIL.
 
Hello (e-mail address removed),
Has anyone seen a similar exception? This is a WPF application
installed via ClickOnce and we have one user who gets it consistently
on startup. We've also seen it occasionally while the applicaiton is
running. We've instrumented the application with exception handling in
most methods we have control over, but due to the nature of a WPF
application startup wiring (or our lack of knowledge), we haven't been
able to implement a 'catch all' handler, so we have no idea where this
is coming from.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 10/4/2007
Time: 6:23:32 AM
User: N/A
Description:
EventType clr20r3, P1 ivory portal.exe, P2 1.0.2832.29459, P3
47043226, P4 presentationframework, P5 3.0.0.0, P6 45398c20, P7 6496,
P8 be, P9 system.windows.markup.xamlparse, P10 NIL.

You should be able to wire into the
 
Hello (e-mail address removed),
Has anyone seen a similar exception? This is a WPF application
installed via ClickOnce and we have one user who gets it consistently
on startup. We've also seen it occasionally while the applicaiton is
running. We've instrumented the application with exception handling in
most methods we have control over, but due to the nature of a WPF
application startup wiring (or our lack of knowledge), we haven't been
able to implement a 'catch all' handler, so we have no idea where this
is coming from.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 10/4/2007
Time: 6:23:32 AM
User: N/A
Description:
EventType clr20r3, P1 ivory portal.exe, P2 1.0.2832.29459, P3
47043226, P4 presentationframework, P5 3.0.0.0, P6 45398c20, P7 6496,
P8 be, P9 system.windows.markup.xamlparse, P10 NIL.

You should be able to wire into the Application.ThreadException event
http://msdn2.microsoft.com/en-us/library/system.windows.forms.application.threadexception.aspx

That would probably give you almost all exceptions with a nice stacktrace.
 
Are you using some ink?
maybe missining an ink SDK?
I have the same problem, but I needed a SDK for tablet PC 2005
 
Back
Top