function OpenWin(url, w, h) { if(!w) w = 400; if(!h) h = 300; window.open(url, "_new", "width=" + w + ",height=" + h + ",menubar=no,toobar=no,scrollbars=yes", true); } function Print() { window.focus(); if(window.print) { window.print(); window.setTimeout('window.close();',5000); } }
| Team-Fly | |
 | Special Edition Using Microsoft® Visual Basic® .NET
By Brian Siler, Jeff Spotts
| | Table of Contents | | | Appendix A. Packaging Your Applications |
| Once you have configured the setup project, you will need to build it in order to create its primary output, a Windows Installer package. Building the project is a simple matter. Follow these steps: -
Right-click the setup project in the Solution Explorer window; then select Properties from the Context menu. In the (projectname) Property Pages window, select the target configuration. If you are still testing, leave the configuration set to Active (Debug). Once you are through testing and ready to create your production setup package, change the configuration to Release. You can also change the output filename here if you like. Click OK to close the Property Pages window when you are happy with the configuration. -
Again, right-click the setup project in the Solution Explorer window, and then select Build from the context menu. The setup project will be compiled and built, and the output .MSI file will be generated. This process may take several minutes. Tip If the main project has changed since the last time it was built, be sure to rebuild it before building the setup package so that the most recent version of your application is deployed. -
After the build process is complete, the final output the MSI installer package is created and stored in either the Debug or Release folder under the Setup Project's folder, depending on whether you selected Debug or Release as the project's configuration in step 1 previously.
|
| | Team-Fly | |
|
| |
|
