Thanks Peter, and will surely take care in future. On Mon, Jun 27, 2011 at 7:18 PM, <wix-users-requ...@lists.sourceforge.net>wrote:
> Send WiX-users mailing list submissions to > wix-users@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/wix-users > or, via email, send a message with subject or body 'help' to > wix-users-requ...@lists.sourceforge.net > > You can reach the person managing the list at > wix-users-ow...@lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of WiX-users digest..." > > > Today's Topics: > > 1. Re: Install package using multiple solutions (Peter Shirtcliffe) > 2. Using the same .exe file for different services in one MSI? > (Stefan Kuhr) > 3. Check the checkbox programmatically (Rahul Ramesh Ekbote) > 4. Re: Installing WiX library to different location, recalling > location on modify/uninstall (Sean Dockery) > 5. Re: Wix bootstrapper issues (Alexander Kriv?cs Schr?der) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 27 Jun 2011 12:09:01 +0100 > From: "Peter Shirtcliffe" <pshirtcli...@sdl.com> > Subject: Re: [WiX-users] Install package using multiple solutions > To: "General discussion for Windows Installer XML toolset." > <wix-users@lists.sourceforge.net> > Message-ID: > > <8701d1480741164db71e42643c4a489f03811...@emeamail0305.global.sdl.corp> > > Content-Type: text/plain; charset="us-ascii" > > Please send all replies to the mailing list so that everyone can benefit > from > the answers and other people can offer help. > > > > You can create a single Wix project that will include the code from both > solutions. Add a new Wix MSI project to the "main" solution (whichever that > is). > > Add the files created by both solutions into the .wxs file that is > automatically created. Make sure that the Wix project is last in the > solution's build order. > > > > > > Solution ABC: > > 80 code projects > > 1 Wix project that outputs an MSI > > Product.wxs > > > > Solution XYZ: > > 40 code projects > > > > The product.wxs file will include many components:- some components will > have > file elements where the Source attribute is pointing to the files created > by > the XYZ solution and some components will have file elements where the > source > attribute is pointing to files created by the ABC solution. > > > > For example: > > <Component> > > <File Source="<path to output directory of ABC>/file1.dll" /> > > </Component> > > <Component> > > <File Source="<path to output directory of ABC>/file2.dll" /> > > </Component> > > ... > > <Component> > > <File Source="<path to output directory of XYZ>/fileA.dll" /> > > </Component> > > <Component> > > <File Source="<path to output directory of XYZ>/fileB.dll" /> > > </Component> > > ... > > > > The procedure is the same as for creating 1 solution containing 1 Wix > project. The difference is that some of your file elements will have source > attribute paths that point to files in the other solution. > > > > This isn't the only way to do this, or the best, but it's simple. > > > > From: Divyesh Ajmera [mailto:ajmera.divy...@gmail.com] > Sent: 27 June 2011 11:50 > To: Peter Shirtcliffe > Subject: Install package using multiple solutions > > > > > Hi Peter, > > Sorry for a direct mail, i read your solution and tried to understand it a > bit, but dint succeed much. > here is my actual scenario: > > I have two solutions, say abc.sln and xzy.sln > abc.sln has some 80 projects and xyz.sln has some 40+ projects. > > Now what i want is to create a installation package using WIX project on VS > 2010, using IDE, this package must include these both solutions and also > their respective projects. > what i have learned from studying is for single project we have to create a > .wxs file satisfying the schema and build the WIX project, it takes care > about creating .wixproj and .wixobj > but have no idea about doing the same for two solutions. > As per i know, it has to be done using .wxs file, but if uyou have some > other > solution, kindly share. > > kindly help in this respect. > Also it wolud be very helpful if you have any sample doing the same or any > link where i can get a reference. > > -- > > Thanks, > > Divyesh Ajmera > > M: +91 81479 87986 > > +91 76762 48064 > > > > E-mail: ajmera.divy...@gmail.com > > </pre> > <BR style="font-size:4px;"> > <a href = "http://www.sdl.com/sdl-vision";><img src=" > http://www.sdl.com/images/email_new_logo.png"; alt="www.sdl.com/sdl-vision" > border="0"/></a> > <BR> > <font face="arial" size="2"><a href ="http://www.sdl.com/sdl-vision"; > style="color:005740; font-weight: bold">www.sdl.com/sdl-vision</a></font> > <BR> > <BR> > <font face="arial" size="1" color="#736F6E"> > <b>SDL PLC confidential, all rights reserved.</b> > If you are not the intended recipient of this mail SDL requests and > requires that you delete it without acting upon or copying any of its > contents, and we further request that you advise us.<BR> > SDL PLC is a public limited company registered in England and Wales. > Registered number: 02675207.<BR> > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 > 7DY, UK. > </font> > > > ------------------------------ > > Message: 2 > Date: Mon, 27 Jun 2011 05:31:53 -0700 (PDT) > From: Stefan Kuhr <kustt...@gmx.li> > Subject: [WiX-users] Using the same .exe file for different services > in one MSI? > To: wix-users@lists.sourceforge.net > Message-ID: <1309177913407-6520212.p...@n2.nabble.com> > Content-Type: text/plain; charset=us-ascii > > Hello everyone, > > our product contains multiple services and all use the same .exe file and > differ only via their name and command line, where a DLL name is passed > that > contains the real service code. So the exe file is more or less a reusable > framework much like svchost.exe and distinct service functionality is > implemented in DLLs. Is it possible to use the WiX ServiceInstall element > to > install multiple such services from one WiX script or is this simply > impossible and I have to resort to a custom action? As far as I see, the > File element whose Keypath is set to 'Yes' within the component where the > ServiceInstall element resides, is considered the BinaryPath of the > service. > In my case however, this file element would be the same for different > services/components and even worse, other installs that we are about to > write in the future will use the same exe file as well so ideally it would > be in one component that we reuse across installs. > > Any help appreciated, > > -- > Stefan Kuhr > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-the-same-exe-file-for-different-services-in-one-MSI-tp6520212p6520212.html > Sent from the wix-users mailing list archive at Nabble.com. > > > > ------------------------------ > > Message: 3 > Date: Mon, 27 Jun 2011 12:59:56 +0000 > From: Rahul Ramesh Ekbote <rahu...@microsoft.com> > Subject: [WiX-users] Check the checkbox programmatically > To: "General discussion for Windows Installer XML toolset. > (wix-users@lists.sourceforge.net)" <wix-users@lists.sourceforge.net > > > Message-ID: > < > 2df8a8f7fab4654baac628df8df4607f327...@sinex14mbxc416.southpacific.corp.microsoft.com > > > > Content-Type: text/plain; charset="us-ascii" > > Hi, > How to check the checkbox programmatically. I search lot on Google but > couldn't find it. > > Thanks, > Rahul > > > ------------------------------ > > Message: 4 > Date: Mon, 27 Jun 2011 07:45:16 -0600 > From: "Sean Dockery" <dockerys...@gmail.com> > Subject: Re: [WiX-users] Installing WiX library to different location, > recalling location on modify/uninstall > To: "'General discussion for Windows Installer XML toolset.'" > <wix-users@lists.sourceforge.net> > Message-ID: <002201cc34d0$737d86b0$5a789410$@gmail.com> > Content-Type: text/plain; charset="us-ascii" > > Thanks, Peter, for the prompt reply. > > I had previously gotten as far as you have described. I realized in > re-reading my original post that I wasn't as clear about the problem as I > should have been. Specifically, in my situation the WiX library > contributes > 32-bit components, which may or may not be installed to the same location > as > the 64-bit product's component. In the case of the 32-bit product, these > sets of components will always be installed to the same location. So, this > is how things appear in the 64-bit product installer project... > > wixlib: > > <Wix...> > <Fragment> > <DirectoryRef Id="LIBINSTDIR"> > <Component Id="LibComponent" ...> > ... > </Component> > </DirectoryRef> > </Fragment> > </Wix> > > product: > > <Wix...> > ... > <Directory Id="TARGETDIR" Name="SourceDir"> > <Directory Id="ProgramFiles64Folder"> > <Directory Id="PRDINSTDIR" Name="CompanyName"> > <Component Id="PrdComponent" ...> > ... > </Component> > </Directory> > </Directory> > <Directory Id="ProgramFilesFolder"> > <Directory Id="LIBINSTDIR" Name="CompanyName" /> > </Directory> > </Directory> > > <Feature Id="ProductFeature" Name="Product Name" > ConfigurableDirectory="PRDINSTDIR" Display="expand" Level="1"> > <ComponentRef Id="PrdComponent" /> > <Feature Id="LibraryFeature" Name="Library" Display="hidden" > Level="1"> > <ComponentRef Id="LibComponent" /> > </Feature> > </Feature> > > ... > > <UIRef Id="WiXUI_FeatureTree" /> > ... > </Wix> > > Because 32-bit components cannot be installed to a 64-bit Program Files > folder, the root folder into which these components are installed are > necessarily different _when the default location is accepted_. However, > when the user chooses to customize the install location of the product, if > the target location is _not_ under the ProgramFiles64Folder, it is required > that the 32-bit components and 64-bit components be installed to the same > target location. For example, either in parallel directories like this... > > - PRDINSTDIR = C:\Program Files\CompanyName > - LIBINSTDIR = C:\Program Files (x86)\CompanyName > > ...or in a single directory like this... > > - PRDINSTDIR = LIBINSTDIR = C:\SomewhereElse\CompanyName > > So, I have two different problems. > > 1st, I need to be able to dynamically derive the value of LIBINSTDIR based > on PRDINSTDIR. That is, if the value of PRDINSTDIR is subordinate to > [ProgramFiles64Folder], then LIBINSTDIR should be installed to a parallel > location under [ProgramFilesFolder]. And if PRDINSTDIR falls outside of > [ProgramFiles64Folder], then LIBINSTDIR can install to the same location. > I > expect that I will need to use some inline VBscript or similar to program > this behaviour in a custom action during the UI sequence. > > 2nd, I need to apply the dynamic value of LIBINSTDIR in such a way that it > is recalled by the WiX library contributed components when they are > uninstalled. I thought that a type 51 custom action would achieve this, > but > I think that it needs to be called earlier than before "InstallFiles". > That > is why I was wondering how "early" it could be called; I was proposing to > do > it immediately following "AppSearch" and wondered if there may be any > problems in doing so. > > I assumed, too, that the directory identifiers needed to be public > properties (i.e.: all uppercase) to allow them to breach the UI/execute > barrier -- but perhaps having them breach the UI/execute barrier isn't > necessary? > > Any advice you (or anyone else, for that matter) can offer is welcome. > > PS: I'm using WiX 3.5, if that matters. It appears that the install > sequence described in the Nick Ramirez WiX book does not match the install > sequence in WiX 3.5 in all cases. I suspect that this is a consequence of > the UI that I'm selecting, however; but I don't know enough about WiX (yet) > to be sure. > > -----Original Message----- > From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] > Sent: June 27, 2011 03:03 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Installing WiX library to different location, > recalling location on modify/uninstall > > A simple wixlib looks something like this. There are some components under > a > directory ref and they are gathered into a component group. > > <Wix...> > <Fragment Id="TestWixLib"> > > <DirectoryRef Id="LIB_Dir"> > <Component> > <File Id="LIB_test.txt" Source="test.txt" /> > </Component> > ...more components > </DirectoryRef> > > <ComponentGroup Id="LIB_Components"> > <ComponentRef Id="LIB_test.txt " /> > .. more componentrefs > </ComponentGroup> > > </Fragment> > </Wix> > > To use this wixlib, reference the component group in a feature and define a > directory alias where you want the files to be. > > <Wix..> > <Product...> > <Feature Id="Main" ..> > <ComponentGroupRef Id="LIB_Components" /> > .. other product components... > </Feature> > > <Directory Id="TARGETDIR" Name="SourceDir"> > <Directory Id="ProgramFilesFolder"> > <Directory Id="CompanyProgramsDir" Name="PLC"> > <Directory Id="ProductDir" Name="FunkyProduct"> > <Directory Id="LIB_Dir" /> <!-- A dir with no name is just an > alias for the containing directory element --> > </Directory> > </Directory> > </Directory> > </Directory> > > </Product> > </Wix..> > > -----Original Message----- > From: Sean Dockery [mailto:dockerys...@gmail.com] > Sent: 27 June 2011 07:11 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Installing WiX library to different location,recalling > location on modify/uninstall > > Hello everyone, > > > > I am in the midst of porting an InstallShield InstallScript for MSI project > to WiX and I've run into a little trouble. I'm new to WiX and not terribly > knowledgeable about Windows Installer, so please forgive me if I'm asking a > question for which the answer seems obvious. > > > > In my effort to port one of our merge modules to a WiX library, I need to > install the content of the WiX library to a custom location - but not the > same location as the main product project. > > > > I have followed the example on page 125 of Nick Ramirez's book on WiX, in > which a type 51 custom action is used to set the AppDataDir property before > the "InstallFiles" sequence in the InstallExecuteSequence. The files > install to the dynamic location, but - unfortunately - it appears that > these > components do not remember where they were installed and removing the > entire > product results in the WiX library contributed files to remain when > installed to a non-default location. Is the problem merely that the type > 51 > custom action should be called earlier in the install execute sequence? > For > example, should it be set immediately after the AppSearch sequence? > > > > Best regards, > > Sean > > > > > ---------------------------------------------------------------------------- > - > - > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > SDL PLC confidential, all rights reserved. > If you are not the intended recipient of this mail SDL requests and > requires > that you delete it without acting upon or copying any of its contents, and > we further request that you advise us. > SDL PLC is a public limited company registered in England and Wales. > Registered number: 02675207. > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 > 7DY, UK. > > > > ---------------------------------------------------------------------------- > -- > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > ------------------------------ > > Message: 5 > Date: Mon, 27 Jun 2011 15:48:05 +0200 > From: Alexander Kriv?cs Schr?der <alexander.schro...@mermaid.no> > Subject: Re: [WiX-users] Wix bootstrapper issues > To: General discussion for Windows Installer XML toolset. > <wix-users@lists.sourceforge.net> > Message-ID: > <17860180d1bd8c41abece6ac6f36239c6e6ba7d...@htv-mail01.headline.tv> > Content-Type: text/plain; charset="utf-8" > > Hey. > > Thank you for your answers, Rob and Vadym. Vadym's suggestion of setting > the installers to ALLUSERS=1 fixes the problem. My question is thus: Why > doesn't the ProductCode detection work without setting ALLUSERS=1? > > As for your question, Rob, I'm not installing an MSI from outside the > bootstrapper. I'm installing two MSIs (both not previously installed) with > this installer, and when ALLUSERS=1, they both end up being properly > detected, and thus if I run the bootstrapper a second time, the PackageState > of both of them is 'Present'. Without ALLUSERS=1, however, only one of them > is 'Present'. The other still shows up as 'Absent'. > > In case it matters, I run these tests on Windows 7. > > Best regards > > ALEXANDER K. SCHR?DER > > -----Original Message----- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: 18. juni 2011 18:54 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Wix bootstrapper issues > > The ProductCode. Are you installing a new version of the MSI from outside > of the bootstrapper? > > -- > virtually, Rob Mensching - http://RobMensching.com LLC > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image Editing > and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------ > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > > ------------------------------ > > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > End of WiX-users Digest, Vol 61, Issue 53 > ***************************************** > -- Divyesh Ajmera M: +91 81479 87986 +91 76762 48064 E-mail: divyesh.ajm...@misys.com ajmera.divy...@gmail.com ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
![http://www.sdl.com/images/email_new_logo.png"](http://www.sdl.com/images/email_new_logo.png"){kind=link}