This Redgate app looks really awesome. It takes your dot net executables and rewrites them to capture a stack trace, locals, and environmental info, when your app crashes.
-Josh
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
This Redgate app looks really awesome. It takes your dot net executables and rewrites them to capture a stack trace, locals, and environmental info, when your app crashes.
-Josh
What't the difference with a memory dump?
@ZippyV: I think the idea is that they give you a much more streamlined way to collect and transmit diagnostic information. Plus, they inject all of the necessary code straight into your assembly after you've already compiled it. Obviously, a properly coded app will have all that stuff built in already, but sometimes you inherit an old app. Or maybe you want to go back and fix up something you wrote in a less enlightened age. Either way, you can add crash reports without even having to break out the project files.
I asked a friend of mine who uses SmartAssembly, and he says it's pretty cool for some things, but that the automated reporting might not be flexible enough for some people if you want to collect anything besides what they give you out of the box.
Used smart assembly for a long time, whist they were a separate company.
Unfortunately they have now been swallowed by the Red Gate aquisition-not-innovation system, and the price has typically spiralled.
Also take a look at Automatic Exception Reporting functionality from Crypto Obfuscator. It is similar to SmatAssembly, is quite flexible and reasonably priced.
Missed opportunity to call it SmartAss if you ask me.
Add your 2¢