It's all about tradeoffs. During a normal repair the Windows Installer will only check the KeyPath of a Component to determine if a Component needs to be repaired. The fewer KeyPaths you have the faster the repair goes but the fewer things that are checked to verify the Component is not broken.<unk<unkIn general, if the Resource is important and stands all by itself, I put it in its own Component.<unk<unk-----Original Message-----<unkFrom: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon W<unkSent: Wednesday, December 27, 2006 08:34<unkTo: wix-users@lists.sourceforge.net<unkSubject: [WiX-users] registry entries within multiple components or in a single component<unk<unkHi All.<unk<unkShould each registry entry be it's own component, or should it just be<unkpart of a single component from which the "keypath" is the file that<unkcontains the registy entries?<unk<unkI would like the add/remove programs repair to fix any registry<unkentries that have been altered. Is there a benefit, or downside to<unkeither approach?<unk<unkFor example,<unk<unk<Component Id="component0" DiskId="1" Guid="PUT-GUID-HERE"><unk <File Id="file0" Name="foo.exe" src="C:\tmp\foo.exe" /><unk</Component><unk<Component Id="component1" DiskId="1" Guid="PUT-GUID-HERE"><unk <Registry Id="foo.exe" Root="HKCR" Key="test"><unk <Registry Value="Company" Type="string" /><unk </Registry><unk</Component><unk<unk<unkor,<unk<unk<Component Id="component0" DiskId="1" Guid="PUT-GUID-HERE"><unk <File Id="file0" Name="foo.exe" src="C:\tmp\foo.exe" KeyPath="yes" /><unk <Registry Id="foo.exe" Root="HKCR" Key="test"><unk <Registry Value="Company" Type="string" /><unk </Registry><unk</Component><unk<unk<unkThank you,<unkJon<unk<unk-------------------------------------------------------------------------<unkTake Surveys. Earn Cash. Influence the Future of IT<unkJoin SourceFor ge.net's Techsay panel and you'll get the chance to share your<unkopinions on IT & business topics through brief surveys - and earn cash<unkhttp://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV<unk_______________________________________________<unkWiX-users mailing list<[EMAIL PROTECTED]<unkhttps://lists.sourceforge.net/lists/listinfo/wix-users<unk
------------------------------------------------------------------------- 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
