Compare Two DLL's

views:

answers:

+1 Q:

Compare Two DLL's

Scenario

I have a C# application compiled as a DLL. I have a build from last week and a build from this week. There has been a significant change in performance so I want to compare the the two builds to see what has changed.

ANY IDEAS?........SUGGESTIONS?

Cheers

EDIT:

Yes it would be better to compare the source code from version control........except we are using TFS, not by choice, and even with the bolton application TFS takes source control to a whole new level of shite........it's very difficult to revert without messing around with workspaces etc....i just thought the DLL approach would be easier...The application is a monster as well......

+3 A:

I would recommend to disassemble two libraries with the Reflector (right click on the assembly -> Export) and then compare directories generated with some merging tool, like WinMerge.

Regent 2010-05-14 08:49:18

+2 A:

Wouldn't it be better to profile the two dll? You will find where in the second one you are spending more time than in the first. This should give you an indication of what has gone wrong.

Francesco 2010-05-14 08:54:06

It may be that the changes that are making the application slower are necessary; by profiling you will be able to keep the functionality in these changes whilst also optimising the code to remove the cause of the poor performance. The profiler is built into Visual Studio--in 2008, it lives on the Analyze menu.

ShellShock 2010-05-14 09:12:00

Yes that's exactly my point. If there are no regressions in the test suite the changes have been introduced for some reason, so profiling seems the way to go.

Francesco 2010-05-14 09:29:51

ansaurus

tags:

views:

answers:

Compare Two DLL's

Scenario

ANY IDEAS?........SUGGESTIONS?

EDIT:

related questions