Databases
StackOverflow2013
Postsdbo
POIdentify / Remove differences in identically build .NET exe's
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIdentify / Remove differences in identically build .NET exe's
    primarykey
    data
    text
    <p>I am back trying to compare two .exe's, this time with some changes.</p> <ul> <li>Building project in Microsoft Visual Studio 2010</li> <li>Project target framework = .NET Framework 3.5 Client Profile</li> </ul> <p>I build the project, run <code>dumpbin /rawdata</code> on the .exe and output to a text file. Next I re-build the project and run <code>dumpbin /rawdata</code> on the new .exe and output to a new text file. I then CRC each one to make sure they are the same (no changes are made between builds).</p> <p>I am getting different CRC values. When I run the raw data through <code>windiff</code> I am seeing differences in the <code>Raw Data #1</code> section, which I believe is actual data generated from the source code of the project (please correct if I'm wrong).</p> <p>There are 3 areas of difference in <code>Raw Data #1</code>, one of which includes a .pdb.</p> <p>Questions:</p> <ol> <li>Does anyone know where I can turn off debugging information in VS 2010 (similar to <code>Project Property Pages -&gt; Config Properties -&gt; Linker -&gt; Debugging -&gt; Generate Debug Info</code> in VS 2005)</li> <li>Are there any tricks to finding out where the highlighted differences in WINDIFF actually exist in the source code?</li> </ol> <p>Thank you, ZayJay</p> <p>PS - feel free to ask for clarifications, and thanks a ton again. I've searched for a while with little success. So glad I found this resource.</p> <p><strong>EDIT / UPDATE</strong> My shift has now turned to compiling the code with ngen to bypass MSIL and whatever was showing up as differences there. One of the differences was in this area: <code>&lt;PrivateImplementationDetails&gt;{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}.Dictionary</code>... and I cannot make anything from the ascii in the other difference (I got rid of the .pdb info).</p> <p><em>I would like to know if there is a way to view / extract the compiled code for viewing.</em> </p> <p>I've tried <code>ngen display "App Name"</code> and searching in <code>WINDOWS/assembly</code> but cannot find anything relevant (also, i do not know 100% what I am looking for either...)</p> <p>Thanks for your time, ZayJay</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJeffrey Hantin
    1. USZayJay
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIdentify / Remove differences in identically build .NET exe's
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThere are timestamps in the assemblies I think, that might account for the differences.
      singulars
      1. POIdentify / Remove differences in identically build .NET exe's
      1. USLasse Vågsæther Karlsen
    2. COThanks, do you know if there are multiple timestamps though? Because I'm getting 3 areas of difference in what I'd expect to be identical .exe's (one of which looks like it involves a .pdb from the ascii). Or any way to turn timestamps off via project settings?
      singulars
      1. POIdentify / Remove differences in identically build .NET exe's
      1. USZayJay
    3. COVague memories of there being multiple ones, yes, but since they're vague, they could be wrong. I could also be totally wrong about there being timestamps in the first place. Have you verified that the changes are in the same place and are of the same size every time?
      singulars
      1. POIdentify / Remove differences in identically build .NET exe's
      1. USLasse Vågsæther Karlsen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload