Show pageOld revisionsBacklinksBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. # IT:AD:Debugging # * [[../|(UP)]] {{indexmenu>.#2|nsort tsort}} * * [[IT/AD/Debugging/IntelliTrace/]] * [[IT/AD/Debugging/Remote/]] * [[IT/AD/JScript/Debugging/]] ## IIS Issues ## For trying to track down 500 issues, etc, see [[IT/AD/Infrastructure/IIS/Diagnostics/]] ## Debugging From Compiled Code ## To debug *optimized* managed apps read this: * http://bit.ly/rWcOqj * http://bit.ly/sfOFSE * http://referencesource.microsoft.com/faq.aspx * http://nuget.codeplex.com/discussions/264611 * Especially the part: > `davidebbo did a great job here summing up the possibilities. I just want to add that in .NET there are no hidden differences between Debug and Release builds - no additional optimizations are applied, only preprocessor conditionals and the Conditional attribute. The entire optimization work is done during JIT, and that can be disabled by COMPLUS_ZapDisable (which, by the way, is a really cryptic name for what it does). or with an INI file: http://blogs.msdn.com/b/jaredpar/archive/2008/08/29/disabling-jit-optimizations-while-debugging.aspx` /home/skysigal/public_html/data/pages/it/ad/debugging/home.txt Last modified: 2023/11/04 22:23by 127.0.0.1