Thursday, December 30, 2010

4 Most Important EXE files used in DotNet FrameWork

CLRVer.exe

.Net Framework SDK includes it. This utility can show which CLR versions installed on a machine & which version of clr is being used by processes currently running on the manchine by using -all switch. anothe switch is process id.

AL.exe

AssemblyLinker.exe. Used to link the assemblies(multiple assemblies into single assemble). grouping the modules in assembly.

NGen.exe

Its the tool that ships with the .NET Framework SDK. This tool compiles all of an assembly’s IL code into native code and saves the resulting native code to a file on disk. At runtime, when an assembly is loaded, the CLR automatically checks to see whether a precompiled version of the assembly also exists, and if it does, the CLR loads the precompiled code so that no compilation is required at runtime. But the navtive code produced by NGen.exe is not higly optimized as JIT Compiler produced code. The NGen'd files can get out of sysnc because the characteristics of the Ngen'd files depend on
CLR Version, CPU type, Windows OS Version, Assembly's identity module version ID (MVID - This changes when recompiling), Referenced Assemblys versionIDs, Security (SkipVerification , declarative link-time declarative inheritance.)

PEVerify.exe

It examines all of an assembly’s methods and notifies you of any methods that contain unsafe code. You may want to consider running PEVerify.exe on assemblies that you are referencing; this will let you know if there may be  roblems running your application via the intranet or Internet.

Whenever I get chance I’ll try to write a separate blog for each tool with examples listed above.

1 comment:

  1. Thanks Naveen for sharing the knowledge!! Keep up the good work!!!

    ReplyDelete