PDA

View Full Version : ICE33 validation errors caused by COM extract at build?



alastair.camero
04-13-2002, 09:08 AM
I'm using validation for the very first time.

I see a lot of ICE33 warnings. They are caused by COM extraction (we have a large number of COM components) importing entries in to the registry table, when in fact Windows Installer would prefer these entries to go in to the AppID/Class/ProgID table.

Two questions:

1. Can I ignore these errors.

2. Can InstallShield make their COM extraction more intelligent by attempting to import entries to the other tables instead of the registry table? or is this being unfair...?

Thanks.

Alastair

gbaroni
04-15-2002, 06:45 AM
Up.
I have same problem.
Is it sufficient to delete "CLSID" registry entry of component, from ide ?
What's to do, for avoid this warning ?

gbaroni
04-16-2002, 01:53 AM
I have discovered that (in my case) this warning is show when the property of registry value is marked as "Install if Absent / Unistall if present (*)"; if I switch back to default "Automatic", this warning is gone. I was changed default, to try if resolve the upgrade bug (delete registry key of first installation !).
I hope help you and/or developer support.