[WiX-users] Executing CA after InstallFiles
I'm trying to execute CA after InstallFiles (I want to execute it after files are copied): lt;CustomAction Id=CABoxUpdate BinaryKey=AdditionsDLL DllEntry=BoxUpdate/gt; lt;InstallExecuteSequencegt; lt;Custom Action=CABoxUpdate After=InstallFilesgt;lt;![CDATA[(DFPOST4LINUX-1) AND NOT UPGRADINGPRODUCTCODE]]gt;lt;/Customgt; lt;/InstallExecuteSequencegt; But CA calling before files are installed, so CA cannot be executed correct. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Executing-CA-after-InstallFiles-tp6076921p6076921.html Sent from the wix-users mailing list archive at Nabble.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
[WiX-users] Authoring a patch to patch everything
Hello all (again), I'm attempting to author a patch that patches every file in a package. To begin with I started with a patch file that only patches some binary, versioned, components, and that seems to work: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Patch AllowRemoval = yes Classification = Update Media Id=5000 Cabinet=RTM.cab PatchBaseline Id=RTM/ /Media PatchFamily Id=ComponentsToPatch Supersede=yes Version=1.0.0.0 ?include ComponentsToPatch.wxi? /PatchFamily /Patch /Wix However I want to create a patch that will patch all changed files in the application. I'm sure I read somewhere (but I can't find the link now), that if I had no children in the PatchFamily element that it would include all changes in the patch. However, if I comment out (or remove) the include of ComponentsToPatch.wxi I get a PYRO error: error PYRO0103 : The system cannot find the file 'c:\tmp\a3pbt24c\patch.msp'. I can probably auto-create a full list of ComponentRefs from the install package to add to the PatchFamily if necessary, but I thought there'd be a slicker way. How does one author a patch to patch all files? 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
[WiX-users] merge modules and upgrade best practice
Hi. I have a msm merge module that are used across different products in different installers (all made with WiX 3+ (the msm is created with 3.5)) I need to provide a way that ensure this msm can only be updated with a higher version. As it is today this is not enforced and I am looking for a best practice for doing this. Is this best made with creating a custom action that that do: 1) read a regkey for version 2) if version is higher cancel installation else install 3) write new version to regkey can it be done within Upgrade elements in the wxs file or is there some documentation on this I have missed? Thanks, /eske -- 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] Executing CA after InstallFiles
The customaction needs Execute=deferred or it will execute while the script is being generated. -Original Message- From: vunder [mailto:vun...@bk.ru] Sent: 01 March 2011 11:47 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Executing CA after InstallFiles I'm trying to execute CA after InstallFiles (I want to execute it after files are copied): lt;CustomAction Id=CABoxUpdate BinaryKey=AdditionsDLL DllEntry=BoxUpdate/gt; lt;InstallExecuteSequencegt; lt;Custom Action=CABoxUpdate After=InstallFilesgt;lt;![CDATA[(DFPOST4LINUX-1) AND NOT UPGRADINGPRODUCTCODE]]gt;lt;/Customgt; lt;/InstallExecuteSequencegt; But CA calling before files are installed, so CA cannot be executed correct. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Executing-CA-af ter-InstallFiles-tp6076921p6076921.html Sent from the wix-users mailing list archive at Nabble.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 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. -- 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] Error 1723
Yea, and the million dollar question is, which dll is missing? The exact error message I get is: MSI (c) (C0:1C) [10:18:19:335]: Note: 1: 1723 2: caStripCharsFromNetworkPort 3: StripExtraCharsFromRegSearchValue 4: C:\DOCUME~1\ADMINI~1.LAB\LOCALS~1\Temp\MSI151.tmp Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action caStripCharsFromNetworkPort, entry: StripExtraCharsFromRegSearchValue, library: C:\DOCUME~1\ADMINI~1.LAB\LOCALS~1\Temp\MSI151.tmp MSI (c) (C0:1C) [10:18:20:664]: Product: Email Management Services -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action caStripCharsFromNetworkPort, entry: StripExtraCharsFromRegSearchValue, library: C:\DOCUME~1\ADMINI~1.LAB\LOCALS~1\Temp\MSI151.tmp This custom action is a managed assembly. I unpacked the MSI and CAB and pointed .NET reflector at the assembly and all its references were found. I set the fusion log to log while running the MSI and it doesn't report any errors. I ran msiexec within a WinDBG session and didn't get any module load failures. Does anyone have tips on how do debug this type or issue? Or basically any debugging related to WiX/MSI? How can the wixpdb files be used? Thanks for the reply, I know you didn't write WiX though I've had an easier time debugging hex machine code than the WiX/MSI process. Message: 6 Date: Thu, 24 Feb 2011 11:05:01 +0200 From: Dan Vasilov d...@rms.ro Subject: Re: [WiX-users] Error 1723 To: 'General discussion for Windows Installer XML toolset.' wix-users@lists.sourceforge.net Message-ID: 02fc01cbd401$eb598740$c20c95c0$@ro Content-Type: text/plain; charset=us-ascii It is very likely the .dll is not included in the MSI package at build. Another possibility is the .dll is missing some dependent .dll files. -Original Message- From: Colin LeMahieu [mailto:clemah...@gmail.com] Sent: Wednesday, February 23, 2011 7:26 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 1723 I'm getting this error on startup for an MSI that previously worked. Are there any tips for debugging this error? Is it unreasonable to expect the name of the offending DLL or some way to attach a debugger to an MSI while installing? -- -- 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.
I would personally leave of Package/@Id and and set Product/@Id to *. Or if you really want to set Package/@Id then set it to *. Product Id=* ... Package Id=* ... / /Product Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 10:48 AM To: General discussion for Windows Installer XML toolset. Subject: 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
Re: [WiX-users] Setup asks for rebooting after change/repair options.
You can also look at the Multi-String value in the registry called PendingFileRenameOperation at the following location to see which files the system has earmarked for change. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setup-asks-for-rebooting-after-change-repair-options-tp6059508p6077825.html Sent from the wix-users mailing list archive at Nabble.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] Executing CA after InstallFiles
http://wix.sourceforge.net/manual-wix2/wix_xsd_customaction.htm This page says that if you do not have the Execute item explicitly listed in CustomAction, it defaults to immediate. I believe what you are looking for is this: lt;CustomAction Id=CABoxUpdate BinaryKey=AdditionsDLL DllEntry=BoxUpdate Execute=deferred/gt; -Original Message- From: vunder [mailto:vun...@bk.ru] Sent: Tuesday, March 01, 2011 5:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Executing CA after InstallFiles I'm trying to execute CA after InstallFiles (I want to execute it after files are copied): lt;CustomAction Id=CABoxUpdate BinaryKey=AdditionsDLL DllEntry=BoxUpdate/gt; lt;InstallExecuteSequencegt; lt;Custom Action=CABoxUpdate After=InstallFilesgt;lt;![CDATA[(DFPOST4LINUX-1) AND NOT UPGRADINGPRODUCTCODE]]gt;lt;/Customgt; lt;/InstallExecuteSequencegt; But CA calling before files are installed, so CA cannot be executed correct. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Executing- CA-after-InstallFiles-tp6076921p6076921.html Sent from the wix-users mailing list archive at Nabble.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
