KNOWN ISSUE: File versions not populated when using Wildcards and Path Variables
|Article:TECH28881|||||Created: 2007-04-18|||||Updated: 2007-05-03|||||Article URL http://www.symantec.com/docs/TECH28881|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
When using Wildcards and Path Variables, versions are not being populated for files added after the initial scan. This only occurs for wildcards whose source directory is a subdirectory of a Path Variable. Steps to reproduce:
- Create c:\test\test2 and add one versioned file to this directory.
- Create a new .wsi.
- Go to the Path Variables page and add a Path variable with the value c:\test.
- On the Files page browse to c:\test\test2 in the upper left pane.
- Click Add Contents.
- Mark Update installation as files are added or removed from source directory. Click OK. The file is added and has a version.
- Compile the .wsi.
- In Windows Explorer a second versioned file to c:\test\test2.
- Compile the .wsi. The new versioned file is added but the version field in the File table is empty. Compiling multiple times does not populate the version information.
Wise for Windows Installer 6.2
Wise Installation Studio 7
Wise Package Studio 7.x
At some point when the new versioned file was added, the file was added to the Hash table. This caused the file version not to be populated on subsequent compiles.
This does not happen if a versioned file changes. It only occurs if new versioned files are added. Once this occurs, perform the following so that the version is scanned next time you compile:
- Go to the Files page.
- Double-click on the file whose version is not populated.
- On the General tab, unmark the Add to Hash Table option.
|Description||Logged in Littlebuggy (Altiris - Lindon, Plymouth) database|
Article URL http://www.symantec.com/docs/TECH28881