When the static constructor throws the exception, it is wrapped inside the TypeInitializationException. You need to check a exception object's InnerException property to see a actual exception.
In the staging or production environment (where you don't have the Visual Studio installed), You will need to either of the below things:
1. Trace or Log a exception and its InnerException (recursively): Add the event handler to your AppDomain.UnhandledException event, and put the logging or tracing code there. Use the System.Diagnostics.Debug.WriteLine for tracing purpose, or the logger (log4net, ETW). DbgView (the Sysinternals tool) can be used to view your Debug.WriteLine trace.
2. Use the production debugger (such as the WinDbg or NTSD) to diagnose your exception.
3. Use the Visual Studio's Remote Debugging to diagnose your exception.