![]() NET Framework and why did it work in earlier versions of. You can get all the answers to these questions from comments I already made You say loading libraries this way is not valid, but why does it work in. NET Core 3.0 (preview) and it fails to load basically any interesting assembly from the framework, but it can load the application assembly just fine (since that is a pure-IL assembly).Īnother consideration: Loading from a file or stream won't work, this assembly is special and it is always loaded first and only one version of it can be loaded ever. So it's likely that you're calling the method on native image assembly, which won't work as mentioned above. So it's a single file and it lives in the framework (there's no native assembly cache, or GAC for that matter). ![]() NET Core, most framework assemblies are native image assemblies which also contain the IL for the assembly. NET Framework the code worked because you were giving it the pure-IL assemblies. The file in the framework folder (or GAC) is the pure-IL assembly. ni.dll) which typically lives in native assembly cache. NET Framework the native image assembly is a separate file (. In fact there's no way in the runtime (that I know of) to load native image assemblies from memory - the file format relies on the OS loader to perform relocations, which can't be triggered on a block of memory. NET Framework (4.2.* I assume).Īssembly.Load(byte) doesn't support loading native image assemblies (in.
0 Comments
Leave a Reply. |