Re: [WiX-users] Multiple instance install questions
Hi 1. Is it possible to uninstall just a single instance, if that instance is no longer needed? Yes, Add/Remove programs will do it, or you can use the command line if you know the Instance ProductCode 2. Is it possible to upgrade just a single instance, if needed. Yes, but again you need some way to identify the instance, especially if it is a major upgrade. With a Major Upgrade, I found that the AppSearch finds all of the instances and schedules them all for deletion. So what I do is write the current product code to a registry key, read it in, and then substitute this value into the Property from the Upgrade table (can't remember the term). There are some other discussions over the past few years in wix-users that discuss other ways of dealing with major upgrades. Michael -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: Friday, 10 June 2011 5:47 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Multiple instance install questions I have a requirement to add the ability to support multiple instance installs to our website Wix installer. I've been looking at a few sites that discuss how to do this, but I have a couple of questions regarding this. 1. Is it possible to uninstall just a single instance, if that instance is no longer needed? 2. Is it possible to upgrade just a single instance, if needed. We are currently using Wix 3.5 for our web application installer, which is used to install a website. The requirement has now been added that the installer must support multiple instances, so that we can do something like below: ProductWebSite\BrandA ProductWebSite\BrandB ProductWebSite\BrandC ProductWebSite\BrandD -- 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 -- 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
Re: [WiX-users] Multiple instance install questions
As I am sure you have read, multi-instance can be a painful road, but YES it is possible to do both of the above. Each instance will just need to make sure to have it's own product codes and upgrade codes. Then they can be upgraded or uninstalled independently of any other instance on the system. Also non-file components that are multi-instance do not work correctly in wix 3.5 AFAIK, b/c it is missing the 'MultiInstance' attribute on the 'Component' elements. There may be workarounds though. On Thu, Jun 9, 2011 at 2:47 PM, CoolBreeze wrote: > I have a requirement to add the ability to support multiple instance > installs to our website Wix installer. I've been looking at a few sites > that > discuss how to do this, but I have a couple of questions regarding this. > > 1. Is it possible to uninstall just a single instance, if that instance is > no longer needed? > 2. Is it possible to upgrade just a single instance, if needed. > > We are currently using Wix 3.5 for our web application installer, which is > used to install a website. The requirement has now been added that the > installer must support multiple instances, so that we can do something like > below: > > ProductWebSite\BrandA > ProductWebSite\BrandB > ProductWebSite\BrandC > ProductWebSite\BrandD > > -- > 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 > -- Tyler Walters -- 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
[WiX-users] Multiple instance install questions
I have a requirement to add the ability to support multiple instance installs to our website Wix installer. I've been looking at a few sites that discuss how to do this, but I have a couple of questions regarding this. 1. Is it possible to uninstall just a single instance, if that instance is no longer needed? 2. Is it possible to upgrade just a single instance, if needed. We are currently using Wix 3.5 for our web application installer, which is used to install a website. The requirement has now been added that the installer must support multiple instances, so that we can do something like below: ProductWebSite\BrandA ProductWebSite\BrandB ProductWebSite\BrandC ProductWebSite\BrandD -- 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
Re: [WiX-users] WixDependencyExtension
Hi, Package A ist installed conditionally (e.g. based on user selection) and requires Package B. So Package B should be installed only if Package A is installed. Of course this can be achieved with the mba, just wondered if there's a cleaner solution. Michael Am 09.06.2011 20:03, schrieb John Robbins: > Hi, > > Are you talking about A.MSI must be installed before B.MSI? > > If so use the After attribute on the MSIPackage Element when defining B.MSI > in your Burn WXS files. See > http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm for more info. > > John > Wintellect > http://www.wintellect.com > +1-877-968-5528 > > -Original Message- > From: Michael Stoll [mailto:unwicht...@mistoll.de] > Sent: Thursday, June 09, 2011 7:20 AM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] WixDependencyExtension > > What't the WixDependencyExtension? Any documentation on it? > I'm looking for a way to tell burn that package A needs package B installed. > Can this be done with WixDependencyExtension? > > Michael > > > -- > 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 > > -- > 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 > -- 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
Re: [WiX-users] Upgrade without providing or removing some previous component.
Sorry for my previous empty post. Must've got sent by accident. Thanks, Peter, for your ideas. I’ll consider them. >>Cant you just upgrade the older installer with the fixes to A, keeping B as it was at release, and make that available to old users for download? The old installer (pre-2010) did not include B. Yes, I could make two separate upgrade installers, but it would get confusing for users to know which one they were supposed to use. >>Then make a later version of that installer with the new version of B and make that available for new users on CD. Upgrading people by sending them another CD would work but is kind of tough. It requires them to call up to ask for it, and would be a cost to us. I guess it depends how many of those users are out there, which I don’t know. I may have misunderstood your suggestion, though. >>If you don't want to make an upgrade installer you could make the upgrade available as a patch (.msp) for older users. The patch would only contain the changes to component A and couldn't be used without the older installer. A patch is harder to write than a major upgrade but, if you haven't violated component rules, it might work for you. Yes that’s one possibility and I thought of that, too. I’m not so familiar with patches so I’ll have to look into it. If it happens that we want to update the driver part of it I’m not sure a driver can be patched. We use DIFxApp for that. I had another thought along the lines of the workaround I mentioned earlier. I’m going to see if I can make an upgrade that can include a dummy component B and then use a condition for it that which is always false so B doesn't get installed. If that doesn’t work because it still removes existing, installed component Bs (which I don’t want), then I’ll try to set the condition dynamically at runtime depending on whether I find component B already on hard disk. I’m not sure if that’s possible or if it will work so I’ll need to experiment. Thanks! Jim -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, June 09, 2011 1:37 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Upgrade without providing or removing some previouscomponent. Cant you just upgrade the older installer with the fixes to A, keeping B as it was at release, and make that available to old users for download ? Then make a later version of that installer with the new version of B and make that available for new users on CD. If you don't want to make an upgrade installer you could make the upgrade available as a patch (.msp) for older users. The patch would only contain the changes to component A and couldn't be used without the older installer. A patch is harder to write than a major upgrade but, if you haven't violated component rules, it might work for you. -Original Message- From: Jim Hewes [mailto:jimhe...@gmail.com] Sent: 09 June 2011 01:03 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Upgrade without providing or removing some previous component. Due to my lack of expertise in installers, I think I got into a bad situation with the wrong installer arrangement and I'm wondering what the best way out of it is. I'm using WiX 3.0, but this is a more general install problem so let me know if it's not appropriate to ask here. I have an installer that installs two components A and B both within the same feature. Component A is a device driver and some associated software. Component B is a third-party library comprised of two DLLs and is used by the driver/software. This third-party library requires a per-unit license. We distribute this on CD with the device and so by counting the CDs we can keep track of the licenses. We began including the library on the CD last year. But there are older owners of the device who would want to download the new version. We cannot put this installer on the web for download because we can't count or track those licenses. So the problem is, we want to upgrade Component A with bug fixes and make it available for web download. But we can't include component B for license reasons---because older users shouldn't get it for free. But if I leave component B out of the upgrade, I believe the upgrade process will remove B from the hard disk of legitimate owners of it. (I know if I had at least made component B as a separate feature, I could specify that it not be removed and do a major upgrade. But it's too late at this point.) My best workaround idea so far is for the upgrade to include dummy DLLs for component B that have a lower version number than the real ones. So when an upgrade happens, the real DLLs already on hard disk will be left alone. And for older users who don't have the license to the library, they will just get the dummy DLLs installed. It's messy, and I hate to think I have to do this for the life of the product. Is there a better way? I think for the future I will put component B completely
Re: [WiX-users] WixDependencyExtension
Hi, Are you talking about A.MSI must be installed before B.MSI? If so use the After attribute on the MSIPackage Element when defining B.MSI in your Burn WXS files. See http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm for more info. John Wintellect http://www.wintellect.com +1-877-968-5528 -Original Message- From: Michael Stoll [mailto:unwicht...@mistoll.de] Sent: Thursday, June 09, 2011 7:20 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WixDependencyExtension What't the WixDependencyExtension? Any documentation on it? I'm looking for a way to tell burn that package A needs package B installed. Can this be done with WixDependencyExtension? Michael -- 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 -- 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
Re: [WiX-users] Failed to configure IIS web svc ext
Here is the markup. Thank you for your help. Test Environment: Windows Server 2008 R2 IIS 7.5 .NET 4.0 -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Failed-to-configure-IIS-web-svc-ext-tp6360160p6458856.html Sent from the wix-users mailing list archive at Nabble.com. -- 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
Re: [WiX-users] moving component to another feature
Thanks Peter! I will only rearrange the feature/component tree. File will not be moved to another location. So major upgrade will be it. Thanks again! Martin -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, June 09, 2011 5:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] moving component to another feature You should not change the guid when moving between features. You would change it if you moved the component to another directory, which is what you might be thinking of. If you rearrange the feature-component tree then you can only use major upgrades. You won't be able to create a small or minor update. -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: 09 June 2011 15:30 To: wix-users Subject: [WiX-users] moving component to another feature Hi, I have one component that I need to move from one feature to another. Should I change the component GUID in order to prevent orphaned files? Thanks, Martin Kulov http://www.kulov.net - - 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 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. -- 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 -- 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
Re: [WiX-users] moving component to another feature
You should not change the guid when moving between features. You would change it if you moved the component to another directory, which is what you might be thinking of. If you rearrange the feature-component tree then you can only use major upgrades. You won't be able to create a small or minor update. -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: 09 June 2011 15:30 To: wix-users Subject: [WiX-users] moving component to another feature Hi, I have one component that I need to move from one feature to another. Should I change the component GUID in order to prevent orphaned files? Thanks, Martin Kulov http://www.kulov.net - - 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 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. -- 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
[WiX-users] moving component to another feature
Hi, I have one component that I need to move from one feature to another. Should I change the component GUID in order to prevent orphaned files? Thanks, Martin Kulov http://www.kulov.net -- 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
[WiX-users] WixDependencyExtension
What't the WixDependencyExtension? Any documentation on it? I'm looking for a way to tell burn that package A needs package B installed. Can this be done with WixDependencyExtension? Michael -- 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
[WiX-users] Simple file extraction & WI vs WiX
Hello everyone, this is my first participation in the mailing list - do forgive my (hopefully) trivial questions! What I need to do is this: - 4 data files should be extracted to a specific (but "user-relative") location. - the user should decide which of the 4 files that should be extracted (check/uncheck). - the extraction must work on Windows XP and Windows 7. - only one executable (unfortunately data files + instructions is not an option). The path to where the files should be extracted to looks as follows (on both XP and 7): C:\Users\[Current User]\AppData\Local\WinFormServer\Configurations As you can see, the path is absolute except for the current user folder. Can this be done easily? Should I use Windows Installer or WiX? Thank you very much, Arvid Kongstad, Sweden -- 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
Re: [WiX-users] Upgrade without providing or removing some previouscomponent.
Cant you just upgrade the older installer with the fixes to A, keeping B as it was at release, and make that available to old users for download ? Then make a later version of that installer with the new version of B and make that available for new users on CD. If you don't want to make an upgrade installer you could make the upgrade available as a patch (.msp) for older users. The patch would only contain the changes to component A and couldn't be used without the older installer. A patch is harder to write than a major upgrade but, if you haven't violated component rules, it might work for you. -Original Message- From: Jim Hewes [mailto:jimhe...@gmail.com] Sent: 09 June 2011 01:03 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Upgrade without providing or removing some previouscomponent. Due to my lack of expertise in installers, I think I got into a bad situation with the wrong installer arrangement and I'm wondering what the best way out of it is. I'm using WiX 3.0, but this is a more general install problem so let me know if it's not appropriate to ask here. I have an installer that installs two components A and B both within the same feature. Component A is a device driver and some associated software. Component B is a third-party library comprised of two DLLs and is used by the driver/software. This third-party library requires a per-unit license. We distribute this on CD with the device and so by counting the CDs we can keep track of the licenses. We began including the library on the CD last year. But there are older owners of the device who would want to download the new version. We cannot put this installer on the web for download because we can't count or track those licenses. So the problem is, we want to upgrade Component A with bug fixes and make it available for web download. But we can't include component B for license reasons---because older users shouldn't get it for free. But if I leave component B out of the upgrade, I believe the upgrade process will remove B from the hard disk of legitimate owners of it. (I know if I had at least made component B as a separate feature, I could specify that it not be removed and do a major upgrade. But it's too late at this point.) My best workaround idea so far is for the upgrade to include dummy DLLs for component B that have a lower version number than the real ones. So when an upgrade happens, the real DLLs already on hard disk will be left alone. And for older users who don't have the license to the library, they will just get the dummy DLLs installed. It's messy, and I hate to think I have to do this for the life of the product. Is there a better way? I think for the future I will put component B completely in its own installer and put that only on the CD. But that doesn't help the current problem. Thanks for any help, Jim - - 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 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. -- 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
