Mike, Thanks for the response.
> -----Original Message----- > From: Mike Dimmick [mailto:[EMAIL PROTECTED] > Sent: Monday, September 18, 2006 5:40 AM > To: Reggie Burnett; wix-users@lists.sourceforge.net > Subject: RE: [WiX-users] Component spanning directories > > Windows Installer only permits a component to install to a single > directory. If you have many directories you will have to author at > least > one component per directory. > > As Cullen says, it may be better in the long run to create one > component > per file. As I recall, you cannot add or remove a file from a component > without changing the component code. > http://msdn.microsoft.com/library/default.asp?url=/library/en- > us/msi/set > up/changing_the_component_code.asp says: > > "When introducing a new component, authors need to do one of the > following to ensure that the component does not conflict with any > existing components: > > - Change the name or target location of any resource that may be > installed under the same name and target location by another component. > > - Otherwise guarantee that the new component is never installed into > the > same folder as another component which has a resource under a common > name and location. This includes localized versions of files with the > same file name. For more information, see What happens if the component > rules are broken?. > > - When changing the component code of an existing component, also > change > the name or target location of every file, registry key, shortcut, and > other resource in the component." > > Tallow.exe or heat.exe (v3) should be able to help you author the XML > if > you're starting from a source tree. > > -- > Mike Dimmick > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Reggie > Burnett > Sent: 15 September 2006 21:27 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Component spanning directories > > We've been using Wix for some time now and recently got around to > cleaning up our wix files. As we are adding samples and source code to > the installer, I find it hard to believe that I can't make a single > component include all my source files. As I understand it, a component > should be anything that you want installed or removed as a unit. Well, > if I want all my sources treated as a single unit, then a single > component should do it. > However, light complains about duplicate symbols. > > Can this be done? If not, why on earth not? It would seem ridiculous > to create a thousand components to install a source tree of a thousand > directories when it should be installed or removed as a unit. > > Thanks > Reggie > > > > ----------------------------------------------------------------------- > - > - > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your job > easier Download IBM WebSphere Application Server v.1.0.1 based on > Apache > Geronimo > http://sel.as- > us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- 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
