Software Deployment

From the Wise Help File.

Wise for Windows Installer

About Wise Tables
Wise tables hold lists of certain items you’ve added in Wise for Windows Installer. These tables are included in a Wise project (.WSI) file only; they are not included in the resulting .MSI file.

WARNING:

Editing Wise tables is not recommended unless you are an experienced Windows Installer developer with a clear understanding of Windows Installer database technology. Editing Wise tables might result in unexpected, undesirable results, including damage to your installation.

These are the tables and what they contain:

· WiseAdvertising. Holds the advertising information you select in the Compiler Options section of the Component Details dialog.

· WiseComPlusApp. Holds a list of MTS/COM+ application that you’ve added to the installation.

· WiseComPlusComponent. Stores information relating to MTS/COM+ applications that you’ve added to the installation.

· WiseFeatureCondition. Holds a list of the conditions you have added to features on the Installation Expert’s Features page.

· WiseLangString. Holds all strings for all languages currently defined in your installation.

· WiseLanguage. Holds a list of all languages defined for your installation, along with the corresponding releases.

· WiseMediaOptions. Is somewhat of a catchall; holds a list of values for development environment display purposes.

· WiseModuleConfiguration. Holds the information that the configurable merge modules uses during the merge process.

· WiseModuleSignature. Holds a list of those merge modules you add to your installation project file.

· WisePathVariable. Stores paths you’ve defined using the Path Variables page in Installation Expert.

· WiseRelease. Holds a list of all releases in the current installation.

· WiseReleaseExclude. Holds a list of all features and components you’ve deselected for a particular release.

· WiseReleaseMedia. Holds a list of all media for each release.

· WiseReleaseMediaDest. Holds a list of all destination directories for each media within each release.

· WiseReleaseMediaInclude. Holds a list of all features and components included in a particular media.

· WiseReleaseOverride. Holds a list of those properties and summary items you’ve overridden for a specific release on the Release Settings page.

· WiseSequence. Holds the remarks used in MSI Script as well as any empty If/End If blocks.

· WiseSourcePath. Holds a list of all source paths for all files you’ve added to the current installation.

· WiseStreamFiles. Holds a list of all source path names for custom actions and graphics you’ve added to the current installation.

· WiseWildcard. Holds a list of entries for each time you add a wildcard on the Installation Expert’s Files page and mark the Update installation as files are added or removed from source directory checkbox.

· WiseWildcardFile. Holds a list of files that were originally added via a wildcard, and were later deleted because they no longer exist. File information is stored so that if and when the files are re-added, crucial information is retained about the file.

Note:

Remember that the Wise tables only show those items you’ve added in Wise for Windows Installer.

Also see Tables Tab.



© 2002, 2003 Wise Solutions, Inc. All rights reserved.


Regards,

thx for the text, but what are there for?
Do you keep the entries in the table?

Regards

Olivier

Once you've compiled the project, they're not part of the MSI. I think you're just creating more work (and possible headache) for yourself by deleting them manually.

Their purpose is so that you can add, delete or update files from the source directories before compiling the MSI.

hi

ok, so I can update a file on my source computer and it will recompile we the newest version of the file?

Exactly. You can do entire directories, or whatever. Let's say App1 comes out with a service pack. You could expand the directories into your Wise Source directory and recompile rather than running setup capture all over again (of course this assumes that the files don't introduce any new problems, are correctly registered, etc. by the MSI and it would need to be tested for functionality).