Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I occasionally use fuslogvw to track down problems loading assemblies. After all my time of using it, it seems that the folder ‘NativeImage’ has results for loading native images of my dlls. When the native image is not found (usually its not), I think it then looks for a .net assembly. The ‘default’ folder is what I normally care about, because it has logs for all assembly bindings, which is where my problem typically lies.
Can anyone explain the real difference here?
The native images are the JIT-compiled versions of the DLLs. If they are not present, the non-JIT-ted versions are located and used.
This article explains native images in more detail and how to use them with fuslogvw.