SmartAssembly - 6.0
Learning SmartAssembly - 6.0
Strong name key signing
Signing your assembly with a strong name key protects the assembly's name, and prevents modification of the assembly.
To use strong name key signing, in the Project Settings window, go to Strong Name Signing or click the icon in the toolbar. |
|
When strong name signing is enabled and set correctly, the colored bar under the toolbar icon and to the left of the feature options are green. If it is disabled, the bars are orange. If the bars are red, there is a problem with the settings and you should check them.
Note: You cannot use strong name key signing if you need to modify the assembly with another tool after SmartAssembly.
Assigning a strong name key to your assembly
To assign a strong name key, select I want to sign my assembly with a strong name. You can choose whether to create a new key or browse for an existing key.
It is recommended that you sign the assembly with the same strong name key in both SmartAssembly and Visual Studio. You must use the same strong name key if you are protecting a WPF assembly or if you want to be able to change dependent DLLs later.
Adding tamper protection
In SmartAssembly Professional and Developer editions, you can enable additional integrity checks to provide enhanced protection. To do this, select I want to add tamper protection. Enabling tamper protection makes your assembly slightly slower to load. We highly recommend that you also enable strings encoding if you enable tamper protection; see Encoding strings.
Note that you cannot use tamper protection with assemblies using .NET 1.1, any version of Compact Framework, Silverlight, Windows Phone 7 XNA, Xbox XNA, or Windows Phone 7.
Troubleshooting strong name key signing
If you have a non-signed dependency (a dependency without a strong name) and the main assembly is signed, the CLR may refuse to load the dependency. This is done for security reasons. For this reason:
- if you wrote the DLL, you need to sign it too.
- if it is a third-party DLL, you need to request a signed version of the DLL.
Was this article helpful?
System requirements
Working with projects
Setting project options
Optimizing and protecting code
Strong name key signingMerging dependenciesEmbedding dependenciesSearching for dependenciesPruning codeObfuscating codeUsing control flow obfuscationProtecting several assemblies without merging themHiding external callsCompressing and encryptingEncoding stringsAdding incorrect metadataPreventing disassembly of the ILOther optimizations
Error reportingFeature usage reportingUsing custom attributes
Configuring SmartAssemblyBuilding assemblies with SmartAssemblyAcknowledgements
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
