Now you would like to make changes to one of the assemblies and provide it as an update.Ī naive re-execution of Dotfuscator upon your application would likely rename your legacy classes and methods in a different way, forcing you to redistribute the entire application to your customers.ĭotfuscator's incremental obfuscation allows you to keep the same names so you can release the changed assembly. Incremental obfuscation allows you to keep a consistent naming scheme across Dotfuscator runs for your application.īy referencing a name mapping file, types and members can be consistently renamed over time.Ĭonsistent renaming is desirable in multiple scenarios, including the redistribution of a subset of files that constitute a dependent group, and sequential obfuscation of assemblies in a resource constrained environment.Īppropriate utilization of this feature offers the additional benefit of more rapid obfuscation, when only some of the assemblies in an application need to be redistributed.Ĭonsider a scenario where you have used Dotfuscator on your application and distributed that application to your customers. Therefore, linking of applications with any XAML should generally be avoided.

Linking is not supported in Automatic Input Management mode.ĭotfuscator does not update the assembly name in Pack URIs in XAML. Linking is not supported for Managed C++ assemblies. If you have other input assemblies that reference the assemblies you are linking together, Dotfuscator will transparently update all the assembly and type references so the output assemblies will correctly work together. The linking feature is fully integrated with the rest of Dotfuscator, so in one step, you can obfuscate, remove unused types, methods, and fields, and link the result into one assembly. The only rule is that you can't link the same input assembly into multiple output assemblies.

Explicitly Specifying the Tool Locationsĭotfuscator can combine multiple input assemblies into one or more output assemblies.Īssembly linking can be used to make your application even smaller, especially when used with Renaming and Removal, and can simplify deployment scenarios.įor example, if you have input assemblies A, B, C, D, and E, you can link assemblies A, B, and C and name the result F.Īt the same time, you can also link D and E and name the result G.

Fully sign a dll file