Edit Question - KnowledgeHub

Title Body

If I NGen an assembly, is it normal that ildasm still disassembles it? Ok. I wrote a HelloWorld class library and the ensuing dll is named NGenILDasmTest.dll. --> Targeted for the .Net fw 4. From Vs 2010 command prompt, I did gacutil -i NGenILDasmTest.dll I could see the assembly installed in the GAC. And I ran ildasm so I could view the IL. So far so good. Then I run ngen NGenILDasmTest.dll (I did not specify any options for ngen). And this assembly successfully got compiled. I located it with a name NGenILDasmTest.ni.dll under the folder C:\Windows\Assembly\NativeImages_v4.0.30319_32\NGenILDasmTest\81d49dd4c7df22fb3df530402b58ffc9 Now, when I run ildasm like below ildasm "C:\Windows\Assembly\NativeImages_v4.0.30319_32\NGenILDasmTest\81d49dd4c7df22fb3df530402b58ffc9\NGenILDasmTest.ni.dll" I could see the contents of the Ngen-ed assembly. Is this normal?. Technically speaking, Ngen generates native CPU instrcutions for the IL (and apparently places it under C:\windows\Assembly\NAtiveImages_V4.#####_32 - in my case). If that is the case, how am I still able to see the NGen-ed assembly as IL using ILDasm? Please help me understand that 'little something' that I am missing here.

Tags (comma-separated) Cancel