[WiX-users] When to call CustomAction
Hi, If you include in your installation some IIS configuration then WIX framework adds ConfigureIIS action to the sequence. You can do the following: 1. You specify after ConfigureIIS in your action. 2. You can add ConfigureIIS action to your InstallExecuteSequence in any place after InstallFiles standard action. Also you can define any condition on ConfigureIIS action (we set condition NOT PATCH because during patch WEB site exists already). 3. In general you can add Web.config configuration after InstallFiles action because the file configuration depends on file existence only and not on presence of Web Site or Virtual Folder. 4. You can use WIX Utils extension to configure XML files unless you doing something that is out of scope of XML standards. Regards -- Forwarded message -- From: Brian Enderle bria...@gmail.com To: WiX Users wix-users@lists.sourceforge.net Cc: Date: Tue, 21 Oct 2014 13:23:33 -0400 Subject: [WiX-users] When to call CustomAction I am trying to run a CA after setting up a website to modify the web.config file based on the IIS version being used. What should I use for the After value (in the InstallExecuteSequence) to make sure the CustomAction executes after the website is installed? Here is the code I am using: Product ... InstallExecuteSequence !-- Only execute on install (not repair or uninstall) -- Custom Action='WebConfigProperties' After='InstallServices'NOT Installed AND NOT REMOVE/Custom Custom Action='UpdateWebConfig' After='WebConfigProperties'NOT Installed AND NOT REMOVE/Custom /InstallExecuteSequence /Product !-- Includes setup info for installing IIS information -- Fragment !-- Create a component group so we only have to make one reference in Product.wxs -- ComponentGroup Id=IISConfiguration ComponentRef Id=InstallWebsite / ComponentRef Id=InstallAppPool / /ComponentGroup !-- Get username / password from AcctInfoDlg.wxs -- !--util:User Id=WebAppPoolUser Name=[IISSERVICEACCOUNT] Password=[IISPASSWORD] /util:User-- DirectoryRef Id=INSTALLFOLDER_FOXPROCONNECTWS !-- Setup application pool information using IISSERVICEACCOUNT from AcctInfoDlg.wxs -- Component Id=InstallAppPool Guid=$(var.AppPoolGUID) KeyPath=yes iis:WebAppPool Id=FoxProConnectWS Name=FoxProConnectWS Identity=applicationPoolIdentity ManagedPipelineMode=Integrated ManagedRuntimeVersion=v4.0 / /Component !-- Create the website in IIS -- Component Id=InstallWebsite Guid=$(var.WebsiteGUID) KeyPath=yes iis:WebVirtualDir Id=WebSiteVirtualDir Alias=FoxProConnectWS Directory=INSTALLFOLDER_FOXPROCONNECTWS WebSite=FoxProWebsite iis:WebApplication Id=WebSiteApp Name=FoxProConnectWS Isolation=medium WebAppPool=FoxProConnectWS / /iis:WebVirtualDir /Component /DirectoryRef !-- These 'website's are defined outside of the 'DirectoryRef' so as to create the websites under the 'Default Web Site' entry in IIS -- iis:WebSite Id=FoxProWebsite Description=FoxProConnectWS Directory=INSTALLFOLDER_FOXPROCONNECTWS iis:WebAddress Id=AllUnassigned Port=80 / /iis:WebSite Binary Id=CustomAction.CA SourceFile=$(var.SolutionDir)CustomActions\bin\$(var.Configuration)\CustomActions.CA.dll / CustomAction Id=WebConfigProperties Return=check Property=UpdateWebConfig Value=FoxProConnectWSPath=[INSTALLFOLDER_FOXPROCONNECTWS];FoxProPath=[FOXPROPATH] / CustomAction Id=UpdateWebConfig BinaryKey=CustomAction.CA DllEntry=UpdateWebConfigCustomAction Execute=deferred Impersonate=no Return=check / /Fragment Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein -- Regards, Fyodor Koryazhkin.. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] MSI won't install on XP
Hi,
The key error from the log file is:
Error 1906. Failed to cache package C:\WINDOWS\Installer\1377ad.msi. Error:
-2147287038.
More possibly this indicates some system error:
1. There is some error with XP image you use (try to install on other XP
computer that has different image i.e. do not use virtual machine or GOST
that were created from the same source image)
2. If you install from local package there could be some error during copy
(try to copy again to different location or run it from network)
3. If you install from network there can be some interruption in network
communication (try to copy installation package locally).
4. Check disk space on system disk (before installation you have to have
free disk space at least 3 times larger than your package because you have
embedded cab). Exact calculation of free disk space needed to start and
finish installation is: Size of product + Size of Package(for cached
msi) + Size of Package(for temporary msi work - this will be released
after installation) + Some free space for System work(depends on system
configuration) If you run upgrade then the required free space rises twice
(to store temporary rollback data).
5. Examine C:\windows\installer folder (permissions, ability to copy files
manually, etc.)
Regards
Fyodor Koryazhkin
-- Forwarded message --
From: Christopher Fraser chr...@goop.org
To: wix-users@lists.sourceforge.net
Cc:
Date: Tue, 21 Oct 2014 23:09:35 +0200
Subject: [WiX-users] MSI won't install on XP
Hello,
When I try and install my MSI on XP I get an error code 2260. I works just
fine on Windows 7 and 8. Any ideas?
From the msiexec log:
MSI (s) (44:DC) [19:13:57:281]: Executing op: ActionStart(Name=
RegisterProduct,Description=Registering product,Template=[1])
Action 19:13:57: RegisterProduct. Registering product
MSI (s) (44:DC) [19:13:57:281]: Executing op: ChangeMedia(,MediaPrompt=Please
insert the disk: USB Debugging Driver 1.0.2 Installation,MediaCabinet=
disk1.cab,BytesPerTick=0,CopierType=2,ModuleFileName=C:
\WINDOWS\Installer\1377ad.msi,IsFirstPhysicalMedia=1)
MSI (s) (44:DC) [19:13:57:281]: Executing op: DatabaseCopy(DatabasePath=C:\
WINDOWS\Installer\1377ad.msi,ProductCode={B61F9010-3474-
11E4-8C21-0800200C9A66},CabinetStreams=disk1.cab,,)
MSI (s) (44:DC) [19:13:57:281]: Note: 1: 1402 2: UNKNOWN\Products\
0109F16B47434E11C81282C0A966\InstallProperties 3: 2
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2260 2: 3: -2147287038
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2205 2: 3: Error
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2260
DEBUG: Error 2260: Storage CopyTo failed. System error: -2147287038
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2260. The
arguments are: , -2147287038,
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 1906 2:
C:\WINDOWS\Installer\1377ad.msi 3: -2147287038
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2205 2: 3: Error
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1906
MSI (c) (CC:84) [19:13:57:296]: Note: 1: 2205 2: 3: Error
MSI (c) (CC:84) [19:13:57:296]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2888
DEBUG: Error 2888: Executing the Binary view failed
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2888. The
arguments are: Binary, ,
Error 1906. Failed to cache package C:\WINDOWS\Installer\1377ad.msi.
Error: -2147287038. Contact your support personnel.
MSI (s) (44:DC) [19:14:31:015]: Note: 1: 2205 2: 3: Error
MSI (s) (44:DC) [19:14:31:015]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (44:DC) [19:14:31:015]: Product: USB Debugging Driver -- Error
1906. Failed to cache package C:\WINDOWS\Installer\1377ad.msi. Error: -
2147287038. Contact your support personnel.
MSI (s) (44:DC) [19:14:31:031]: Note: 1: 2205 2: 3: Error
MSI (s) (44:DC) [19:14:31:031]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1602
MSI (c) (CC:84) [19:14:31:031]: Note: 1: 2205 2: 3: Error
MSI (c) (CC:84) [19:14:31:031]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2888
DEBUG: Error 2888: Executing the Binary view failed
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2888. The
arguments are: Binary, ,
Are you sure you want to cancel?
Action ended 19:14:32: InstallFinalize. Return value 3.
The .wxs:
?xml version='1.0' encoding='windows-1252'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
xmlns:difx='http://schemas.microsoft.com/wix/DifxAppExtension'
?define ProductCode=b61f9010-3474-11e4-8c21-0800200c9a66 ?
Re: [WiX-users] Burn - Checkbox on Modify Page
Hi everyone, has there been a feature-request for this topic yet? It seems that one can still not search the issue-database... Best regards, Tobias Von: Neil Sleightholm [n...@x2systems.com] Gesendet: Dienstag, 22. April 2014 08:11 Bis: General discussion about the WiX toolset. Betreff: Re: [WiX-users] Burn - Checkbox on Modify Page Out of the box that isn't possible. If you start with the extended BA http://wixextba.codeplex.com/ (WiX 3.8 is basically the same code as this) you could modify OnChangeState() and OnClickRepairButton() to support this function. Neil -Original Message- From: Shannon Cornish [mailto:shan...@shannoncornish.com] Sent: 22 April 2014 05:01 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Burn - Checkbox on Modify Page Hi, I would like to add a checkbox to the Modify page of my Burn project and have that value be passed into the MSI file. I have added a Variable element as a Bundle child and a checkbox to the 'Modify' page of my burn application using a custom theme (based on the RTF License theme). I also have used an MsiProperty element to pass this value to the MSI. The issue is that the checkbox on the modify page does not bind to the variable. If I move the checkbox to the 'Options' page it does bind to the variable. I would like to have the option on the 'Modify' page to allow the user to remove settings files during installation (via a custom action in the MSI). Thanks in advance! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Checkbox-on-Modify-Page-tp7594244.html Sent from the wix-users mailing list archive at Nabble.com. -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI won't install on XP
Hi Fyodor,
Thanks for this. I'm starting to think it's a privilege issue. Looking
at the installer now I see that on platforms newer than XP I run:
elevate msiexec /i
On Windows XP this wasn't working so I disabled it. I'll see if I can
get elevate working on XP.
Christopher.
On 22/10/14 08:46, Fyodor Koryazhkin wrote:
Hi,
The key error from the log file is:
Error 1906. Failed to cache package C:\WINDOWS\Installer\1377ad.msi. Error:
-2147287038.
More possibly this indicates some system error:
1. There is some error with XP image you use (try to install on other XP
computer that has different image i.e. do not use virtual machine or GOST
that were created from the same source image)
2. If you install from local package there could be some error during copy
(try to copy again to different location or run it from network)
3. If you install from network there can be some interruption in network
communication (try to copy installation package locally).
4. Check disk space on system disk (before installation you have to have
free disk space at least 3 times larger than your package because you have
embedded cab). Exact calculation of free disk space needed to start and
finish installation is: Size of product + Size of Package(for cached
msi) + Size of Package(for temporary msi work - this will be released
after installation) + Some free space for System work(depends on system
configuration) If you run upgrade then the required free space rises twice
(to store temporary rollback data).
5. Examine C:\windows\installer folder (permissions, ability to copy files
manually, etc.)
Regards
Fyodor Koryazhkin
-- Forwarded message --
From: Christopher Fraser chr...@goop.org
To: wix-users@lists.sourceforge.net
Cc:
Date: Tue, 21 Oct 2014 23:09:35 +0200
Subject: [WiX-users] MSI won't install on XP
Hello,
When I try and install my MSI on XP I get an error code 2260. I works just
fine on Windows 7 and 8. Any ideas?
From the msiexec log:
MSI (s) (44:DC) [19:13:57:281]: Executing op: ActionStart(Name=
RegisterProduct,Description=Registering product,Template=[1])
Action 19:13:57: RegisterProduct. Registering product
MSI (s) (44:DC) [19:13:57:281]: Executing op: ChangeMedia(,MediaPrompt=Please
insert the disk: USB Debugging Driver 1.0.2 Installation,MediaCabinet=
disk1.cab,BytesPerTick=0,CopierType=2,ModuleFileName=C:
\WINDOWS\Installer\1377ad.msi,IsFirstPhysicalMedia=1)
MSI (s) (44:DC) [19:13:57:281]: Executing op: DatabaseCopy(DatabasePath=C:\
WINDOWS\Installer\1377ad.msi,ProductCode={B61F9010-3474-
11E4-8C21-0800200C9A66},CabinetStreams=disk1.cab,,)
MSI (s) (44:DC) [19:13:57:281]: Note: 1: 1402 2: UNKNOWN\Products\
0109F16B47434E11C81282C0A966\InstallProperties 3: 2
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2260 2: 3: -2147287038
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2205 2: 3: Error
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2260
DEBUG: Error 2260: Storage CopyTo failed. System error: -2147287038
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2260. The
arguments are: , -2147287038,
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 1906 2:
C:\WINDOWS\Installer\1377ad.msi 3: -2147287038
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2205 2: 3: Error
MSI (s) (44:DC) [19:13:57:296]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1906
MSI (c) (CC:84) [19:13:57:296]: Note: 1: 2205 2: 3: Error
MSI (c) (CC:84) [19:13:57:296]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2888
DEBUG: Error 2888: Executing the Binary view failed
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2888. The
arguments are: Binary, ,
Error 1906. Failed to cache package C:\WINDOWS\Installer\1377ad.msi.
Error: -2147287038. Contact your support personnel.
MSI (s) (44:DC) [19:14:31:015]: Note: 1: 2205 2: 3: Error
MSI (s) (44:DC) [19:14:31:015]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (44:DC) [19:14:31:015]: Product: USB Debugging Driver -- Error
1906. Failed to cache package C:\WINDOWS\Installer\1377ad.msi. Error: -
2147287038. Contact your support personnel.
MSI (s) (44:DC) [19:14:31:031]: Note: 1: 2205 2: 3: Error
MSI (s) (44:DC) [19:14:31:031]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1602
MSI (c) (CC:84) [19:14:31:031]: Note: 1: 2205 2: 3: Error
MSI (c) (CC:84) [19:14:31:031]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2888
DEBUG: Error 2888: Executing the Binary view failed
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2888.
Re: [WiX-users] When to call CustomAction
Thank you, didn't think about WiX having that functionality. However, I am having an issue with adding a brand new node. I need to add the following under //configuration/system.webServer/handlers/add add name=svc-Integrated verb=* path=*.svc preCondition=integratedMode type=System.ServiceModel.Activation.HttpHandler/ I have tried the following but nothing is being created (I also tried this without the condition but still no luck): Component Id=UpdateWebConfigForIIS8 Guid=3DB3C8CE-7271-4505-83E8-F83A67011DC4 Directory=INSTALLFOLDER_FOXPROCONNECTWS Condition![CDATA[IIS_MAJOR_VERSION = #8]]/Condition CreateFolder / util:XmlConfig Id=UpdateHandlers Action=create File=[#WebConfig] ElementPath=//configuration/system.webServer/handlers/add Name=name Value=svc-Integrated Sequence=2 / util:XmlConfig Id=UpdateHandlerVerb Action=create File=[#WebConfig] ElementPath=//configuration/system.webServer/handlers/add[\[]@name='svc-Integrated'[\]]/verb Value=* Sequence=3 / util:XmlConfig Id=UpdateHandlerPath Action=create File=[#WebConfig] ElementPath=//configuration/system.webServer/handlers/add[\[]@name='svc-Integrated'[\]]/path Value=*.svc Sequence=4 / util:XmlConfig Id=UpdateHandlerPreCondition Action=create File=[#WebConfig] ElementPath=//configuration/system.webServer/handlers/add[\[]@name='svc-Integrated'[\]]/preCondition Value=integratedMode Sequence=5 / util:XmlConfig Id=UpdateHandlerType Action=create File=[#WebConfig] ElementPath=//configuration/system.webServer/handlers/add[\[]@name='svc-Integrated'[\]]/type Value=System.ServiceModel.Activation.HttpHandler Sequence=6 / /Component Can someone give me an example that I can work with? Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein On Tue, Oct 21, 2014 at 1:30 PM, John Cooper jocoo...@jackhenry.com wrote: Why are you re-inventing the wheel? Util:XmlFile and Util:XmlConfig are quite serviceable and give you full rollback support. Scheduling depends. There's no one magic value. Since you should be using a deferred action, you'll be limited to the range after CostFinalize to before InstallFinalize. The file must exist before you can edit it, so InstallFiles will need to have been run first. That leaves you after InstallFiles to before InstallFinalize. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | jocoo...@jackhenry.com -Original Message- From: Brian Enderle [mailto:bria...@gmail.com] Sent: Tuesday, October 21, 2014 12:24 PM To: WiX Users Subject: [WiX-users] When to call CustomAction I am trying to run a CA after setting up a website to modify the web.config file based on the IIS version being used. What should I use for the After value (in the InstallExecuteSequence) to make sure the CustomAction executes after the website is installed? Here is the code I am using: Product ... InstallExecuteSequence !-- Only execute on install (not repair or uninstall) -- Custom Action='WebConfigProperties' After='InstallServices'NOT Installed AND NOT REMOVE/Custom Custom Action='UpdateWebConfig' After='WebConfigProperties'NOT Installed AND NOT REMOVE/Custom /InstallExecuteSequence /Product !-- Includes setup info for installing IIS information -- Fragment !-- Create a component group so we only have to make one reference in Product.wxs -- ComponentGroup Id=IISConfiguration ComponentRef Id=InstallWebsite / ComponentRef Id=InstallAppPool / /ComponentGroup !-- Get username / password from AcctInfoDlg.wxs -- !--util:User Id=WebAppPoolUser Name=[IISSERVICEACCOUNT] Password=[IISPASSWORD] /util:User-- DirectoryRef Id=INSTALLFOLDER_FOXPROCONNECTWS !-- Setup application pool information using IISSERVICEACCOUNT from AcctInfoDlg.wxs -- Component Id=InstallAppPool Guid=$(var.AppPoolGUID) KeyPath=yes iis:WebAppPool Id=FoxProConnectWS Name=FoxProConnectWS Identity=applicationPoolIdentity ManagedPipelineMode=Integrated ManagedRuntimeVersion=v4.0 / /Component !-- Create the website in IIS -- Component Id=InstallWebsite Guid=$(var.WebsiteGUID) KeyPath=yes iis:WebVirtualDir Id=WebSiteVirtualDir Alias=FoxProConnectWS
[WiX-users] Return to Dialog Screen on Custom Action Error
I have a Custom Action that checks that a directory path entered by the user is valid. I would like to return to the setup screen which contains the 'Directory Path' edit box if the path is invalid (ActionResult.Failure). Can this be done? Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Return to Dialog Screen on Custom Action Error
It is done in the default InstallDirDlg and support code. Take a look at that code in the Wix source. That pattern can be used to chain-in whatever custom actions you need for validation. It's kludgy, but that is dictated by the way the Windows Installer Service implement UI elements. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Brian Enderle [mailto:bria...@gmail.com] Sent: Wednesday, October 22, 2014 8:18 AM To: WiX Users Subject: [WiX-users] Return to Dialog Screen on Custom Action Error I have a Custom Action that checks that a directory path entered by the user is valid. I would like to return to the setup screen which contains the 'Directory Path' edit box if the path is invalid (ActionResult.Failure). Can this be done? Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI won't install on XP
There is no Elevate on XP, There is a Run As User Option where you can choose the Local Administrator. Your best option here would be to package 2 MSI's, one for XP, without Elevated Privileges, and on for = Vista with Elevated Privileges. Quoting Christopher Fraser chr...@goop.org: Hi Fyodor, Thanks for this. I'm starting to think it's a privilege issue. Looking at the installer now I see that on platforms newer than XP I run: elevate msiexec /i On Windows XP this wasn't working so I disabled it. I'll see if I can get elevate working on XP. Christopher. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] PatchProperty setting
I believe I need to set a property during a patch. Feel free to disprove me as I am new to WIX Patches and think I know what I am doing ( Ha! ) Ok, I am patching an installation that someone else created. I have two sets of files , Server and Client When I attempt to install a patch to the Client, my shortcuts to the product, and a registry entry are getting messed up. So I am thinking that a property used by the client install to create the shortcuts is NOT being set by the patch install, thus they are getting messed up. So How do I set a PatchProperty based on a registry entry? This is OK PatchProperty Name=PARENTPATH Value=[PARENTDIR]\MSDynamicsSL.exe / This gets an error in candle.exe PatchProperty Name=SLAPPLICATIONSDIR RegistrySearch Id=SLApplicationsRegistry Type='directory' Root='HKLM' Key='$(var.DynamicsSL_RegKey)' Name='$(var.ParentDirectory_RegName)' / /PatchProperty -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Return to Dialog Screen on Custom Action Error
In looking at InstallDirDlg I don't see anything that would return control to the dialog on an error. I am not sure what support code to look at. Can you tell me what I should look at? Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein On Wed, Oct 22, 2014 at 9:23 AM, John Cooper jocoo...@jackhenry.com wrote: It is done in the default InstallDirDlg and support code. Take a look at that code in the Wix source. That pattern can be used to chain-in whatever custom actions you need for validation. It's kludgy, but that is dictated by the way the Windows Installer Service implement UI elements. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | jocoo...@jackhenry.com -Original Message- From: Brian Enderle [mailto:bria...@gmail.com] Sent: Wednesday, October 22, 2014 8:18 AM To: WiX Users Subject: [WiX-users] Return to Dialog Screen on Custom Action Error I have a Custom Action that checks that a directory path entered by the user is valid. I would like to return to the setup screen which contains the 'Directory Path' edit box if the path is invalid (ActionResult.Failure). Can this be done? Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Unable to get install button to enable
I was looking for the wrong Id in the detect routine. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unable-to-get-install-button-to-enable-tp7597419p7597433.html Sent from the wix-users mailing list archive at Nabble.com. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Return to Dialog Screen on Custom Action Error
Take a look at code similar to this (this may or may not come through): Publish Dialog=InstallDirDlg Control=Next Event=DoAction Value=WixUIValidatePath Order=2NOT WIXUI_DONTVALIDATEPATH/Publish Publish Dialog=InstallDirDlg Control=Next Event=SpawnDialog Value=InvalidDirDlg Order=3![CDATA[NOT WIXUI_DONTVALIDATEPATH AND WIXUI_INSTALLDIR_VALID1]]/Publish Publish Dialog=InstallDirDlg Control=Next Event=NewDialog Value=VerifyReadyDlg Order=4WIXUI_DONTVALIDATEPATH OR WIXUI_INSTALLDIR_VALID=1/Publish 1) The DoAction attribute causes the WixUIValidatePath custom action to be called (the validation can be suppressed by defining the WIXUI_DONTVALIDATEPATH property; 2) WixUIValidatePath sets a property, WIXUI_INSTALLDIR_VALID; 3) If the path is not valid, InvalidDirDlg is displayed; 4) If the path is valid, the next dialog in sequence, VerifyReadyDlg, is displayed; -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Brian Enderle [mailto:bria...@gmail.com] Sent: Wednesday, October 22, 2014 9:45 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Return to Dialog Screen on Custom Action Error In looking at InstallDirDlg I don't see anything that would return control to the dialog on an error. I am not sure what support code to look at. Can you tell me what I should look at? Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein On Wed, Oct 22, 2014 at 9:23 AM, John Cooper jocoo...@jackhenry.com wrote: It is done in the default InstallDirDlg and support code. Take a look at that code in the Wix source. That pattern can be used to chain-in whatever custom actions you need for validation. It's kludgy, but that is dictated by the way the Windows Installer Service implement UI elements. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | jocoo...@jackhenry.com -Original Message- From: Brian Enderle [mailto:bria...@gmail.com] Sent: Wednesday, October 22, 2014 8:18 AM To: WiX Users Subject: [WiX-users] Return to Dialog Screen on Custom Action Error I have a Custom Action that checks that a directory path entered by the user is valid. I would like to return to the setup screen which contains the 'Directory Path' edit box if the path is invalid (ActionResult.Failure). Can this be done? Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying,
Re: [WiX-users] Return to Dialog Screen on Custom Action Error
Hi, You could make a clone of the dialog where u want to return to. On a button click execute the CA and set a public property there if directory is valid. then goto new dialog if property is set otherwise goto cloned dialog . execute CA after button click from clone dialog. check for property . go back to original dialog if property is nt set(invalid directory). Its kind of toggle between two dialogues based on property value. Regards, Sampat -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Return-to-Dialog-Screen-on-Custom-Action-Error-tp7597427p7597439.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Addressing download failures in Burn driven MSI
I have continued to research this issue (between local network disruptions).
While I have done many experiments to try and understand a rare download
failure of a 90mb payload cab file, I have focused on Rob's comment about
Burn's use of http being reliable 'with retries' (in contrast to BITS). I
originally used the WixBA as a template for creating my mba. So my
ResolveSource is similar to the WixBA ResolveSource, in regard to the
retries code.
private void ResolveSource(object sender, ResolveSourceEventArgs e)
{
int retries = 0;
this.downloadRetries.TryGetValue(e.PackageOrContainerId, out
retries);
this.downloadRetries[e.PackageOrContainerId] = retries + 1;
e.Result = retries 3
!String.IsNullOrEmpty(e.DownloadSource) ? Result.Download : Result.Ok;
}
When I review many logs, both successful and with download failures, I do
not see any evidence that there is any retry. I added log messages and
observed that when a package has more than one item the first retry
(retries==0) is the msi, the second retry (retires==1) is the next payload,
the third retry is the next payload, and if there are more payloads the
whole install fails. If any one of these downloads fails, say the msi
download fails while retries==0, then the whole setup fails without any
'retries'. By changing the above two lines in ResolveSource to use
e.PayloadId, I resolved this latter problem, since when the msi package is
downloaded both e.PackageOrContainerId and e.PayloadId are the same value.
(I don't know if this would be the case for a container.)
The problem with the 90 mb cab file failing to download happens rarely but I
do not think that issue is addressed by this change. I did not find a way
to increase the failure rate yet. When I severely restrict bandwidth in the
virtual switch or memory it seems to be less likely to fail. I have been
experimenting with adding retry code in CachePackageComplete, which based on
one experiment seems promising. I also looked at CacheVerifyComplete and
CacheAquireComplete.
Is the use of e.PackageOrContainerId rather than e.PayloadId a bug in WixBA?
(or maybe something that does not matter as long as WixBA does not have any
packages with more than two payloads.)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Addressing-download-failures-in-Burn-driven-MSI-tp7597272p7597443.html
Sent from the wix-users mailing list archive at Nabble.com.
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
