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.
Cheers
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......
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.
This is a free option to compare .Net C # assembly: Assembly Diff Tool for .NET - JustAssembly
Today the same can be done with JetBrains dotPeek. Load the dll right mouse button -> export to project and compare in WinMerge
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.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With