c# - Determine the orginal build location / path of an exe using .Net Reflector or another tool -


I have an EXE which is currently deployed on our production server (C #. 2). I inherited the task of making some changes and re-deploying this app.

I have not written this app and I have been pointing to different network drives with some different visual studio solutions (~ 10) on some different folders, through which time this app There were various impeditions and to be the claimant of the Visual Studio Project which was used to generate this exe, but I do not know which project was used which was in production EXE Matches.

Is there a way to use it correctly or another tool when determining the original file path when they were used to compile EXE I can work backwards to determine the correct visual studio solution and to make changes there.

Thank you

This situation looks like a hell if you know it Can not believe what is the origin of what is going on in production.

However, one possible solution is to look at the debug header of the .exe assembly, if it is compiled with debug compression, OLL, this could be the original path of PDB, which shows you That is where it has been built. You can get it from the Dumpbin tool, which is part of Windows SDK.

Here is an example of output:

  debug directories time type size RVA pointer -------- ----------- --- -------- -------- 4AFAA 94CV510006672C649cc format: RSDS, {77468AA8-8494-46AC-87DF-422721517504}, 8 , C: \ source \ mcs \ class \ Mono.Cecil \ obj \ Debug \ Mono.Cecil.pdb  

Better yet, if you have PDBs easier, You can use to find out which files were used to compile the assembly.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -