Hi Neil, I have read in Wix tutorial that
"Installing a component should never influence other components, removing one should never damage another component or leave any orphaned resource on the target machine." Link: http://www.tramontana.co.hu/wix/lesson1.php#1.2 So as I have mentioned earlier removing a component having a .css file leaves another component which have .aspx file orphaned or invalid In this scenario, still advised to put a single file per Component? Thanks Maheswaran Selvaraj -----Original Message----- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Wednesday, January 07, 2009 3:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Defining components and Files in Wix Installer. In general the advice is one file per component. I think Rob Mensching has some information on this on his blog. Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com <mailto:n...@x2systems.com> ________________________________ From: Maheswaran Selvaraj [mailto:maheswaran.selva...@proteans.com] Sent: Wed 07/01/2009 06:00 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Defining components and Files in Wix Installer. I am beginner in Wix installer development, I need Wix installer to be created for my web application. I need to get .wxs file generated for every build. My web application folder structure look like this I Images ii Css iii AspxPages Each folder has some files. When i use Heat.exe to generate WXS file. <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi <http://schemas.microsoft.com/wix/2006/wi> "> <Product Id="PUT-GUID-HERE" Language="1033" Manufacturer="PUT-COMPANY-NAME-HERE" Name="PUT-PRODUCT-NAME-HERE" > <Package Compressed="yes" InstallerVersion="200" /> <Feature Id="ProductFeature" Level="1" Title="PUT-FEATURE-TITLE-HERE"> <Fragment> <DirectoryRef Id="AspxPages" FileSource="D:\AspxPages"> <Component Id="ActiveDirectoryUserHelper.cs" Guid="PUT-GUID-HERE"> <File Id="ActiveDirectoryUserHelper.cs" Name="ActiveDirectoryUserHelper.cs" KeyPath="yes" Source="D:\ActiveDirectoryUserHelper.cs" /> </Component> </DirectoryRef> <Fragment> <DirectoryRef Id="CSS" FileSource="D:\Css"> <Component Id="ApplicationCSS" Guid="PUT-GUID-HERE"> <File Id="ApplicationCSS" Name="Application.CSS" KeyPath="yes" Source="D:\Application.CSS" /> </Component> </DirectoryRef> </Fragment> </Fragment> </Wix> Multiple components are created with single file as its resources. Is this right way to organize our applications into components ? Should not we put all the files in a single component ? Like <Component id="WebApplication" Guid="Some-Guid"> <File id="AdminPage" name="AdminPage.aspx"/> <File id="CSS" name="Application.CSS"/> <File id="AdminIcon" name="Admin.Ico"/> </Component> Ideally removing one component should not influence on another. In this case removing CSS component and its resources Make ASPX Component invalid. The file which resides in ASPX component have dependency on another CSS or Images Component resource. is there any way to configure dependency list ? what is ideal approach for defining components for Web Application in installer? It would be great if anybody explain on it. Thanks Maheswaran Selvaraj ------------------------------------------------------------------------ ------------------------------------------------- "The information contained in this e-mail transmission is confidential and may be privileged. It is intended only for the addressee(s) stated above. If you are not an addressee, any use, dissemination, distribution, publication, or copying of the information contained in this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately notify us by telephone (+91 80 6618 6555), or e-mail the sender and delete the e-mail from your system. If you do not want to receive our emails please let us know so that we may delete you from our email list. Proteans Software Solutions and its parent group ("CAMO Group") do not accept liability for damage caused by this email, and may monitor email traffic." ------------------------------------------------------------------------ ------------------------------------------------- ------------------------------------------------------------------------ ------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------------------------------------------------- "The information contained in this e-mail transmission is confidential and may be privileged. It is intended only for the addressee(s) stated above. If you are not an addressee, any use, dissemination, distribution, publication, or copying of the information contained in this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately notify us by telephone (+91 80 6618 6555), or e-mail the sender and delete the e-mail from your system. If you do not want to receive our emails please let us know so that we may delete you from our email list. Proteans Software Solutions and its parent group ("CAMO Group") do not accept liability for damage caused by this email, and may monitor email traffic." ------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
