![]() This entry determines the default install folder for your product. A default icon is set based on your installer type, but you can select any standard Windows. ![]() This is the icon that will be shown in Add/Remove Programs. While a Windows Application will always be installed in a subfolder of Program Files, selecting Script Application or PowerShell Module will select default folders in the user data folders on the target machine if “Install for all users” is not selected. The selection of Script Application, Windows Application, or PowerShell Module affects the default icon and template selection when building the MSI file. ![]() This field cannot be empty if is used in the path specifier. This entry is also used to resolve the part of the default path name. This string will also show up in Add/Remove Programs, as shown below. If you maintain a version number here, please keep in mind that while a major version increase usually resets the minor part (e.g., 3.8 –> 4.0), the maintenance and build portion generally do not reset-so 3.8.167 would update to 4.0.168. So 2.5.6.1 and 2.5.6.17 would be considered identical and the same product version. While version resources for executables allow and support a 4-element number () Windows installer does not evaluate the ‘build’ portion. Any increases need not be sequential you can go from 2.6.309 to 2.7.312 without any problem. You should never decrease that version number. Assuming you already do this for the main executable, providing the path to that file here is your best option. In order for updates to your product to work properly, your version must increase for each release. There are several things to consider here. ![]() ![]() This can be a number (e.g., 2.4.6.7) or the name of a file-typically your product’s main executable file-which contains a version resource. The Product Name will also be used later to substitute in the path specifier. Windows will show the Product Name as an Add/Remove Programs entry. There are reasonable defaults in place for a number of fields, and some you should not change unless there is a very specific reason.Īlright, let’s get to it and take a closer look at these fields: This first article in our step-by-step guide for the SAPIEN MSI Builder walks you through the initial settings you need for every Windows Installer you will create. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |