How to make a good. NET code generation MSI file

One:
Build a new project on the basis of the original project, and select the "Install and deploy project", especially if you choose the "Add in Solution" option, because this is the only way to put the deployment project and our own application into the same "solution", and that's important!
Two:
After clicking on the "OK" button, the Installation Wizard appears because of our. NET test program is a Web application, so select the Install Wizard. Click on "Next (N)", we will see the need to select the screen of the various items of choice to believe that we can from the Chinese name intuitive understanding, we will not waste more breath. Clicking "Next" until the final Installation Wizard completes will take 5 steps, eventually adding a setup project called "Setup1" in the current solution.
Three: After completing the above two steps, we will find that VS. NET Installation Wizard has found the various assemblies, system DLL files, resource files, and so on that we use in our applications, and we can easily continue to add additional relevant files that we need to do something similar to InstallShield, However, you do not need to write an installation script script.
In this way, we select Vs.net's menu "Generate (B)"-〉 "Build Solution" to immediately build our installation file Setup1.msi, which you can find in the directory where your application solution resides.
Find this installation file you will be surprised, even if our application only a simple word, after packaging will be 17M big! But there is no way, VS. NET generates a concise. NET SDK in the installation file that we just generated.
The rest of the matter is directly in the absence of installation. NET environment to run our WINDOWS9X/NT/2000/XP this setup1.msi file on it!
The above approach is vs.net7. Test Pass in 0beta2
If there's anything else you don't understand,
H.xue@163.net