It appears that Cecil 0.9.6.1 from NuGet breaks Windows .NET DLL consistency with a simple NOP-roundtrip:
string clrAssembly= "helloWorld.dll"; AssemblyDefinition l = AssemblyDefinition.ReadAssembly(clrAssembly); l.Write(clrAssembly); If you try loading helloworld.dll into NUnit before the roundtrip, everything works OK, and you get a message about how it is not linked with a framework. if you try loading helloworld.dll into NUnit afterthe roundtrip, you get a FileLoadException, sometime regarding the hash, sometimes modules not in the manifest. The xUnit runner displays the same issues also. I would speculate the way reflection loads DLLs is more stringent than the normal loader, and this is why this has not been seen before. -- -- -- mono-cecil --- You received this message because you are subscribed to the Google Groups "mono-cecil" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
