Latest version: 6.7
Learning SmartAssembly - 6.0
Moving SmartAssembly to another computer
When you move SmartAssembly to a different computer, you may need to move the license, the SmartAssembly database, and the map files. If you do not move all three components, SmartAssembly may not work correctly.
Throughout this page, the old computer is the one you are moving SmartAssembly from. The new computer is the one you are moving SmartAssembly to.
The instructions on this page assume that the old computer and the new computer are both running SmartAssembly 5 or later. The database format in SmartAssembly 4.3 and earlier was different, and so the database cannot be replaced. If you are affected by this, contact Support for guidance.
1. Before you start
Before you start, ensure that you know:
- whether SmartAssembly uses a .mdb file, or a SQL server database
- whether SmartAssembly stores map files on the old computer, or on a network share
To check both settings, on the old computer, start SmartAssembly and click Options.
2. Moving your SmartAssembly license
To move your SmartAssembly license to a different computer:
- Install SmartAssembly on the new computer.
- On the old computer, start SmartAssembly, and click Deactivate Serial Number.
- Write the serial number down somewhere.
- Click Deactivate.
- On the new computer, start SmartAssembly and, on the evaluation dialog box, click Activate.
- Enter the serial number you wrote down previously.
- Click Activate.
3. Moving your reports database
SmartAssembly uses a database to store error and feature usage reports. Some settings relating to de-obfuscation are also stored in the database, so you must move the database even if you do not use error or feature usage reports.
How to move the database depends on whether you use a .mdb, or a SQL server database.
If SmartAssembly uses a .mdb file for storing reports
- Copy the reports database from the old computer.
On Windows 7 and Vista, the database is stored in %ProgramData%\Red Gate\SmartAssembly\
In earlier versions of Windows, the database is stored in %ProgramFiles%\Red Gate\SmartAssembly 6\
- Replace the copy of the reports database on the new computer with the copy from the old computer.
If the new computer uses a different operating system than the old computer, ensure that you put the database in the correct location for the new computer's operating system.
Note: This step replaces the reports database on the new computer. If you have already built assemblies on the new computer, you will no longer be able to de-obfuscate stack traces, or to read error reports from assemblies previously built on the new computer.
If SmartAssembly uses a SQL server for storing reports
If you store reports on a SQL server, on the new computer, set the SQL server's address in the SmartAssembly Options. See Configuring reporting on multiple computers.
If you have moved the SQL server database itself, see Configuring reporting on multiple computers.
4. Moving your SmartAssembly map files
Map files are used to de-obfuscate stack traces in error reports.
How to move the map files depends on whether you store map files on the old computer, or on a separate network share.
If SmartAssembly stored map files on the old computer
- Copy all of the SmartAssembly map files from the old computer.
On Windows 7 and Vista, the map files are stored in %ProgramData%\Red Gate\SmartAssembly\Maps\ by default.
In earlier versions of Windows, the map files are stored in %ProgramFiles%\Red Gate\SmartAssembly 6\Maps\ by default.
- Put the map files into the appropriate directory on the new computer.
If the new computer uses a different operating system than the old computer, ensure that you put the map files in the correct location for the new computer's operating system.
You can change the path where map files are stored, see About map files.
If SmartAssembly stores map files on a network share
If you store map files on a network share that has not changed, you do not need to do anything. The map files path is stored on the SQL server, and is fetched when SmartAssembly connects to the database.
To change the network path where map files are stored, see About map files.
Was this article helpful?
Thanks for your feedback!
- 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
- 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
- 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