ICE60 error/warning bug during InstallAware build process
Posted: Wed Sep 08, 2010 9:16 am
We suppose that ICE60 errors (from ICE Checks integrated in InstallAware or validation within ORCA) may be a bug during InstallAware MSI file table creation. For general explanation:
ICE60 posts a warning or an error if a file in the MSI file that is not a font and has a version, does not have a language.
Let’s say we have an .NET assembly (DLL) with a version number and set the language property to "neutral" (for example AssemblyInfo.vb with <Assembly: NeutralResourcesLanguageAttribute("")>). This assembly should be correct in respect to ICE validation.
Now let’s come to the MSI file table. For this property ("neutral") the correct value inserted in the language column should be 0 (siro), but InstallAware's build process puts NULL (nothing) in here. This always results in an error during ICE validation!
We think the InstallAware’s build process is somehow inaccurate ... please help on that, but don’t advise changing the MSI file table manually ...
ICE60 posts a warning or an error if a file in the MSI file that is not a font and has a version, does not have a language.
Let’s say we have an .NET assembly (DLL) with a version number and set the language property to "neutral" (for example AssemblyInfo.vb with <Assembly: NeutralResourcesLanguageAttribute("")>). This assembly should be correct in respect to ICE validation.
Now let’s come to the MSI file table. For this property ("neutral") the correct value inserted in the language column should be 0 (siro), but InstallAware's build process puts NULL (nothing) in here. This always results in an error during ICE validation!
We think the InstallAware’s build process is somehow inaccurate ... please help on that, but don’t advise changing the MSI file table manually ...