Dotfuscator User's Guide
Exception Reporting

To detect exceptions that occur within a method, place ExceptionTrack attributes on the method. To detect exceptions that occur anywhere in an assembly, place ExceptionTrack attributes on the assembly.

Exceptions can be either explictly or implicitly reported.

The ExceptionTrack defines three properties for specifying an explicit ExceptionSource at runtime:

Note that assembly level ExceptionTrack attributes can not define an ExceptionSource and must use the detected exception object as defined below otherwise a build error will occur.

When Dotfuscator encounters an ExceptionTrack attribute with ExceptionSourceElement set to DefaultAction (the default) during its processing, it adds code that detects exceptions of the configured type:

An exception can be reported to the configured PreEmptive Analytics endpoint by setting the SendReport property of the ExceptionTrack attribute to true (the default).

Dotfuscator can also be configured to obtain information from the user such as a description of the actions leading to the exception and a contact address that the developer can use to solicit additional information or provide notification of an issue that has been fixed. This information will be attached to the exception report message. To obtain this type of user-provided information, specify a ReportInfoSource. For more information on configuring a ReportInfoSource, see Collecting User-specified Exception Report Information.

The sending of exception reports will honor the opt-in setting of the user if an OptInSource has been configured.

Dotfuscator can be configured to obtain explicit consent from the user to send the exception report message. In this case, the user's explicit consent will override the PreEmptive Analytics opt-in setting if one has been configured. To obtain explicit consent to send the exception report message, specify a ReportInfoSource. For more information on configuring a ReportInfoSource, see Collecting User-specified Exception Report Information.

The report info source settings are optional. If they are omitted, no user-provided information will be collected, and the sending of the exception report messages will be controlled by the PreEmptive Analytics opt-in setting.

 

 


© 2016 PreEmptive Solutions, LLC. All Rights Reserved.

www.preemptive.com