SmartAssembly - 6.0
Learning SmartAssembly - 6.0
Configuring reporting on multiple computers
Setting the reports database
To use Automated Error Reporting or Feature Usage Reporting on more than one computer, the error reports must be saved on a central database. To do this:
- In the menu bar, click Options.
- Scroll to Reports Database Options:

- Select To allow sharing of reports, I want to store data in a SQL Server database
- Click Choose...

- Enter the name of your SQL Server. If you have multiple instances of SQL Server running on the same computer, append the SQL Server instance name to the computer name, in the format computername\instancename.
Note: all computers which will be used for downloading error reports must be able to access the computer hosting the SQL Server instance. - Click OK.

Setting the map file path
If your application is obfuscated, you must also be able to access the map file, which SmartAssembly uses to de-obfuscate error reports, from all of the computers.
To set the maps folder:
- If the chosen SQL Server instance has not been used by SmartAssembly before, you are asked to supply a network path where SmartAssembly can store map files.
Note: SmartAssembly must have read and write access to this network path from all of the computers that you will use to download the error reports.

- If the chosen SQL Server instance has already been entered on another computer, the network path will be set automatically. To ensure that all computers share the same map file, it cannot be changed from within SmartAssembly. (To change the setting, see the instructions in the About map files topic.)
Note: You must set a map files location even if you only want to use feature reporting, not error reports.
Using SQL authentication
By default, SmartAssembly uses Windows authentication when connecting to the SQL server. To use SQL authentication instead, follow these steps:
- Using an XML editor, open SmartAssembly.settings. By default, this file is located in C:\ProgramData\Red Gate\SmartAssembly\ in Windows Vista and later, or C:\Program Files\Red Gate\SmartAssembly 5\ in older versions of Windows.
- Find the
<Database>node. - Check that the
DatabaseEngineattribute is set to '1' (this means that SQL server will be used for error reports, rather than a .mdb file). - Set the value of the
Serverattribute to the computer name and SQL server instance in the formatMyServer\SQLExpress. - Set the value of the
MasterConnectionStringattribute as follows. This will be used to create the error reports database.Data Source=MyServer\SQLExpress; Initial Catalog=master; UserId=[YourUserName]; Password=[YourPassword] - Set the value of the
ConnectionStringattribute as follows. This will be used for subsequent connections to the database.Data Source=MyServer\SQLExpress; Initial Catalog=smartassembly; UserId=[YourUserName]; Password=[YourPassword]
The resulting file should look like this:
<SmartAssembly.Settings>
...
<Options>
<Database DatabaseEngine="1" Server="MyServer\SQLExpress" ConnectionString="Data Source=MyServer\SQLExpress; Initial Catalog=smartassembly; User Id=[YourUserName]; Password=[YourPassword]" MasterConnectionString="Data Source=MyServer\SQLExpress; Initial Catalog=master; User Id=[YourUserName]; Password=[YourPassword]"/>
</Options>
...
</SmartAssembly.Settings>
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

Optimizing and protecting code
Configuring SmartAssembly