PDA

View Full Version : ICE errors and selfregistering dlls



yann.bertaud
06-14-2007, 03:38 PM
All

I am working on installer for our next product version and we need it to be vista certified. OUr product uses a lot of COM, as such I am setting the dlls to self register. However, when I run the Certified for Vista validation suite on the installer, I get a lot of ICE33 errors, ie
regkey _xxxx is used in an unsuported way, Typelib should be registerd via the typelib table, this entry may overwrite a value created through that table.

My question is: is there some way to have installshield do the right thing for me when it self registers the dlls, ie put the typelib stuff in the typelib table?

we have so many COM dlls that I would hate to have to do this all by hand. Even if I do have to do this by hand, i dont know what i need to put into the table.

Any help on this would be appreciated.

MichaelU
06-14-2007, 04:01 PM
You can use the older behavior by following this KB article: http://support.installshield.com/kb/view.asp?articleid=Q113259

However be aware that we made this change because using the Typelib table is no longer recommended. See the remarks on:
http://msdn2.microsoft.com/en-us/library/aa372092.aspx

yann.bertaud
06-14-2007, 04:07 PM
You can use the older behavior by following this KB article: http://support.installshield.com/kb/view.asp?articleid=Q113259

However be aware that we made this change because using the Typelib table is no longer recommended. See the remarks on:
http://msdn2.microsoft.com/en-us/library/aa372092.aspx

I dont understand why I am getting these ICE warnings then. Shouldnt installshield be updated to reflect those best practices and not give those warnings.

yann

Christopher Painter
06-14-2007, 07:32 PM
InstallShield didn't write ICE33, Microsoft did. Besides, just because Microsoft changes their mind on what the `best practice` is doesn't mean they actually get around to updating their ICE's. After all it's taken them 7 months just to publish 2 KB articles. All Microsoft can do is get the word from the Windows Installer team and then attempt to improve their tool regardless of what ICE33 complains about.

Then there is the question of WHICH Microsoft best practices to follow.... the ones coming from the Windows Installer team or the ones coming from Rob Mensching and all of his buddies.

Either way, some time spent on my blog listening to my cynical rants might be enlightening.... :)