Alternatives to SmartAssembly for exception handling and reporting?

问题

I was happy with the SmartAssembly solution for exception handling, but I reported an issue on Red Gate forum and is not being solved yet.

What alternatives exists to SA? I mean with similar features (hosting your reports, sending you e-malis, etc)?

回答1:

SmartAssembly has two main features - obfuscation and error reporting.

If you are using obfuscation, there are several free and commercial alternatives. The list linked to by TrueWill shows a good selection.

For exception handling, the only similar thing that comes to mind is Exceptioneer. A benefit it has over SmartAssembly is that there is a free version available in addition to a paid-for version.

回答2:

Disclaimer: I work for PreEmptive Soltutions, the makers of Dotfuscator and Runtime Intelligence.

Dotfuscator also has the ability to report on exceptions within your application. In addition, with Runtime Intelligence you can inject additional code into your applications so that you can also gather data on how users are using your application and which features they use (and don't use).

Dotfuscator is also a very powerful obfuscator and can even obfuscate XAML and BAML in your WPF, SilverLight and WP7 applications.

You can get a free evaluation from the PreEmptive website.

回答3:

The latest version of Crypto Obfuscator supports automatic exception handling. It has a ready to use exception reporting service which you can host on your own server. The exception reports contain a lot information including values of all local variables as well as method arguments for all methods in the stack trace, system info, etc.

DISCLAIMER: I work for LogicNP, the developers of Crypto Obfuscator.

回答4:

There is also Exceptionless. They have a free plan for 1 project & 1 user.

回答5:

There are several obfuscators out there, but you can roll your own exception handler. Note that the method can vary based on the type of application.

Your exception handler can send an email, call a web service (arguably a more reliable choice), log locally, save the stack trace, or whatever you want.