M.A. Hanin
2013-05-21 07:13:51
When a static constructor throws an exception, it is wrapped inside a TypeInitializationException. You need to check the exception object's InnerException property to see the actual exception.
In a staging / production environment (where you don't have Visual Studio installed), you'll need to either:
- Trace/Log the exception and its InnerException (recursively): Add an event handler to the
AppDomain.UnhandledExceptionevent, and put your logging/tracing code there. UseSystem.Diagnostics.Debug.WriteLinefor tracing, or a logger (log4net, ETW). DbgView (a Sysinternals tool) can be used to view the Debug.WriteLine trace. - Use a production debugger (such as WinDbg or NTSD) to diagnose the exception.
- Use Visual Studio's Remote Debugging to diagnose the exception (enabling you to debug the code on the target computer from your own development computer).
Thanks, this put me on the right path. I have implemented my own exception logging, but I wasnt logging the InnerExceptions correctly.
Hey! man, this is because of lack of Capability .... If you see the Inner Exception you will see this message "Access is denied. Access to speech functionality requires ID_CAP_SPEECH_RECOGNITION to be defined in the manifest." So to get rid of this exception. turn on the capability for Speech Recognition as mentioned.