[WiX-users] Running a third party installer
Hi, In our WIX installer, a third party installer (postgresql server installer) is run as a custom action the third party installer starts and the following error message pops up. Another program is being installed. Please wait until that installation is complete, and then try installing this software again Any idea why this happens? -- Vishva -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WIX Coding Guidelines/Standards
I would like to know if there are any coding guidelines/standards to be followed while using WIX implementation. Also any good books on the same? Thanks, Smitha -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper for localized installer
We have a bootstrapper exe which will install the .net framework and depending on the localized setting of the machine,it will pick up the required localized mst. Our exe is working only till the point where it tries to launch the localized mst but fails throwing an error dialog The file resdll_GERMANREScan not be installed because the file in the CAB file pcpe.cab not found wurde.Dies indicates a network error, even a CD-ROM reading error or a problem with the package We tried with German and above error message is a translation of the error string. Can someone point me to a link where it explains about having bootstapper for localized installer..? Thanks, Smitha -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Running a third party installer
Without deeper knowign the issue: Are you trying to run an MSI from another one ? If yes: Not recommended! The only workaround is to abuse the InstallUI sequence for such an approach. This fails e.g. if user runs installer without UI! A short fragment to illustrate such an approach: CustomAction Id=Install_MSI Impersonate=yes Execute=immediate Directory=WindowsFolder ExeCommand=msiexec.exe /i quot;c:\MyMSIpackage.msiquot; /qb Return=ignore / InstallUISequence Custom Action=Install_MSI After=ProgressDlgNot Installed/Custom /InstallUISequence But to emphasis it again. Not recommended by MSDN but to be honest I do a similat approach as well e.g. for deploying the VCRedists. Regards Tobias 2011/2/25 Samudra Vishvajith vishv...@gmail.com: Hi, In our WIX installer, a third party installer (postgresql server installer) is run as a custom action the third party installer starts and the following error message pops up. Another program is being installed. Please wait until that installation is complete, and then try installing this software again Any idea why this happens? -- Vishva -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Running a third party installer
Just as additional information if you want to run several MSIs: For sure a bootstrapper or chainer application to do so would be the recommended solution. Tobias 2011/2/25 Tobias S tobias.s1...@gmail.com: Without deeper knowign the issue: Are you trying to run an MSI from another one ? If yes: Not recommended! The only workaround is to abuse the InstallUI sequence for such an approach. This fails e.g. if user runs installer without UI! A short fragment to illustrate such an approach: CustomAction Id=Install_MSI Impersonate=yes Execute=immediate Directory=WindowsFolder ExeCommand=msiexec.exe /i quot;c:\MyMSIpackage.msiquot; /qb Return=ignore / InstallUISequence Custom Action=Install_MSI After=ProgressDlgNot Installed/Custom /InstallUISequence But to emphasis it again. Not recommended by MSDN but to be honest I do a similat approach as well e.g. for deploying the VCRedists. Regards Tobias 2011/2/25 Samudra Vishvajith vishv...@gmail.com: Hi, In our WIX installer, a third party installer (postgresql server installer) is run as a custom action the third party installer starts and the following error message pops up. Another program is being installed. Please wait until that installation is complete, and then try installing this software again Any idea why this happens? -- Vishva -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ExecSecureObjects fails with access denied error
Hello WiX Community, I have a requirement for my MSI package to set certain permissions on %SYSTEMROOT%\Globalization folder. Well, that's quite trivial itself, but ExecSecureObjects throws access denied error trying to do this. After some troubleshooting and investigations it turns out that SYSTEM account (which msiexec runs as, AFAIK) doesn't have Change Permissions right to that folder. Moreover, by default the Administrators group doesn't have these rights, either. Hence, I get the same error trying to change the permissions manually. So, the question is what can I do in this situation? :-) It seems that it's not possible to tell it to fail silently and continue with other folders, is it? Any thoughts and suggestions are welcome! Thanks, -- Yan -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Run UI sequence during patch removal?
Hi - Is it possible to run a UI sequence during the removal of a patch? I've tried the following but it does not display. Show Dialog=PatchUninstallDlg After=CostFinalizeMSIPATCHREMOVE/Show (From the log file UILEVEL =5 CLIENTUILEVEL = 0) If not, is it possible to run an immediate CA before the files have been reverted to the previous version? Thanks - Tom -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem with RemoveExistingProducts action
I would actually consider that desirable behavior in my product, since
version 2.1 was designed and tested with bbb.dll version 1.0 - not version
1.5. What's happening is the removal of product 2.0 causes the reference
count on component bbb.dll to go to zero, and so MSI deletes the file. Then
the new version installs a fresh copy of bbb.dll version 1.0.
If you want to retain the behavior you describe, then you would need to test
product version 2.1 with both bbb.dll versions 1.5 and 1.0. Version 1.5
would occur when the user upgrades and version 1.0 would occur on a clean
install of product 2.1. If at all possible, I like to just to put the DLLs
alongside your application in the application directory, and not put them in
a shared place like the Windows System32 directory - this is easier since
you only have to test one configuration instead of two. This tends to be a
recommended way of doing things to avoid DLL Hell.
That said, sometimes 3rd-party components have prescribed ways of
installation and there's nothing you can do about it. And maybe there are
some reasons for keeping the bbb.dll file around. For example, you might
have bbb.dll as a 3rd-party component in the SYSTEM32 directory. In that
case I would set the Permanent and SharedDllRefCount attributes both to
yes. Permanent will add an extra reference to the component during
installation, so that it doesn't get deleted on uninstall (or therefore an
upgrade). SharedDllRefCount deals with maintaining a similar, older-style
reference counting scheme for non-Windows Installer installers so that some
other non-MSI installer doesn't wipe your DLL from underneath you.
James
-Original Message-
From: Igor Lemsky [mailto:igor.lem...@gmail.com]
Sent: Friday, February 25, 2011 04:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem with RemoveExistingProducts action
It seems that I dont break component rules... I just add new component into
existing feature and trying to upgrade.
Besides I put it after InstallInitialize, but now take another problem. If
some of dlls will have lower version - it deleted during upgrade.
If product version 2.0 have bbb.dll version 1.5, and product version 2.1
have dll version 1.0 - it just erase it during upgrade!
As I understand it must leave bbb.dll version 1.5...
On Tue, Feb 22, 2011 at 9:13 PM, James Johnston
johnst...@inn-soft.comwrote:
In that case you have to be following component rules. See
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/ Also with
your placement, if the old version fails to uninstall then the user
will have both old new versions installed - something to keep in mind.
Try putting it after InstallInitialize. The old version will be
uninstalled first before anything new is installed. If the install of
the new product fails then the rollback will restore the old version.
If you use DIFxApp for driver installs then it needs to be put between
InstallValidate and InstallInitialize due to a bug in DIFxApp. In
that case a failed install of the new product but after the successful
uninstall of the old product will leave the computer with no product
installed at all.
I
think that must be a good place to put it if there are buggy custom
actions and component rules aren't being well-followed.
James
-Original Message-
From: Igor Lemsky [mailto:igor.lem...@gmail.com]
Sent: Tuesday, February 22, 2011 06:04
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Problem with RemoveExistingProducts action
I have upgrade scenario for my system from 2.0 version to 2.1 version.
I have file for example aaa.xml in 2.1 version and no such file in 2.0
version. It lies in independent component i feature Afeature (it was
in 2.0 also). During install there are no problems: file installs to
the right location. But during upgrade from 2.0 version it copies and then
deleted.
It seems that RemoveExistingProducts deletes it during uninstall of
older
2.0 product. It planned after InstallFinalize action (the most right
place as I understand).
Due to the log Installer unpublish features and the delete files...
MSI (s) (DC:B8) [11:54:05:148]: Executing op:
FileRemove(,FileName=aaa.xml,,ComponentId={369A88EA-F2DD-4124-9560-13E
5694E2
EEB})
RemoveFiles: File: aaa.xml, folder: C:\Mag\
I dont understand - what happened? Why it deletes files? May be I
didnt configured installer correctly? But how?
--
--
--
Index, Search Analyze Logs and other IT data in Real-Time with
Splunk Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical,
virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights.
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
[WiX-users] Problems applying patches
Hello all, I'm working with Liam who previously asked some patch related questions. ( http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-Using -Purely-Wix-td6031594.html ) We've made progress, with the comments to Liam's post, and by looking at http://blogs.msdn.com/b/pmarcu/archive/2008/05/30/patching-something-you-did nt-build-with-wix-using-wix-.aspx. However we're still unable to successfully patch our installation. We have two install packages: setup_32_unicode_new.msi and setup_32_unicode_old.msi, there is only 1 file (dyalog.exe, which I've changed from 6Mb to 15Mb) that is changed from old to new. Initially we're just trying to create a patch that will install that one modified file. Here's my patch xml: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; !-- Path variables -- Patch AllowRemoval = yes Manufacturer = Dyalog DisplayName = Dyalog APL 13.0 Patch Description = Dyalog APL 13.0 Patch Classification = Update Media Id=5000 Cabinet=RTM.cab PatchBaseline Id=RTM/ /Media PatchFamilyRef Id=Interpreter/ /Patch Fragment PatchFamily Id=Interpreter Supersede=yes Version=1.0.1.0 ComponentRef Id=dyalog.exe/ /PatchFamily /Fragment /Wix I use the following script to make the patch file: WIXDIR=c:/wix35/bin $WIXDIR/candle Patch.wxs $WIXDIR/light Patch.wixobj -out Patch/Patch.WixMsp msiexec -passive -norestart -l* inst_old.log TARGETDIR=c:\\tmp\\wix_patching\\dyalog\\inst_old -a setup_32_unicode_old.msi msiexec -passive -norestart -l* inst_new.log TARGETDIR=c:\\tmp\\wix_patching\\dyalog\\inst_new -a setup_32_unicode_new.msi $WIXDIR/torch -v -p -xo -a inst_old/setup_32_unicode_old.msi inst_new/setup_32_unicode_new.msi -out patch/diffs.wixmst $WIXDIR/pyro -v Patch/Patch.WixMsp -out Patch/Patch.msp -t RTM Patch/Diffs.wixmst I've used msix ( http://blogs.msdn.com/b/heaths/archive/2006/04/07/571138.aspx ) to extract the CAB from the MSP file and I can see that the only file in it is the modified binary that I expect to see. On a clean XP VM I install setup_32_unicode_old.msi, and then I apply the patch. However dyalog.exe remains the old version. If, however, I install setup_32_unicode_old.msi, then delete dyalog.exe, and then apply the patch I do get the new version. I've looked at the logs for the two applications of the patch, and the only significant difference seems to be the installation of the file, which isn't present unless I delete the file first: (without deleting dyalog.exe first) Action 14:28:51: InstallFiles. Copying new files Action 14:28:51: WriteRegistryValues. Writing system registry values (with deleting dyalog.exe first) Action 14:37:36: InstallFiles. Copying new files InstallFiles: File: dyalog.exe, Directory: C:\Program Files\Dyalog\Dyalog APL 13.0 Unicode\, Size: 15731712 Action 14:37:37: WriteRegistryValues. Writing system registry values What could we be doing wrong that prevents the installation of the new file if the old one exists? Many Thanks, John -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall an installed product.
What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burton kev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall an installed product.
Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall an installed product.
Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and
Re: [WiX-users] Uninstall an installed product.
Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver
Re: [WiX-users] Uninstall an installed product.
The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at
Re: [WiX-users] Uninstall an installed product.
Kevin, If you are doing Major upgrades, your product ID must for change whilst your Upgrade ID must remain the same. Chris On 02/25/2011 01:48 PM, Kevin Burton wrote: The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search
[WiX-users] The imported project .... Wix.CA.targets was not found
I'm doing a TFS 2008 build with wix 3.0 and I'm getting the error: SQLServerCustomAction.vbproj(101,11): error MSB4019: The imported project C:\Program Files\MSBuild\Microsoft\WiX\v3.0\Wix.CA.targets was not found. Confirm that the path in the Import declaration is correct, and that the file exists on disk. I saw the post on incorporating Wix into the build process. I followed that because I was having problems with the Wix.targets file. Once I incorporated the fix, that first problem went away and the build went through without problems. After a couple of builds .. I'm now getting the error on the wix.ca.targets files. Here is the contents of my project file: Project DefaultTargets=Build xmlns=http://schemas.microsoft.com/developer/msbuild/2003; PropertyGroup ... WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND '$(MSBuildExtensionsPath32)' != '' $(MSBuildExtensionsPath32)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath WixCATargetsPath Condition= '$(WixCATargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.CA.targets/WixCATargetsPath /PropertyGroup PropertyGroup WixToolPath$(SourceCodeControlRoot)\NiceWareProductDevelopment\TissueManagementSystem\WixInstallerToolsForBuild\/WixToolPath WixTargetsPath$(WixToolPath)Wix.targets/WixTargetsPath WixTasksPath$(WixToolPath)wixtasks.dll/WixTasksPath /PropertyGroup PropertyGroup WixToolPath$(SourceCodeControlRoot)\NiceWareProductDevelopment\TissueManagementSystem\WixInstallerToolsForBuild\/WixToolPath WixCATargetsPath$(WixToolPath)Wix.CA.targets/WixCATargetsPath WixTasksPath$(WixToolPath)wixtasks.dll/WixTasksPath /PropertyGroup Import Project=$(WixTargetsPath) / Import Project=$(WixCATargetsPath) / Any ideas ? -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
