Let. NET programs run out of the. NET Framework Framework

Net framework is now gradually becoming popular, there are still many people looking for how to let. NET program out of the. NET Framework. Off-the-shelf tools include Xenocode postbuidle or Vas, and Salamander. NET Linker.

There is also the Maxtocode author's previous framework linker. And some packaging tools Molebox,thinstall that support registry emulation and file emulation. Finally there is a user to sell a method of implementation.

Xenocode uses a virtual machine environment to simulate the registry information and file information required by the framework. Xenocode's so-called generation native code function actually refers to this function. I tested several programs for packaging, and compatibility doesn't seem to be very good. I don't know if it's because the frame is already installed on the machine.

Jason made the framework linker, which I used before, he actually took advantage of the Remotesoft kernel file, and then realized a loader. It seems that the earlier kernel files were used, and the compatibility was not very good.

Salamander. Net Linker, a product of Remotesoft, is not downloadable, but its compatibility seems to be good. The mobile flying letter software took advantage of its core.

The method of a netizen seems to be to use Remotesoft's core and the frame of flying a letter, because he does not have free public method, from the example that he gives out can see to have remotesoft core document as well as the frame procedure that fly a letter.

The method to be introduced here is to use the framework of flying letter directly to achieve the separation from the. Net framework.

First download a letter of the program installation. There will be a vmdotnet directory in the installation directory. This is. NET Framework virtual environment needs the files.

Extract the entire catalogue directly.

How do you use this virtual environment to run your own. Net program? Very simply, a command line is done. A FetionVM.exe will be found in the Vmdotnet directory. This is the loader of the virtual environment.

How to use: FetionVM.exe pathtoyoureexe. is to pass your. NET program as a command-line parameter to FetionVM.exe to execute your. NET program in this virtual environment.

It is best to write a startup program yourself first to check if the system is installed. NET Framework, if there is direct running. No virtual environment was invoked to run.

The start of the program to fly a letter, if you do not want to write directly to the installation directory of Feition.exe, but in this case your own. NET program's name must be called FeitionFX.exe. Put it in the same directory as the Feition.exe and execute the Feition.exe directly.

In addition, if you are right. NET program uses encryption protection, need to pay attention to, currently on the market most. The encrypted assembly of the net encryption tool cannot be run in this virtual environment.

In addition to being able to run out of the. NET Framework, there is another side effect-let. NET programs run in the specified version of the. NET Framework (although the. NET Framework is installed on the machine, you can still have the. NET program run under this virtual framework).