[WiX-users] SourceDir
Hi I run the following command to generate the attached .wxs file. heat dir \\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug -gg -sfrag -sreg -template:product -out directory.wxs -cg WebAppComponentGroup In the directory.wxs file the Source attribute of File element is set to SourceDir\FileName. See attached wxs file. I would like to know how this SourceDir can be replaced with the actual path \\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug when running heat. Thanks Satyaprakash J -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wix shortcut run as administrator.
Hi , we are creating the shortcut from our installer on desktop. But the shortcut is not having the option Run As Administrator . How can I this menu Item when the user right clicks on the shortcut. If I create a shortcut manually, I am able to get that option. Any help is appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-shortcut-run-as-administrator-tp5443294p5443294.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] SourceDir
Hi I run the following command to generate the attached .wxs file. heat dir \\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug -gg -sfrag -sreg -template:product -out directory.wxs -cg WebAppComponentGroup In the directory.wxs file the Source attribute of File element is set to SourceDir\FileName. See attached wxs file. I would like to know how this SourceDir can be replaced with the actual path \\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug%3cfile:\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug%3e when running heat. Thanks Satyaprakash J -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Release feature of Installshield in WIX
Hi All, I have a couple of questions regarding WIX. How can I have multiple releases(like in Installshield) with one project? Also is it possible to specify any property like PRODUCTCODE during building the project? Thanks, Akshi -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Release-feature-of-Installshield-in-WIX-tp5444328p5444328.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Release feature of Installshield in WIX
This is something I've been meaning to tackle as I make extensive ( and I mean really extensive ) use of Product Configurations and Release Flags in InsallShield. Basically with WiX you have to break everything out into fragments and then instead of using release flags you use FeatureRef and FeatureGroupRef elements to pull various features into your installer. I think in the end you'll end up having individual wxs files for each product configuration that define the bare minimum variation points such as INSTALLDIR ( INSTALLLOCATION in WiX UI ) , UpgradeCode, ProductCode ( I generate these at build time since I always do major upgrades ). I can basically see it in my mind but I haven't taken the final step yet to actually do it on a large scale and see the pain points. Currently I use WiX to generate close to 1000 merge modules and then use WiX fragements with some custom code to transform them into InstallShield Automation Interface calls. Basically I take a template Basic MSI and build up the feature tree and product configuration at build time using wxs files. My next step will be to create a pure wix version of this; I just don't have it on my roadmap yet. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: akshi_gupta akshi.gupt...@gmail.com To: wix-users@lists.sourceforge.net Sent: Fri, August 20, 2010 7:32:44 AM Subject: [WiX-users] Release feature of Installshield in WIX Hi All, I have a couple of questions regarding WIX. How can I have multiple releases(like in Installshield) with one project? Also is it possible to specify any property like PRODUCTCODE during building the project? Thanks, Akshi -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Release-feature-of-Installshield-in-WIX-tp5444328p5444328.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] SourceDir
Set the PreprocessorVariable. It's an optional string parameter that will substitute SourceDir for another variable name (ex: var.Dir). -Original Message- From: Satyaprakash J [mailto:sat...@smartek21.com] Sent: Friday, August 20, 2010 2:54 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] SourceDir Hi I run the following command to generate the attached .wxs file. heat dir \\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug -gg -sfrag -sreg -template:product -out directory.wxs -cg WebAppComponentGroup In the directory.wxs file the Source attribute of File element is set to SourceDir\FileName. See attached wxs file. I would like to know how this SourceDir can be replaced with the actual path \\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug%3cfile:\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug%3e when running heat. Thanks Satyaprakash J -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ShortCuts Win 7
Hi All, I've just followed this example http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm to the letter in my own script but still no short cut. Do I need to be doing something else for this to work on Windows 7? Thanks, James LalPac Limited registered in England No: 4211747 Partner in Licensing to over 120 UK local government authorities. Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK. Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 (0)1249 462542 Web: www.lalpac.com - Email: i...@lalpac.com This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on this e-mail. Opinions advice, conclusions and other information in this message that do not relate to the official business of LalPac Ltd shall be understood as neither given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall bear no responsibility whatsoever in respect thereof. This e-mail and any attachments have been checked by anti-virus software and are believed to be free of viruses but it is your responsibility to carry out all necessary virus checks and LalPac Ltd accepts no liability in connection therewith. The Company actively monitors all incoming and outgoing e-mails to ensure a satisfactory level of customer service is maintained, to maintain Company security, and to prevent abuse of the Company systems. Please do not print this e-mail unless absolutely necessary - SAVE PAPER -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] (no subject)
Hi, I has two product MSI setups, A.msi and B.msi. They have some shared files installed to Program Files\Common Files. I need update some of them in our Service Pack. I created A_sp1.msp and B_sp1.msp to update those shared files. I have A and B installed on one machine. I also applied A_sp1.msp and B_sp1.msp to the machine. The shared files updated correctly. But when I uninstall either A_sp1.msp or B_sp1.msp, those shared files rolled back to previous version. My questions is: Is there a way to make those updated shared files not roll back to previous version if any of A_sp1.msp or B_sp1.msp is not uninstalled? Thanks, Chunlin -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] MSP uninstall issue related to update shared files
Hi, I has two product MSI setups, A.msi and B.msi. They have some shared files installed to Program Files\Common Files. I need update some of them in our Service Pack. I created A_sp1.msp and B_sp1.msp to update those shared files. I have A and B installed on one machine. I also applied A_sp1.msp and B_sp1.msp to the machine. The shared files updated correctly. But when I uninstall either A_sp1.msp or B_sp1.msp, those shared files rolled back to previous version. My questions is: Is there a way to make those updated shared files not roll back to previous version if any of A_sp1.msp or B_sp1.msp is not uninstalled? Thanks, Chunlin -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix shortcut run as administrator.
It's because it's an advertised shortcut that has the intentional effect of doing resiliency check on the feature the target component belongs to. I think there's an advertised attribute for shortcuts you can set to no, IIRC. Phil Wilson -Original Message- From: MYFLEX [mailto:shrinuen...@gmail.com] Sent: Thursday, August 19, 2010 11:30 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] wix shortcut run as administrator. Hi , we are creating the shortcut from our installer on desktop. But the shortcut is not having the option Run As Administrator . How can I this menu Item when the user right clicks on the shortcut. If I create a shortcut manually, I am able to get that option. Any help is appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-shortcut-run-as-administrator-tp5443294p5443294.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (no subject)
The shared files should also share the exact same Component Guids and component composition (what is inside of each component). -Original Message- From: Chunlin Liu [mailto:c...@esri.com] Sent: Friday, August 20, 2010 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] (no subject) Hi, I has two product MSI setups, A.msi and B.msi. They have some shared files installed to Program Files\Common Files. I need update some of them in our Service Pack. I created A_sp1.msp and B_sp1.msp to update those shared files. I have A and B installed on one machine. I also applied A_sp1.msp and B_sp1.msp to the machine. The shared files updated correctly. But when I uninstall either A_sp1.msp or B_sp1.msp, those shared files rolled back to previous version. My questions is: Is there a way to make those updated shared files not roll back to previous version if any of A_sp1.msp or B_sp1.msp is not uninstalled? Thanks, Chunlin -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Big problem with IIS and not IIS components!!
Set the SKIPCONFIGUREIIS property to some value when you detect that you are not installing and haven't already installed any of your features that do need IIS. -Original Message- From: Igor Lemsky [mailto:igor.lem...@gmail.com] Sent: Thursday, August 19, 2010 3:22 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Big problem with IIS and not IIS components!! I have installer which have some components for IIS (Virtual Directory and so on) and other components doesn't have any connections to IIS, just installing files. So, for them IIS is not needed. But when I install them and no IIS on server Installer get an error: Cannot connect to IIS. This is big problem, because many clients have no IIS on servers... I didn't install any components with IIS, all of the features have files only, but Installer drop such error! -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Component Rules Question
If the new version of the file has the same name as the old file and goes into the same directory, keep the component's guid the same. -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Thursday, August 19, 2010 9:13 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Component Rules Question Hi All, This should be dead quick. Despite reading through numerous pieces of information, both on MSDN and in the archives, I am still a little confused by the Component Rules and I'd like to get some clarification if someone has a moment. I have an installer that installer an .EXE and a number of support files. Each file has it's own component and the installer always carries out a major upgrade with RemoveExistingProducts sequenced after InstallValidate. I now have a new version of one of the support files that I need to incorporate and I need to build a new installer. All the remaining files are the same as before. What do I have to do with the component GUID for the component that contains the altered file? Should it change or not? Thanks Chris -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Component Rules Question
Thanks Blair. On 08/20/2010 03:54 PM, Blair wrote: If the new version of the file has the same name as the old file and goes into the same directory, keep the component's guid the same. -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Thursday, August 19, 2010 9:13 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Component Rules Question Hi All, This should be dead quick. Despite reading through numerous pieces of information, both on MSDN and in the archives, I am still a little confused by the Component Rules and I'd like to get some clarification if someone has a moment. I have an installer that installer an .EXE and a number of support files. Each file has it's own component and the installer always carries out a major upgrade with RemoveExistingProducts sequenced after InstallValidate. I now have a new version of one of the support files that I need to incorporate and I need to build a new installer. All the remaining files are the same as before. What do I have to do with the component GUID for the component that contains the altered file? Should it change or not? Thanks Chris -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WebBrowser control in custom UI dialog
Only via your own UI (either embedded, external (requires a bootstrapper where you can place your UI), or in your own bootstrapper before starting the MSI transaction. You could use IDCRL from a custom action. -Original Message- From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] Sent: Thursday, August 19, 2010 11:45 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WebBrowser control in custom UI dialog Hi, I'm trying to solve the following problem. The MSI will enroll the client into my service only if the user provides LiveID credentials and the MSI is able to get a federated token from LiveID service. Currently LiveID does not support using ws-trust endpoint to get a token, so I will have to either use IDCRL or use a WebBrowser control. I am trying to look into the option of using a WebBrowser control. Is it possible to have a WebBrowser control in the custom UI dialog, so that the user can provide his LiveID credentials and the WebBrowser control can talk to the LiveID service to get a token? I myself am not sure if what I'm asking for even makes any sense, but there has to be a starting point... :) Thanks, Pratap. -- Vote for loksatta = vote for a better future -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shared files/registry question
wixlib -Original Message- From: Sohail Somani [mailto:soh...@taggedtype.net] Sent: Thursday, August 19, 2010 1:14 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Shared files/registry question Hi, I have 4 products for which I need installers. Each installer requires 3 DLLs from another of my products. In my reading on the Internets, it appears that the right way to share these DLL components is to use a merge module. However, the WiX way appears to be to use a ComponentRef. Whether the above is right or wrong, could someone please enlighten me as to the least headache-inducing way to do this properly with WiX? Thanks in advance. -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shared files/registry question
Actually, wixlib and ComponentGroup/ComponentGroupRef. -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, August 20, 2010 1:12 PM To: 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Shared files/registry question wixlib -Original Message- From: Sohail Somani [mailto:soh...@taggedtype.net] Sent: Thursday, August 19, 2010 1:14 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Shared files/registry question Hi, I have 4 products for which I need installers. Each installer requires 3 DLLs from another of my products. In my reading on the Internets, it appears that the right way to share these DLL components is to use a merge module. However, the WiX way appears to be to use a ComponentRef. Whether the above is right or wrong, could someone please enlighten me as to the least headache-inducing way to do this properly with WiX? Thanks in advance. -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] UpgradeGUID question
Or, alter your upgrade table to something that allows whatever your SxS story is. -Original Message- From: Sohail Somani [mailto:soh...@taggedtype.net] Sent: Thursday, August 19, 2010 12:38 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] UpgradeGUID question On 10-08-19 1:10 PM, Wilson, Phil wrote: and it might help to look at it in terms of a product line. Using two products as an example: Prod1 v1.0 = Prod1 v2.0 = Prod1 = v3.0 And Prod2 v10.0 = Prod2 v11.0 = Prod2 = v12.0 Each of these is a product line where each new version is intended to replace any already-installed pre-existing versions. Prod1 and Prod2 would each have their own unique UpgradeId for the life of the product although each version would have a new ProductCode. The point is that Windows makes it easy to do the upgrades because all you do is use the Upgrade table to say which previous versions you want to upgrade. You get the uninstall/upgrade for free with RemoveExistingProducts. Phil Wilson A corollary is if you want to install major versions side-by-side, you should use a different UpgradeCode for each major version, correct? -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (no subject)
Yes, they have the exact same Component Guids. They were included in both setup through the same mergemodule. -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, August 20, 2010 12:39 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] (no subject) The shared files should also share the exact same Component Guids and component composition (what is inside of each component). -Original Message- From: Chunlin Liu [mailto:c...@esri.com] Sent: Friday, August 20, 2010 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] (no subject) Hi, I has two product MSI setups, A.msi and B.msi. They have some shared files installed to Program Files\Common Files. I need update some of them in our Service Pack. I created A_sp1.msp and B_sp1.msp to update those shared files. I have A and B installed on one machine. I also applied A_sp1.msp and B_sp1.msp to the machine. The shared files updated correctly. But when I uninstall either A_sp1.msp or B_sp1.msp, those shared files rolled back to previous version. My questions is: Is there a way to make those updated shared files not roll back to previous version if any of A_sp1.msp or B_sp1.msp is not uninstalled? Thanks, Chunlin -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (no subject)
They are the same between the old and the new merge modules? -Original Message- From: Chunlin Liu [mailto:c...@esri.com] Sent: Friday, August 20, 2010 1:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) Yes, they have the exact same Component Guids. They were included in both setup through the same mergemodule. -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, August 20, 2010 12:39 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] (no subject) The shared files should also share the exact same Component Guids and component composition (what is inside of each component). -Original Message- From: Chunlin Liu [mailto:c...@esri.com] Sent: Friday, August 20, 2010 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] (no subject) Hi, I has two product MSI setups, A.msi and B.msi. They have some shared files installed to Program Files\Common Files. I need update some of them in our Service Pack. I created A_sp1.msp and B_sp1.msp to update those shared files. I have A and B installed on one machine. I also applied A_sp1.msp and B_sp1.msp to the machine. The shared files updated correctly. But when I uninstall either A_sp1.msp or B_sp1.msp, those shared files rolled back to previous version. My questions is: Is there a way to make those updated shared files not roll back to previous version if any of A_sp1.msp or B_sp1.msp is not uninstalled? Thanks, Chunlin -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shared files/registry question
Awesome, thanks. I'm probably going to stick with ComponentGroupRef as the code generating my installers already works with that :D On 10-08-20 4:12 PM, Blair wrote: Actually, wixlib and ComponentGroup/ComponentGroupRef. -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, August 20, 2010 1:12 PM To: 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Shared files/registry question wixlib -Original Message- From: Sohail Somani [mailto:soh...@taggedtype.net] Sent: Thursday, August 19, 2010 1:14 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Shared files/registry question Hi, I have 4 products for which I need installers. Each installer requires 3 DLLs from another of my products. In my reading on the Internets, it appears that the right way to share these DLL components is to use a merge module. However, the WiX way appears to be to use a ComponentRef. Whether the above is right or wrong, could someone please enlighten me as to the least headache-inducing way to do this properly with WiX? Thanks in advance. -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] UpgradeGUID question
Oh, I'm trying to keep it simple here :) On 10-08-20 4:14 PM, Blair wrote: Or, alter your upgrade table to something that allows whatever your SxS story is. -Original Message- From: Sohail Somani [mailto:soh...@taggedtype.net] Sent: Thursday, August 19, 2010 12:38 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] UpgradeGUID question On 10-08-19 1:10 PM, Wilson, Phil wrote: and it might help to look at it in terms of a product line. Using two products as an example: Prod1 v1.0 = Prod1 v2.0 = Prod1 = v3.0 And Prod2 v10.0 = Prod2 v11.0 = Prod2 = v12.0 Each of these is a product line where each new version is intended to replace any already-installed pre-existing versions. Prod1 and Prod2 would each have their own unique UpgradeId for the life of the product although each version would have a new ProductCode. The point is that Windows makes it easy to do the upgrades because all you do is use the Upgrade table to say which previous versions you want to upgrade. You get the uninstall/upgrade for free with RemoveExistingProducts. Phil Wilson A corollary is if you want to install major versions side-by-side, you should use a different UpgradeCode for each major version, correct? -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
