Linking .NET Framework
Previous Top Next

dotnetlinker
clip0323


.NET Developers: Deploy .NET applications as a single EXE that runs without the .NET Framework.

Are you worried about lost sales from potential customers who can't or won't install the .NET Framework?

1. The .NET Framework adds more that 20MB to your application download. How many users are you losing because of the extra 1-3 hours of modem download time?
Thinstall creates a stand-alone application that runs without the .NET Framework in as small as 2.7MB for a simple Hello World, and ~6MB for a typical GUI application.

2. The installed size of the .NET Framework is more than 100MB. How many users will decide to uninstall your application because it takes up too much space?
Thinstall runs .NET EXEs without decompressing any files to disk, so the download size and install are exactly the same. i.e. 2.7MB versus 100MB, or 3700% less space.


3. Users are afraid of installing the .NET Framework.
Users have a short attention span, don't waste time trying to convince them they need to install 2 things to run your application.
When you have the user's attention, sell them on your application, not on why they need the .NET Framework.
Thinstall combines your program with the required portions of the .NET Framework to form a single EXE that runs without installation.
No files are extracted/installed to the hard drive, the application can be run directly from CDROM or Internet download link.


4. The .NET Framework install requires registry write access and is not possible for Guest accounts on 2k/xp.
Guest accounts are very common in large corporate and educational institutions.
Guest users cannot evaluate your software for purchase without contacting the IT department, which leads to lost sales.
Thinstall allows .NET applications to run without registry permissions on all windows Accounts.

5. The .NET Framework install fails on more than 1% of computers because the user's computer is "broken" from previous installers or viruses.
Is is not your job to trouble shoot why the .NET Framework installer isn't working!
With zero installation, Thinstall runs .NET applications on PCs with corrupted registries, missing DLLs, broken MSI, etc.


6. Your application may not be compatible with newer or older versions of .NET Framework.
Don't waste your time tracking down bugs that aren't your fault.
Thinstall links a specific version of the .NET Framework with your application, so it runs exactly the same every time.


Are you worried about lost sales from hackers removing licensing code from your .NET application?

1. Even with obfuscators applied, .NET applications can be perfectly disassembled and reassembled.
This makes it very easy for any programmer to find your license code and remove it. Once a "crack" for your application is released on the net you can stop it. Don't wait until it is too late.
Thinstall hides your .NET "byte-code" from all external disassemblers and hacking tools.


How does it work?

Thinstall first inspects your program to find all the code it uses. Next Thinstall packages these files into a single EXE utilizing patent pending Virtual Registry and Virtual Filesystem technology to relocate .NET Framework directories so all files are always loaded from your EXE package. The system version of the .NET framework is never used and it does not matter if the user has v1.0, v1.1, both or no version at all.

Thinstall's virtual registry allows .NET Framework's ActiveX controls to be visible to your application without system changes. These ActiveX controls are listed in the text file
mscoree.dll.threg.

Thinstall relocates the Global Assembly Cache and Native Images directory to reside inside your EXE package. This prevents any conflicts from external configurations. These settings are controlled in the text file fusion.dll.threg.

Compatabilitiy

· 100% compatability with all portions of .NET Framework including Reflection
· Supports all Intel platforms supported by .NET (Windows 98, ME, NT, 2k, XP, 2003, PE, XP Embedded)


How to Link the .NET Framework

1. Automatic .NET EXE detection during new project Wizard
When you use the New Project Wizard, Thinstall will automatically detect the EXE in question is .NET and ask if you would like to link the .NET Framework.
Simply select the option "Link required portions of .NET Framework directly into my EXE" and then OK.

clip0292



2. Importing .NET Framework files into an existing project

If you've already created a project and would like to import required .NET files, you can select the menu option:
Languages -> .NET -> Import required .NET

clip0294
If your .NET program uses new external Assemblies, you can use this option to automatically import any referenced assemblies.


Special Notes:

Thinstall is not able to determine assemblies or external programs that are used dynamically. For example, assemblies that are referenced explicitly through
System.Reflection.Assembly.Load

For such assemblies, you may need to manually add these Assemblies to your project by copying from c:\windows\assembly\gac