It’s been a while since I blogged. It’s good to be back.
I switched job descriptions and became an application architect, which means, I get to decide how solutions are designed…and if the solutions won’t work, the blame goes on me :-p
Now seriously, I was reviewing old posts and realized WordPress didn’t make a good job at keeping my old code snippets from Blogger :(, the formatting is way off and you can hardly see the code properly. Oh well.
Today we had a deployment issue, one of our projects was compiled to the wrong target framework. When we compared properties and sizes we realized this was not the ordinary dll size, but how could we determine the actual target framework?
The windows explorer properties or the IIS properties are of no use in this case, giving you only the build number.
There are actually two main options with two utilities distributed on the SDK to determine the target framework of a dll or exe:
- ILDASM.exe
- CorFlags.exe
and if you want to use CorFlags.exe:
Happy coding 🙂
L.
I’m not able to find either of these exe in the specified path.
Any clue?
The utilities mentioned on this article are installed as part of Visual Studio.
https://docs.microsoft.com/en-us/dotnet/framework/tools/ildasm-exe-il-disassembler
The tools mentioned can be also used by installing the Visual Studio Developer Command Prompt from the Marketplace. https://marketplace.visualstudio.com/items?itemName=ShemeerNS.VisualStudioCommandPromptdevCmd
Thanks.
Quite funny how, I refer the same page again after over a year.
Not often, do I work in Dll components and here I am.
Regards,
Gautaman
For those who doesn’t have the space or license to install Visual Studio.
Microsoft SDK can be installed to use the required tools.
For those who doesn’t have the space or license to install Visual Studio.
Microsoft SDK can be installed to use the required toools.
C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools
I might’ve been silly not to include the path.