In my past life, as a developer of COBOL mainframes, I widely used a tool called Abendaid , which in case of an exception give me a complete memory dump, including a formatted list of each variable in memory, as well as a full trace of the program stack with a highlighted violation statement. This greatly simplified the cause of the error and saved a lot of step-by-step debugging and / or tracing instructions.
Now I have switched to C # and .NET web development. I find that the information provided by ASP.NET tells only half of the story, giving me a stack trace, but not any information about a variable or class. This makes debugging difficult, since you need to start the process again using the debugger in order to try to reproduce the error, and not just with intermittent errors or with assemblies that run under such SQL Server or CRM.
I looked back a lot at what was doing this, but I could not find anything obvious. Does anyone know if he is or not, what do I need to start to write?
source share