SmartAssembly - 5.5
Learning SmartAssembly - 5.5
Merging dependencies
Dependencies merging integrates the code of a dependency with the code of the main assembly. After merging, the dependency is inseparable from the main assembly.
You can obfuscate and prune the code from a merged dependency in the same way as code in the main assembly.
Using dependencies merging
|
To use merging, in the project settings window, either scroll to the Dependencies Merging feature settings pane or, on the toolbar, click the dependencies merging icon. |
Select the dependencies to merge. To refresh the list, click Rescan dependencies.
If you select a dependency, which itself has dependencies that are within the list, these are automatically selected.
When dependencies merging is enabled, the colored bars under the toolbar icon and to the left of the features options are green. The colored bars for dependency embedding also turn green when you enable dependencies embedding because merging is preferred over embedding. If merging is disabled, the bars are orange.
Merging example
The following example shows code before and after merging DLL1 and DLL2 into MainExe:
Before merging:
DLL1:
internal class InvalidDocumentContentsException : Exception
public sealed class DiscoveryDocument);
DLL2:
internal class InvalidDocumentContentsException : Exception
internal class LinkGrep
MainExe:
public sealed class DiscoveryClientResult
internal struct CallId
After merging:
MainExe:
public sealed class DiscoveryClientResult
internal struct CallId
internal class InvalidDocumentContentsException : Exception
internal sealed class DiscoveryDocument
internal class InvalidDocumentContentsException : Exception
internal class LinkGrep
What is the difference between merging and embedding?
Merging
When you merge a dependency with the main assembly, the code from the two assemblies are merged into a single assembly. The resulting assembly does not contain a reference to the dependency. Calls are no longer public (by name) but internal (by member ID), which provides greater protection and is quicker.
You can protect a merged dependency by obfuscating the whole assembly in the normal way.
Embedding
With embedding, the dependency is compressed is then stored in the main assembly. At runtime, the first time the DLL is needed, it is decompressed and an assembly is created and loaded into memory. The embedded assembly keeps its identity and its integrity. If you embed a dependency, the main assembly is not modified.
To protect the dependency, first protect it in a separate SmartAssembly project and then embed the obfuscated DLL.
Troubleshooting merging
Third-party DLLs
You may not be able to merge a third-party DLL. In some cases, the DLL has integrity protection and will fail to load if the code is changed, which happens when the dependency is merged with the main EXE. If this happens, embed the dependency instead of merging it (see Embedding dependencies).
Complex merging
Merging may fail if your application has a complex architecture and you have not merged all dependencies together. A typical example of when merging may cause your application to fail is when you are using a plug-in, as in the case below:
Assume that both MainExe.exe and plugin.dll reference shared.dll, and also that MainExe.exe loads plugin.dll by reflection.
If you merge shared.dll into MainExe.exe, MainExe.exe and plugin.dll will not be able to communicate using types from shared.dll. This is because the fully-qualified names of those types will have changed from "shared, MyNamespace.MyType" to "MainExe, MyNamespace.MyType".
The solution is to embed plugin.dll instead of merging it (see Embedding dependencies).
For projects where dependency embedding is not supported (.NET 1.x, .NET Compact Framework, XNA), you must keep the dependency separate and distribute the DLL with your application.
See also |
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
Error reporting