SmartAssembly - 6.2
Learning SmartAssembly - 6.2
About map files
When a user sends an error report for an obfuscated program, the objects and methods in the error report are obfuscated. This means that the error report would be unintelligible without first being de-obfuscated.
SmartAssembly uses map files to convert obfuscated information within an error report back to meaningful names. SmartAssembly also uses map files to record information about the assembly which is used when displaying error reports, for example line numbers.
Managing map files
In order to avoid useless map files taking up disc-space unnecessarily, map files are automatically deleted 180 days after the last report relating to the associated assembly was received. SmartAssembly assumes it was a test build and is no longer used.
If the build will be released to end-users, you need to specify that SmartAssembly should not to delete the map file.
To mark the build as 'released', click the Mark as Released button after building the assembly. If you need to mark a build as released after building it (within 180 days of the last error report), use the following command on the command line:
SmartAssembly.com /markasreleased YourAssembly.exe
If you set up SmartAssembly to use a SQL Server database, the map files are stored in the folder you specified when you first set up SmartAssembly.
Moving map files
You can change where map files are saved. This may be useful if you are decommissioning the storage medium where the map files are currently stored, for example, and you need to move the map files.
If more than one user uses SmartAssembly
- Open SQL Server Management Studio or equivalent
- Connect to the database server which contains the error reports
- Right-click on the SmartAssembly database and click New Query
- Type the following line into the new query window:
SELECT * FROM dbo.Information - In the results, note the value stored in the MapFolderNetworkPath column
- Create a new query as follows:
UPDATE dbo.InformationSET MapFolderNetworkPath = '\\NEWPATH\Folder'WHERE MapFolderNetworkPath = '\\OLDPATH\Folder'
replacing \\OLDPATH\Folder with the value you noted in step 5 and replacing \\NEWPATH\Folder with the new location for map files.
If only one user uses SmartAssembly
To move your development environment to a new computer, see Moving SmartAssembly to another computer.
If you want to change the path where the Maps files are stored, change the LocalPath attribute value for the <Maps> node in the config file:
<SmartAssembly.Settings>
<Options>
...
<Maps LocalPath="c:\PathToSmartAssembly\Maps\" />
...
</Options>
</SmartAssembly.Settings>
(If the <Maps> node also has a NetworkPath attribute, ignore it as this is no longer used.)
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
Using SmartAssembly for error reporting