Features

• The linker utility is intended for linking multiple managed modules or assemblies into a single module or assembly with only the code that is really required to execute the resulting assembly.
• The linker supports both EXE and DLL assemblies. Multiple DLLs can be linked into a single DLL, and DLLs can be linked into one EXE.
• The mini-deployment supports standard alone applications, including windows forms and console EXEs, and windows service EXEs. These EXEs can refer to .NET assemblies that are exposed as COM components.
• The linking process starts with entry point methods. By default, EXE has only one entry point, the Main() method, while for DLLs, the public methods are the entry points. An entry points can be added into the linker using the .NET Explorer interface.
• The linker removes multiple assembly and module declarations, and leaves only one declaration for the linked assembly or module.
• The linker merges assembly, module, file and type references, and eliminates references pertinent to the modules being linked.
• Automatically resolves same-name, same-signature global methods or fields in the modules being linked.
• Automatically resolves classes with identical full names in the modules being linked.
• Mixed images that contain both managed and unmanaged code can not be linked. Assemblies produced by Visual C++.NET belong to this category. Howerver, such assemblies can be still mini-deployed by leaving them as seperate files.
• Mini-deployed applications can be directly launched from CD, without any need to touch the system. Absolutely no installation - no file copying, no registry modification. A user can simply insert a CD, click the EXE to launch it; this is extremely useful for showing demo to potential customers.
• Mutiple applications can be deployed to the same directory where CLR runtime and public assemblies are shared, and thus save disk space.
• Extremely easy to use, the linker takes one or more .exe and .dll files as input, and transforms them into new format either in place or save as different file names. No configuration is required. No extra steps are involved. No third party tools are needed.
• Advanced GUI, highly integrated with Remotesoft .NET Explorer.
• Seamless integration with Microsoft Visual Studio .NET through an addin. Linking and deployment can be performed within the same IDE, and can be added into the automatic build process.
• Microsoft .NET Framework 1.1 is supported.   
• Small runtime component needs to be distributed with the mini-deployed code.