ICE60 error/warning bug during InstallAware build process

[HAHNmediaservice]

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 ...

[mills]

Is this producing an error or a warning?

[HAHNmediaservice]

It's a warning and yes, only errors threaten logo certification, not warnings. But we want to get rid of the ICE60 warnings as well. We still think the InstallAware’s build process is inaccurate (it's a bug, isn't it?), so please help on that, but don’t advise changing the MSI file table manually ...

[mills]

As I see it, yes.

[HAHNmediaservice]

We need help soon. How long will it take to fix it?

[HAHNmediaservice]

What about this post? Do we get an answer on that issue?

[mills]

You asked not to be told the answer.

[norbertjurkiewicz]

I see as of IA2012 the generated .msi files are still causing the ICE60 Warnings. Is there any information on a way to get rid of these? without manual interverntion

[FrancescoT]

Dear User,

Certain ICE warnings are unavoidable because of the way the MSIcode scripting magic works in InstallAware. We have not investigated this warning in detail, but ICE warnings are completely safe to ignore and they do not jeopardize the result of any logo certification test, and they are absolutely inconsequential with respect to runtime setup reliability.
We cannot attest to whether the ICE 60 warning here is something that can theoretically be eliminated, but there are those which cannot theoretically be eliminated without sacrificing InstallAware's MSIcode scripting magic, and therefore we do NOT make a priority of researching such issues, as they are really without any real effect whatsoever and in some cases unavoidable.

Hopr this helps you.

Regards