Thank you all, after using the param "-cg MyComponentGroup", now my problem is solved! Thank you!
> > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 6 Aug 2009 10:48:34 -0700 > From: Brian Rogers <rogers.br...@gmail.com> > Subject: Re: [WiX-users] How to make use of the output .wxs file of > heat.exe in WiX3.0? > To: "General discussion for Windows Installer XML toolset." > <wix-users@lists.sourceforge.net> > Message-ID: > <6dfbefe50908061048m51505696yaee1f3a894c4a...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hey Bonn, > > Just a friendly reminder. Features are only allowed to have 1600 components > according to MSI docs. Heat generates one component per file so I would > recommend breaking up your harvesting effort into more than one directory > and having more than one output file if you have greater than 1600 files. > This might also help you when using the -cg <Group1-n> switch. > > Thanks, > > Brian Rogers > "Intelligence removes complexity." - Me > http://blogs.msdn.com/icumove <-- NEW > > > On Thu, Aug 6, 2009 at 8:38 AM, Richard Hollis <richhol...@gmail.com> > wrote: > > > I think you need to use a component group: > > > > heat ... -cg WebSiteFiles .... > > > > This wraps all your components up into a single component grouping that > you > > can then reference easily in your feature: > > > > <Feature ...> > > <ComponentGroupRef Id="WebSiteFiles" /> > > </Feature> > > > > Richard > > > > 2009/8/6 bonn deng <bonnd...@gmail.com> > > > > > Hi all, I am now using heat.exe to generate the .wxs file of one > > > directory with the command: > > > heat.exe dir "." -gg -nologo -sfrag -out test.wxs -template:product > > > , where the current directory contains thousands of files (because > it's > > > the root dir of a web application). > > > Then I want to include all the files listed in the test.wxs into > > another > > > .wxs file, but the question is: there're so many components and the > > > test.wxs > > > file doesn't list all the components in the Feature Element, in this > case > > > it > > > would be impossible for me to do it manually, What can I do? Please > help, > > > thank you so much in advance! > > > Best wishes, > > > Bonn > > > > > > > > > ------------------------------------------------------------------------------ > > > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > > 30-Day > > > trial. Simplify your report design, integration and deployment - and > > focus > > > on > > > what you do best, core application coding. Discover what's new with > > > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > > _______________________________________________ > > > WiX-users mailing list > > > WiX-users@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > ------------------------------------------------------------------------------ > > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > > trial. Simplify your report design, integration and deployment - and > focus > > on > > what you do best, core application coding. Discover what's new with > > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
