Menu
How does the Developer command prompt for Visual studio 2012 search the location of ildasm.exe. Running command window Developer command prompt for Visual studio 2012 will point to location C:\Program Files (x86)\Microsoft visual studio 11.0 but at this location ildasm.exe couldn't be found. In fact input to command window, ildasm.exe will open the ildasm tool.
Can any one clarify how does Developer command prompt for Visual studio 2012 locate the physical ildasm.exe.
499
It will find ildasm.exe in i.e. c:\Program Files (x86)\Microsoft SDKs\Windows\v8. 0A\bin\NETFX 4.0 Tools\ .
To use the GUI, type ildasm at the command line without supplying the PEfilename argument or any options. From the File menu, you can navigate to the PE file that you want to load into Ildasm.exe. To save the metadata and disassembled code displayed for the selected PE, select the Dump command from the File menu.
To display the contents of an assembly using Ildasm.exe, enter ildasm <assembly name> at a command prompt. For example, the following command disassembles the Hello.exe assembly. To view assembly manifest information, double-click the Manifest icon in the MSIL Disassembler window.
Ildasm.exe shows only metadata descriptions for .obj and .lib input files. IL code for these file types is not disassembled. You can run Ildasm.exe over an.exe or .dll file to determine whether the file is managed.
Ildasm.exe takes a portable executable (PE) file that contains intermediate language (IL) code and creates a text file suitable as input to Ilasm.exe. This tool is automatically installed with Visual Studio. To run the tool, use Visual Studio Developer Command Prompt or Visual Studio Developer PowerShell.
It does not operate on files installed in the global assembly cache. The text file produced by Ildasm.exe can be used as input to the IL Assembler ( Ilasm.exe ). This is useful, for example, when compiling code in a programming language that does not support all the runtime metadata attributes.
This is useful, for example, when compiling code in a programming language that does not support all the runtime metadata attributes. After compiling the code and running its output through Ildasm.exe, the resulting IL text file can be hand-edited to add the missing attributes.
When you start Developer command prompt for Visual studio 2012 the command (it is a bat script) modifies environment PATH (and other things that does not matter in this case).
You can see the difference when you type set in Developer command prompt for Visual studio 2012 and in classic cmd.
When you open Developer command prompt for Visual studio 2012 it is true that you land in C:\Program Files (x86)\Microsoft visual studio 11.0 but thanks to the modified PATH variable windows will look in every directory mentioned by this variable.
It will find ildasm.exe in i.e. c:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\.
115
please check following section. I am using VS 2013 & 2015.
If you want to use them from Visual Studio Directly. You can try following URL
Launch ildasm tool from inside visual studio itself how
25
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
