Is this feasible? How can you do it? It should air something similar to a jar file for java applications. In addition, you do not have to agonize about not there dlls when your application is deployed.Usually, if all the functionality of your circulated application is not required at previously, you might dearth to consider having the application not speaking into break away modules or libraries. It would be nice to take them all together as a particular assembly. The .NET runtime will fill each section only at what time a type is referenced. If you have a .net application through about 10 assemblies. On the back up hand, packaging the whole thing into a solo file command bring piece improvements, mostly as the loader does not have to win the time to resolve all the enslavement issues. NOTE: The connected assemblies will not be obfuscated. It allows put together your application effectually. Linking provides closing advantages for your .NET endeavor by increasing reliability and security time reducing range. The Skater's special Linker interface is the effectiveness that can association multiple modules keen on a single box file for deployment. It does the linkage after thats your main assembly has been obfuscated. By and large, if all the functionality of your distributed application is not obligatory at once, you power want to bear in mind having the application divided keen on separate modules or libraries. The Linker interface on purpose for linking manifold managed executables or assemblies into a unattached module or assembly. The assigned referenced and non-referenced assemblies will be related into your definitive obfuscated assembly afterwards what time obfuscation is done for your contemporary open assembly. Give pleasure to obfuscate the coupled modules before Linkage. In addition, you do not have to fret about gone astray dlls when your application is deployed.Also packaging the whole thing into a track file long for bring feat improvements, mostly as the loader does not have to work the time to resolve all the addiction issues. The .NET runtime will cargo each part only while a type is referenced. When packaging you can amalgamate assemblies using the assembly linker. Compilation merging is an acute angle of any application together with multiple assemblies. The capacity to merge multiple libraries as one would simplify deployment in a lot of cases; applications with the purpose of use several separate languages or huge applications in print in the same style but built upon lots of different projects would profit from single-assembly exploitation. When distributing some closely connected but separate DLLs is not to facilitate much of a plague, it would be a fine if, since they are so narrowly interlaced, you could merge these unique assemblies into lone. Or you may suggest safe the combined libraries as soon as Linkage.