Rats on the Ids.  The way heat rolls seems to be a pretty good answer to the 
problems I've seen.

Thanks for pointing out Directory/@ComponentGuidGenerationSeed.  This seems to 
do the trick for me.


--- On Mon, 6/8/09, Brian Rogers <rogers.br...@gmail.com> wrote:

> From: Brian Rogers <rogers.br...@gmail.com>
> Subject: Re: [WiX-users] Id and Guid Questions
> To: chr...@deploymentengineering.com, "General discussion for Windows 
> Installer XML toolset." <wix-users@lists.sourceforge.net>
> Date: Monday, June 8, 2009, 3:41 PM
> Hey Chris,
>  
> > Is there a way to make it make the autogenerated
> flavor be like the way heat does it?
>  
> Short answer is no. The Ids in heat are done using a
> seed to keep them unique according to the output. Once moved
> into the Compiler/Linker level it would be a bit more tricky
> to get it 100% right to auto generate Ids (although not
> impossible).
> 
>  
> >  declare a Directory of ProgramFilesFolder with
> a DefaultDir of . and put it in the heiraachy 
>  
> Are you still following the authoring guidelines on
> this?
>  
> http://msdn.microsoft.com/en-us/library/aa367787.aspx
>  
>  For the GUID generation you could look at using 
> Directory/@ComponentGuidGenerationSeed
> at the root directory of your merge modules.
>  
> Thanks,
> 
> Brian Rogers
> "Intelligence removes complexity." - Me
> http://icumove.spaces.live.com
> 
> 
> 
> On Mon, Jun 8, 2009 at 1:22 PM,
> Christopher Painter <chr...@deploymentengineering.com>
> wrote:
> 
> 
> When I use heat, it generates dir/comp/file ID's such
> as
> 
> cmpXXXXXXXXXXXXXXXX
> dirXXXXXXXXXXXXXXXX
> 
> filXXXXXXXXXXXXXXXX
> 
> If I omit the File/@Id attribute I get a different
> transformation pattern autogenerated.   Is there a way to
> make it make the autogenerated flavor be like the way heat
> does it?
> 
> Also when I try to use autogenerated componentID/Guids in
> merge module projects I get an error message saying the file
> isn't rooted in ProgramFilesFolder.  Eventually it will
> be though since we wire all of our modules up to
> targetdir\installdir.   I found a hackish way around
> this error ( declare a Directory of ProgramFilesFolder with
> a DefaultDir of . and put it in the heiraachy )  but I was
> wondering if there is a better way here.
> 
> 
> Basically I'm trying to come up with a way of writing
> merge modules that have as much autogenerated id's and
> guids as possible to minimize the mistake of component rule
> violations and such.
> 
> 
> Thanks,
> 
> Chris
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited
> 
> royalty-free distribution of the report engine for
> externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> 
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> 
> 


      

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to