SmartAssembly
Latest version: 6.7
Learning SmartAssembly - 5.5
This copy of [Program Name] has expired and will no longer run / This feature requires that {smartassembly} is available on this computer.
Date: 9/8/2010
Product: SmartAssembly
Description of problem
A program that you are trying to run displays one of the following error messages:
- This copy of [Program Name] has expired and will no longer run.
This is because it was created using a version of Red Gate's SmartAssembly which is only licensed for testing software.
You should report this problem to the vendor who supplied [Program Name] - This application has been built with an evaluation version of SmartAssembly, and therefore cannot be distributed. You can install SmartAssembly on this computer to be able to run this application.
This application will now quit. - This feature requires that {smartassembly} is available on this computer.
Explanation
Red Gate's SmartAssembly is a product which software developers can use when making their programs ready for release. If you see any of the messages above, the author of the program you are trying to use originally made that program using an evaluation edition of SmartAssembly.
The evaluation edition of SmartAssembly does not allow software developers to distribute their programs, so programs made with the evaluation edition of SmartAssembly will not work on other computers.
Programs made with the evaluation edition of SmartAssembly will also stop working after one week.
Solution
Please contact the vendor who sold the program to you, or contact the developer of the program, giving them the address of this page. They may not see the error if they only tested the program on computers that had SmartAssembly installed.
We regret that Red Gate Software Ltd. cannot assist you directly with this error.
More information for developers
SmartAssembly does not allow you to distribute assemblies built using the evaluation edition of SmartAssembly. If you have a valid SmartAssembly team edition licence, note that you cannot distribute assemblies built with a developer edition; you must use the copy of SmartAssembly installed on your build server. To solve this problem, create a new build of your assembly with an appropriately-licensed copy of SmartAssembly and distribute it to your customers as a patch release.
To avoid this problem in the future, please test your build on a computer that does not have SmartAssembly installed, before distributing it.
The three error messages are displayed in the following circumstances:
- This copy of [Program Name] has expired and will no longer run. - The assembly was built more than 15 days ago, using an evaluation or developer edition of SmartAssembly 5+.
- This application has been built with an evaluation version of SmartAssembly, and cannot be distributed. - The assembly was built between 1 and 15 days ago, using an evaluation or developer edition of SmartAssembly 5+.
- This feature requires that {smartassembly} is available on this computer. - The assembly was built using an evaluation edition of {smartassembly} 4.2 or earlier.
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