Native Image Generation

Question

0.00/5 (No votes)

See more:

Hello!

I wonder where is the binary file located after Ive compiled the .exe or .dll assembly using the ngen.exe. I have a .NET 4 assembly (in C#) and want to remove MSIL and leave the native code to bypass JIT compilation at runtime. I do this in command line compiler:

C#

ngen install myAssemblyName.exe

and it approves to have installed in native image cache but I dont know where it is. Can anyone help?

Thanks

Posted 9-Feb-12 21:36pm

Tsotne1990

Add a Solution

Comments

Sergey Alexandrovich Kryukov 10-Feb-12 3:41am

I wonder why?
--SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-02-09T21:49:00

Solution 1

As far as I understand, you never need to know that. You are not using the native image in cache directly. You will keep using the same assembly executable module file to run your application, exactly as you would do before using Native Image Generator. The generated native image will only be used during run time to prevent JIT operation through using pre-compiled native code. You may only see the difference in performance (do not expect dramatic improvements because JIT is effective enough for most applications).

You can read about other effects of using the native image:
http://msdn.microsoft.com/en-us/library/6t9t5wcf%28v=vs.100%29.aspx[^].

[EDIT #1]

Native images are typically named like "*.ni.dll", "*.ni.exe".

[EDIT #2]

This is a good in-depth Microsoft Magazine article: http://msdn.microsoft.com/en-us/magazine/cc163610.aspx[^].

—SA

Posted 9-Feb-12 21:49pm

Sergey Alexandrovich Kryukov

Updated 9-Feb-12 22:29pm

v4

Comments

Manfred Rudolf Bihy 10-Feb-12 3:59am

Moved from non-solution: Thank you for quick answer. One more please: I have read that article you pointed. I wonder if it is enough to simply install the binary into the native image cache and forget about it. Are there any references required or it automatically resolves the location of that assembly at runtime? Thanks again!

Sergey Alexandrovich Kryukov 10-Feb-12 4:18am

I remember I saw some references in MSDN just recently; when I saw your question, failed to find it quickly, sorry. I found it a while ago, so you could, too, by adding the key words ("resolve" OR "resolution"). I usually use very simple resolution which should not cause any problems, so I did not really think about the resolution problem...
--SA

Sergey Alexandrovich Kryukov 10-Feb-12 4:40am

[Misplaced -- SA]

Sergey Alexandrovich Kryukov 10-Feb-12 4:18am

If I come across this detail again, I'll notify your.
--SA

Sergey Alexandrovich Kryukov 10-Feb-12 4:21am

Yes, basically, this is correct: you should install the image and forget, but more exactly, not forget it forever. If you want to remove the application later on, you need to remove the generated native image from cache first, using ngen.exe.
--SA

Sergey Alexandrovich Kryukov 10-Feb-12 4:39am

OK, I think the problem of resolution does not exist. There is a problem if referenced assemblies and dependencies on them, and MSDN says:
"Installing an assembly also installs its dependencies, simplifying the syntax of Ngen.exe.". It looks more or less obvious to me that is the assembly resolution is successful during "normal" run, NGEN can copy with them, too.

Also, please read the important section "Assemblies and the GAC" in the article "The Performance Benefits of NGen" I referenced under [EDIT #2]. Just a clarification: GAC assemblies are resolved by the strong name which is considered world-unique.

--SA

Sergey Alexandrovich Kryukov 10-Feb-12 4:41am

I hope, at this moment the case is closed.

If you agree that it makes sense, please accept the answer formally (green button) -- thanks.
--SA

Manfred Rudolf Bihy 10-Feb-12 4:00am

5!

Sergey Alexandrovich Kryukov 10-Feb-12 4:21am

Thank you, Manfred.
--SA

Espen Harlinn 11-Feb-12 5:15am

5'ed!

Sergey Alexandrovich Kryukov 11-Feb-12 5:29am

Thank you, Espen.
--SA