Hi Bob,
The idea here was to avoid ICE33 warnings and if I create the registry keys
by using registry/registry values/tags I believe they would cause ICE33
warnings.
Another thing I noticed was having used TypeLib, Class, AppId and ProgId
tags, the resulting MSI do not have ProgId, Class tables. Is there any flag
I need to set to cause these tables to be created?Am I missing something
here? ICE33 warnings are still reported after having used these tags?
What would be your inputs on this?
-aparna
On 11/30/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
aparna wrote:
I unable to create the following keys with the above code:
"
*Software\Classes\AppId\Cxyz.exe" Name="AppID" Value="{GUID}"
Type="string"*
*Software\Classes\TypeLib\{Guid}\1.0\HELPDIR - with it's path being blank*
*Software\Classes\AppId\{Guid}" Name="RunAs" Value="NT
AUTHORITY\LOCALSERVICE" Type="string"*
"
It doesn't appear that WiX supports those values. You can write them
manually with RegistryKey/RegistryValue elements but please submit a feature
request so we can evaluate them. If you can provide links to docs that
describe those values as valid, it would be helpful.
--
sig://boBhttp://bobs.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
