What are the challenges you face when working across database platforms? Take the survey
Options

Long lines of code

banozbanoz Posts: 2
edited August 8, 2016 12:49PM in .NET Reflector Previous Versions
There is a bug in debugging through decompiled assemblies - when the line of code is quite long, debugger steps after that code points to the line shifted forward, not actual. Seems like there is some unnecessary wrapping happens.

Comments

  • Options
    Jessica RJessica R Posts: 1,319 Rose Gold 4
    Just a quick update that this issue was resolved by disabling optimization on the assembly that was being debugged:

    1. Close Visual Studio
    2. Set an environment variable (From Advanced System Settings) named "COMPLUS_ZAPDISABLE" and give it the value 1
    3. In the folder where YourAssembly.dll is, you then need a .INI file called YourAssembly.ini that contains the text below:

    [.NET Framework Debugging Control]
    GenerateTrackingInfo=1
    AllowOptimize=0

    4. Try debugging again

    Thank you banoz for providing your reproduction!

    Jessica Ramos | Product Support Engineer | Redgate Software

    Have you visited our Help Center?


Sign In or Register to comment.