Lock(object) and ThreadAbortException- July 30, 2007 We have experience some weird deadlock using managed code. We have a class with some shared resources. To protect the shared resources, we create a synchronization object, and use Lock(object) prior to access the shared resources. There is no nested lock so in theory we should never have deadlock. However, for some reason, one of the call has stucked in the Lock(object) call. After a round of discussion with CLR team, we finally figure out the problem. It is a debug build. (not...http://blogs.msdn.com/junfeng/archive/2007/07/30/lock-object-and-threadabortexception.aspx Don't catch all exceptions- July 25, 2007 One of the best practices on exception is don't catch all exceptions. There are many reasons why this is a best practice. For example, You want to look at the application state when the exception is thrown so that you can understand exactly why the exception is thrown. The exact state is often lost when exception is caught and application is continued. Here is another example why should not catch all the exceptions. One team found a strange deadlock when turning on fusion binding log. After a.http://blogs.msdn.com/junfeng/archive/2007/07/25/don-t-catch-all-exceptions.aspx 64 bit gacutil.exe- July 19, 2007 32 bit gacutil.exe can installuninstallenumerate 64 bit assemblies for GAC, so there is really no need for 64 bit gacutil.exe.http://blogs.msdn.com/junfeng/archive/2007/07/19/64-bit-gacutil-exe.aspx Unknown exception 0xe0434f4e- July 16, 2007 If you attach windows debugger to a .Net framework application, occasionally you may see debug spew of unknown exception 0xe0434f4e. (cfc.1244): Unknown exception - code e0434f4e (first chance) 0xe0434f4e is defined as EXCEPTION_HIJACK. (Copied from Rotor 2.0 sources corexcep.h) define EXCEPTION_HIJACK 0xe0434f4e 0xe0000000 'COM'+1 EXCEPTION_HIJACK is thrown by CLR as part of the process of suspending threads for garbage collection. It's raised to help resume...http://blogs.msdn.com/junfeng/archive/2007/07/16/unknown-exception-0xe0434f4e.aspx |