Maybe I'm missing something, but I understood the question not only as a general "How can I resolve/avoid this warning", since that seems to be quite clear from the excellent error message and the link to the ICE documentation as well.
I assume the OP would like to stay with his current harvesting using heat and therefor boldly claim that the _real_ question is: "Can I avoid causing the warning without manual intervention/still using heat?" (Maybe related: Why is heat generating a component per file anyway? Came up only a few days ago as "Heat harvesting and fragment/component generation" where the question was if heat couldn't just create a component per directory instead and Brian Rogers answered with "No, there isn't a way to do that. Gather all files at the folder level and putting them into a component can lead to many problems.") I followed that one closely, because I'm currently tracking my ~250 files by hand, to make sure that the layout/structure makes sense to me - and basically end up more or less with a component per directory for now. On Mon, Apr 12, 2010 at 1:33 PM, Pally Sandher <pally.sand...@iesve.com> wrote: > An easy workaround would be to create child Features under your main > Feature to split the components up into smaller chunks without affecting > the functionality. If your components are within separate Fragments you > could consider creating FeatureGroups containing the Components in each > Fragment & referencing them appropriately in you main Feature Element. > > Palbinder Sandher > Software Deployment & IT Administrator > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > > http://www.iesve.com > **Design, Simulate + Innovate with the <Virtual Environment>** > Integrated Environmental Solutions Limited. Registered in Scotland No. > SC151456 > Registered Office - Helix Building, West Of Scotland Science Park, > Glasgow G20 0SP > Email Disclaimer > > -----Original Message----- > From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] > Sent: 12 April 2010 06:02 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] How to resolve WiX Warning: "Too Many > Componentswithin Feature" ? > > Are you planning to support installation on Win9x systems? > > If so, then yes you should address this warning. However if you're not > planning to support Win9x systems you can safely ignore this limitation. > See also the documentation on ICE47 - > http://msdn.microsoft.com/en-us/library/aa368976(VS.85).aspx and the > '-sice' switch for light if you wish to prevent this particular warning > appearing. > > Sascha > > > > On Mon, Apr 12, 2010 at 1:23 PM, jeff00seattle > <jeff_tan...@earthlink.net> wrote: >> >> Hi >> >> I have a project with over 1000 files (1287 to be exact). >> >> I created WiS configuration using: >> >>> heat dir .\Source -gg -g1 -cg WordPressOnAzure -nologo -sfrag -ke >>> -out Source.wxs >> >> Then I used it within a WiX 3.0 project in Visual Studio 2008. >> >> When I built it, the following single warning appeared: >> >> Warning 1 ICE47: Feature 'ProductFeature' has 1287 components. This >> could cause problems on Win9X systems. You should try to have fewer >> than 817 components per feature. >> >> It bothers me not to address warnings. How can I resolve this? >> >> ----- >> Thanks >> Jeff in Seattle >> -- >> View this message in context: >> http://n2.nabble.com/How-to-resolve-WiX-Warning-Too-Many-Components-wi >> thin-Feature-tp4888158p4888158.html >> Sent from the wix-users mailing list archive at Nabble.com. >> >> ---------------------------------------------------------------------- >> -------- Download Intel® Parallel Studio Eval Try the new >> software tools for yourself. Speed compiling, find bugs proactively, >> and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > ------------------------------------------------------------------------ > ------ > Download Intel® Parallel Studio Eval Try the new software tools for > yourself. Speed compiling, find bugs proactively, and fine-tune > applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
