This is a standard WISE Installation Script file (to make an.msi). You will need. The icon of the project should be set in the Application's exe. Figure: Adding.
SSW's Wise Standard for Products As a part of Branding within SSW, all the product installations should have a standard layout. There is no point having one installation that has the SSW Logo and the web site if none of the others follow suit. The idea is that each product when the first installation is created should have several items filled out by the programmer working on the product. Below is a list of the current items that are required in the product installations.
Is a standard WISE Installation Script file (to make an.msi). You will need WISE for Windows Installer to open it. Note: This document has been updated to Wise 7. To see the standard on how to release a version see SSW's Wise Enterprise Standard for Products.
Installation directories To setup template for the Wise Installer for Windows:. Copy SSWWindowsApplications.msi from to you application's 'Setup' folder. This template will be used in conjunction with the Visual Build Pro script which will be used to build release packages. Now we can create new setup with the standard template Right-click the SSW.msi and choose 'Edit in Wise editor'.
Figure: Open file using the Wise editor. Go to the 'File' Menu and 'Save As.' , then choose 'Installer Projects (.wsi)' from the type combo as shown below, then name the file after your solution file's name. Figure: Save file as a wsi file. This will prevent developers from keeping a template on their local drive rather than always getting the latest template. Copy the Product Code Across This is very important if you are creating a new package for an existing product. You also need to check the codes in the package that you get from Source Safe to ensure that they're the same as the previous released version.
If you do not copy the Product Code across from the old WSI file, your new package will not be able to detect versions created with old Wise packages and will not uninstall these older versions. Copying the Product Code:.
Open the old WSI file. Select the Setup Editor. Click the Product Tab. Select Properties from the tree view. Copy the Product Code value. Paste the Product Code into your new WSI file. Repeat the process for the UpgradeCode.
Repeat the process for the PackageCode (which is found in the Summary section). Figure: The Product Code.
Include all the files needed Select 'Files' on the left hand side and browse through to the folder containing your release. Select the files you would like to add, and click 'Add File'. Make sure the directory structure in the bottom left is correct as needed on the client computer. The icon of the project should be set in the Application's exe.
Figure: Adding files to the package The following files should NOT be included:.scc;.vspscc - Source Safe Files.pdb - Debug Files.user - User settings for Visual Studio.NET IDE You can enforce these by adding those extensions to the Exclude Wildcard. Make sure that the wildcards are similar to those in the application's old msi. Figure: Using Wildcards Figure: Exclude wildcards These files will automatically be removed on uninstall because Wise keeps a link to each file that has been added above. However, if there are files that have been added to the directory after the installation process, Wise will not have the list of these files to remove. Therefore the RemoveFile operation needs to be added to the list as shown below:. In the Destination Files list, select the 'Remove file' option from the 'Operation' button.
Figure: Specifying the 'Remove File' Operation. In the dialog box, check the 'All Files' checkbox and select 'Uninstall' in the 'Remove During:' drop down list. Figure: 'Remove all files during uninstall'. Figure: The 'RemoveFile' operation is added to the file list. Change the Default Directory Once the files have been added, the directory will be available in the Directory combo boxes throughout the wise installer. Go to the 'Project Details' section from the left hand menu.
Click the 'Change' button and select the appropriate Program Files folder that the product will be installed under. Figure: Select the correct Default Directory The merge module directory must now also be set if you want to use the components than can't be packaged automatically. Go to the 'Merge Module' section from the left hand menu, click 'Add' button to add modules Figure: Add MFC component. Set the destination directory of the component to install.
Figure: Install MFC component to System32 folder. The module is added. You can double click the module to edit its properties. Figure: The MFC module is added to the installer.
Enter Add/Remove Program Information Select 'Add/Remove Programs' on the left hand side and enter information that will show up in the Add/Remove Program Control Panel for Windows 2000/XP:. Select the icon that will appear in the Add/Remove Program list. There should be an ssw.ico for SSW products. Note: You will need to add the files first before accessing the executable through the 'browse.' .
Check 'Hide modify button' if the product does not have multiple installation features. Contact Person should be the current head developer for the application. Help URL should reference product's Online User Guide Example: Figure: Add/Remove Program entry page Figure: What it will look like in Add/Remove Control Panel. Add Shortcuts Enter Shortcut setting that will appear in the Start Program Menu. Destination Directory will be suffixed with version so product version can be checked at a glance without executing the application. This will be handled by Visual Build PRO. Prefix Name of each item with a number so sorting can be controlled.
Main executable should start with 1 so it will appear at the top. Click 'Add'. Click 'Next'.
Select the main executable to be put in your installation package. Click 'Next'.
Expand the 'Programs' node and select the 'ProductName' folder, then click Ok. Change the name of the Shortcut as shown in Figure1. Select the icon. Look at the disabled 'Icon Number' and remember the icon number value. Uncheck 'Advertised' checkbox and enter the icon number value in the 'Icon Number' textbox.
Note: If you remove the file from the wise package that is associated with the shortcut, the shortcut will also be removed. Figure 1: Make sure the shortcut name is '1. ProductName' and select the icon by clicking 'New Icon' button.
Change the component reference in the Shortcut Tables. Select 'Setup Editor' on the bottom left panel. Select 'Tables' tab on the top left panel. Select the 'Shortcuts' table on the left panel list (as shown in Figure 2). Change all the 'Components' column to be the same as the Executable.
(as shown in Figure 3) Figure 2: The default way in which the 'Shortcuts' table has different references to the 'Component' key. This will not allow the Update and Uninstall shortcut to be removed from the start menu on uninstall. Figure 3: A better way of allowing shortcuts to be removed on uninstall is to have the component references the same as the shortcut of the executable file. Technical Note: (this step is not required) Destination Directory are stored in the Directory Table.
This should generally be left as it is since Visual Build PRO will update the DefaultProgramMenu directory name. This point to SSW Diagnostics website - this point to the latest version of SSW Diagnostics You should use the aspx one for redirect user to SSW Diagnostics website. Do you have a 'Systems Requirements' screen when installing a product? Installing a product should be easy and fuss free! If your product requires other programs to be installed, for example the Microsoft.NET Framework, I find it is best to include a 'Systems Requirements' screen where the user can click the links provided and install the required programs and then continue with the installation of your product. If your installation exits prematurely due to not having the required programs installed, the user can get frustrated - make life easy for them!
Figure: Installation Prerequisites Screen However, sometime it's very hard to detect the required software in user environment, eg. A database server on the network. In such cases, you should still include the required software on other screen to warn your user. At least let them know what they are going to need to run your application. Figure: Installation Prerequisites (Optional) Screen Acknowledgements - 11 Feb 2002 - 07 May 2002 - 05 May 2004 - 14 Dec 2005 - 26 Mar 2008.
Disclaimer The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind.
Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.