This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Reply to a long ago post...
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 29, 2009
09:36 AM
Validation error ICE60 when using dynamic file linking
I suppose this is more of a bug report, but since it's a low priority issue I don't really feel like paying for an incident report just to report an error so I'd thought I'd just document it for the community. If anyone has any insight or suggestion on how to avoid the issue below please feel free to reply.
Problem:
We have a rather large setup project (IS 2008) with ~9000 files and ~900 components (which may be an issue in itself, but that's another matter..)
Due to the large number of files which may also change between product builds we make heavy use of dynamic file linking to create the setup package. Now, when running validation on the .Msi we recieve a large number of unexpected ICE60 warnings. Upon examining the 'File' table we discover that a number of .xml, .gif and other files have a value entered in the 'Version' column even though these file types do not have any embedded version information. The 'Language' column is empty for these files, which leads to the ICE60 warnings.
After looking at the affected files it seems there is a pattern:
When sorting the files alphabetically per component it appears that everything is fine until a DLL with version information is encountered, after that all subsequent non-versioned files gets the same version attibute as the DLL (but no language attribute).
So it seems that when using dynamic file linking the 'Version' attribute is not properly cleared between files when there is a mix of versioned and non-versioned files included in a component.
Problem:
We have a rather large setup project (IS 2008) with ~9000 files and ~900 components (which may be an issue in itself, but that's another matter..)
Due to the large number of files which may also change between product builds we make heavy use of dynamic file linking to create the setup package. Now, when running validation on the .Msi we recieve a large number of unexpected ICE60 warnings. Upon examining the 'File' table we discover that a number of .xml, .gif and other files have a value entered in the 'Version' column even though these file types do not have any embedded version information. The 'Language' column is empty for these files, which leads to the ICE60 warnings.
After looking at the affected files it seems there is a pattern:
Component FileName FileSize Version Language
--------------------------------------------------------
Comp1 File1.xml xxxxx
Comp1 File2.gif xxxxx
Comp1 File3.dll xxxxx 1.5.0.0 0
Comp1 File4.gif xxxxx 1.5.0.0
Comp1 File5.xml xxxxx 1.5.0.0
When sorting the files alphabetically per component it appears that everything is fine until a DLL with version information is encountered, after that all subsequent non-versioned files gets the same version attibute as the DLL (but no language attribute).
So it seems that when using dynamic file linking the 'Version' attribute is not properly cleared between files when there is a mix of versioned and non-versioned files included in a component.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 11, 2010
03:18 PM
Check is the 'Always Overwrite' tag is set for these files. If it is it assigns a version of 255.255.65534 to the file(s). This would cause the Validaiton to see it as a versioned file. Hence the need for the language designation.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)