Needed to check if one of our servers was gobbling up RAM due to a debug DLL, so checked and found
this SO conversation about identifying debug / release builds DLLs. One of the replies mentions '.NET Assembly Information' by Rotem Bloom -
https://github.com/jozefizso/AssemblyInformation and a more recent fork at
https://github.com/tebjan/AssemblyInformation
Also a quick and dirty solution, "One way that could work for most people is to simply open the DLL/EXE file with Notepad, and look for a path, for example search for "C:\" and you might find a path such as "C:\Source\myapp\obj\x64\Release\myapp.pdb", the "Release" shows that the build was done with Release configuration."
No comments:
Post a Comment