Loading CLR DAC dll from a different path- August 13, 2007 From .Net framework 2.0, CLR creates a debugger helper dll mscordacwks.dll. The dll is used by Windows Debugger to enumerate CLR data structures. Mscordacwks.dll is part of .Net framework redist. C:WindowsMicrosoft.NETFrameworkv2.0.50727>dir mscordacwks.dll Volume in drive C is Vista Volume Serial Number is C84C-2424 Directory of C:WindowsMicrosoft.NETFrameworkv2.0.50727 07102007 04:38 PM 812,544...http://blogs.msdn.com/junfeng/archive/2007/08/13/loading-clr-dac-dll-from-a-different-path... The Unusual RefDef Mismatch FileLoadException- August 6, 2007 One of my colleagues has experienced a very strange RefDef Mismatch FileLoadException (The located assembly's manifest definition does not match the assembly reference). After a long investigation, we finally track down the cause. To explain the problem, we have to understand the sequence of assembly loading and the interaction between fusion and CLR. The key is after LoadLibrary , loader does one more check to make sure the file has not been changed between the original file mapping and.http://blogs.msdn.com/junfeng/archive/2007/08/06/the-unusual-ref-def-mismatch-fileloadexce... The sequence of interactions between CLR loader and fusion during Assembly.Load- August 6, 2007 The following describes roughly the sequence of interactions between CLR loader and fusion during Assembly.Load() in .Net framework 2.0. 1. User calls Assembly.Load. 2. Loader pass the assembly reference to fusion. 3. Fusion checks to see if the assembly has already loaded. If it is, the assembly is returned. 4. If not, fusion probes the assembly as described in MSDN. If fusion cannot find the assembly, it returns a failure. 5. If fusion finds an assembly, it asks loader to crack the metadata.http://blogs.msdn.com/junfeng/archive/2007/08/06/the-sequence-of-interactions-between-clr-... |