SmartAssembly - 6.2
Learning SmartAssembly - 6.2
Setting up error reporting
To enable error reporting:
|
|

When error reporting is enabled, the colored bar under the toolbar icon and to the left of the feature options is green. If it is disabled, the bar is orange.
Because error reporting captures fields and local variables, sensitive information may be included in error reports. To avoid this, use the [DoNotCapture] and [DoNotCaptureVariables] attributes. For more information, see Using custom attributes.
Note that you cannot use error reporting for assemblies using any version of Compact Framework or Xbox XNA.
Standard template
Templates define both the look of the dialog box displayed to your user in the event of an exception, and the information included in the error report. SmartAssembly provides three standard templates for error reporting:
If you want the user to have control over whether an error message is sent, select Send error dialog box. This allows the user to decide whether to send an error report or to debug the problem themselves. You can also choose the language that the message is displayed in.
If you want to let users provide their email address when they choose to send an error report, select Dialog box + email address collection.
If you do not want the user to have control over whether a message is sent, but instead you want the message to be generated and sent automatically, select Automatic (without dialog box). Use Automatic (without dialog box) to report errors in applications that do not have a user interface, for example services and web applications.
Custom template (SmartAssembly Developer and Professional only)
You can customize the dialog box shown to your customers by using a custom error reporting template. For details on creating a custom template, see Error reporting with the SDK.
To select the custom template that you have created, on the project settings window in SmartAssembly, click Browse for Template.
Custom web server (SmartAssembly Developer and Professional only)
You can choose to send error reports to your own server rather than the default server operated by Red Gate Software. For details on how to set up a custom web server, see Setting up the custom web server for reporting.
Was this article helpful?
SmartAssembly
- Using Smartassembly to obfuscate a windows service
- Obfuscation not renaming identically-named methods in different classes
- Serialization exceptions occurring in obfuscated assemblies
- SmartAssembly skipping obfuscation of some classes in your assembly
- SmartAssembly is not merging or embedding all assembly dependencies
- Can I customize the path to the MDB database?
- System.InvalidOperationException when attempting to connect to local SmartAssembly database
- Protecting website code using SmartAssembly
- Visual Studio Deployment Projects including unprotected builds
- SmartAssembly MSBUILD tasks failing because of difference in log4net assembly
- SmartAssembly Error Reporting: This application has submitted too many reports
- The assembly is being merged, but the dependent assembly isn't
- ERR 2002: Server did not recognize the value of HTTP Header SOAPAction
- The error report is not associated with a valid project ID - SmartAssembly
- Application built with an evaluation edition of SmartAssembly
- How end users can change their participation in Feature Usage Reporting
- Log file for SmartAssembly
- Moving SmartAssembly to another computer
- 'Using JET databases is not possible in 64-bit applications' error when using MSBuild or TFS
- SmartAssembly stack trace is invalid when Method Parent Obfuscation is enabled
- Upgrading SmartAssembly version 4.x to version 5
- Upgrading SmartAssembly Standard to Professional
- Problems building WPF applications with SmartAssembly 6.7
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SmartAssembly
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs


Using SmartAssembly for obfuscation