Re: [WiX-users] Patch issue
Its true. But in this case we want this component(file not getting patched) to follow a parent which is getting patched. You need to try this and do a thorough testing of all the scenarios. There is also a other way of tackling this situation, the point is the value in file version field(in the msi cache) which is removed after application of the mst should come back before applying the patch. To get the value back apply another mst and write the value (may be doing a reinstall, so this would re-cache the msi. You need to pass the correct mst via the TRANSFORM property). This needs to be tested. -Original Message- From: Uma Harano [mailto:uhar...@esri.com] Sent: Tuesday, October 16, 2012 10:01 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patch issue I read in the SDK that the companion file cannot be the key path of the component. In my case, the file that I want to be a companion file (the one that is not getting patched) is key path file. So I cannot make it a companion file, correct? -Original Message- From: Kajal Kumar Biswas [mailto:kbis...@adobe.com] Sent: Monday, October 15, 2012 5:42 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patch issue You could try making it a companion file in your patch. So, the installation state of a companion file depends not on its own file version, but on the version of its companion parent. Hence the mst removing the version no. will become ineffective. -Original Message- From: Uma Harano [mailto:uhar...@esri.com] Sent: Monday, October 15, 2012 5:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patch issue Hi Kajal Thank you for your email. Unfortunately the mst has already been released to our customers. We are now trying to release the msp patch and it is not patching the file. So we are trying to see how we can now fix the problem (so that the msp updates the file correctly) caused by the released mst. Thanks Uma- -Original Message- From: Kajal Kumar Biswas [mailto:kbis...@adobe.com] Sent: Sunday, October 14, 2012 10:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patch issue When the mst is applied, the msi cache is not updated with the file version at the end of the installation and hence during patching the file is not updated. What you can do this try creating the mst correctly, such that it does not update the file version in the file table. Can you let me know how exactly you are trying to create the mst file? -Original Message- From: Uma Harano [mailto:uhar...@esri.com] Sent: Sunday, October 14, 2012 3:52 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Patch issue Hi I have a patching issue I need help with. Version 10.1 of my msi installs a dll with version 10.1.0. This is the also the version listed in the File table of the msi for this dll. This msi is the English setup. I have embedded msts in this msi that localizes the dialogs for this msi. There was a problem with this mst, so when this mst is applied over the setup msi, the version of this dll in the File table is removed. (The dll installed on the machine is OK, it is just the File table of the msi that has the version removed when you apply the mst). I now have an msp for this Version 10.1 that increments the dll to 10.1.1. I am finding that when the localized msi is installed (with the mst that removes the file version in the file table), and when the msp is applied over this, the dll is not patched. How can I fix the msp so that the file is successfully patched in this scenario? Thanks! Uma Harano -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't let slow site performance ruin your business. Deploy New
Re: [WiX-users] ActionData to show file names
Hi Jacob, That is what I had tried but I get the error that InstallFiles is a duplicate primary key. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: 16 October 2012 16:51 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ActionData to show file names This might help as a starting point: http://wix.tramontana.co.hu/tutorial/user-interface-revisited/is-this-progre ss ... ProgressText Action=InstallFiles Template=File: [1], Directory: [9], Size: [6]Copying new files/ProgressText ... Control Id=ActionData Type=Text X=59 Y=165 Width=273 Height=41 Transparent=yes TabSkip=no Subscribe Event=ActionData Attribute=Text / /Control A while back I found the some of the parameters documented on MSDN, but I can't seem to find it today. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: Tuesday, October 16, 2012 10:12 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] ActionData to show file names No problem Steve, I will post when I have it working. Messing around with it now to try to get it working..:) -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 16 October 2012 15:53 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ActionData to show file names Hi Natalie, When you get that working I would love to see the code (that would be something I would be interested in seeing in my install as well) Steve -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: October-16-12 10:39 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] ActionData to show file names Hi, I want to show each file that is getting installed I used the actiondata control: Control Id=ActionData Type=Text X=70 Y=100 Width=285 Height=10 Subscribe Event=ActionData Attribute=Text //Control It shows the full file and directory but I would only like it to show the file. Is this possible? I am also installing a service that's name is a property found at install time, however when I changed this it gave the DisplayName as the literal property name. Kind Regards, Natalie Carr -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FW: Patch installation asks for a reboot
Have you anything referencing the fragment that the installexecutesequence is in ? There is no installexecutesequenceRef element so you'll need some way to tell Wix to include the new sequence in the patch. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 17 October 2012 03:09 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] FW: Patch installation asks for a reboot Hi, There is still one more problem. I thought if I change the install execute sequence in the target msi, that will be picked up by the msp. However when I drop the msp on the base msi in Orca tool I do not see any change in the install sequence. All the new components that I have added, modified seem to be there in the tables - basically I can see all other changes that I have made in the patch except for the install execute sequence change. Can you please provide some idea as to what might be happening here? Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, October 16, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patch installation asks for a reboot A patch works by transforming the installed and cached MSI with the patch and then running a repair on the resulting MSI. That's why you see the MSI apparently installing again. Altering the condition to NOT REMOVE AND NOT PATCH in the patch sounds like a reasonable fix, if you're certain that the condition that required the reboot won't occur again. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 16 October 2012 11:23 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Patch installation asks for a reboot Hi, We are creating a patch on top of already shipped product. In the product msi we schedule a reboot like ScheduleReboot sequence=AfterInstallFinalizeNOT REMOVE/ScheduleReboot It appears while installing the patch which targets the above msi, it reruns the msi and a reboot gets scheduled. Is there any way we can avoid the ScheduleReboot while installing the patch? Will changing the schedule reboot condition in product msi to something like *NOT REMOVE AND NOT PATCH* or, *NOT REMOVE AND NOT OLDERPRODUCTFOUND* help? While re-running the msi installsequence does the patch pick up the actions from already installed msi i.e is it runtime event? Or, the msi installsequence run by the patch is determined at compile time (I.e. if I change the condition for reboot in the product msi will it be honored by the patch)? Regards Abhijit -- --- - Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-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. -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net
[WiX-users] Adding ticks to immediate custom actions
I have a few custom actions that run just before InstallFinalize and I am trying to tidy up my progress bar because at the moment it runs two or three times and looks empty just before the install completes. They are immediate custom actions and I have used ProgressText to show text explaining what they do for the user but I would like to know how to give them ticks so that they are displayed correctly in the progress bar. Can anyone help me please? Kind Regards, Natalie Carr -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Removing table in the Patch
RemoveFile table entries are always associated with a component http://msdn.microsoft.com/library/aa371201.aspx If you removed the RemoveFile table, you would be changing component contents, which is not allowed. You could possibly add a condition of NOT PATCH on the RemoveFiles action so that it doesn't run during a patch. Be warned that this will affect all removefile elements in the current and future versions until you release a new baseline MSI. -Original Message- From: Fyodor Koryazhkin [mailto:fyodor...@gmail.com] Sent: 16 October 2012 22:25 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Removing table in the Patch Hi, I have an installer that has two entries in RemoveFile table. This is done to update during Major upgrade files that were edited by the customer. During Patch this leads to problem because files are deleted therefore these entries were removed in new package. There is no problem with one patch and files remaining on the disk but when the second patch is created with removed table it cannot be applied. It does not matter in what sequence patches are installed they cannot be applied on each other. The question is whether during patch installation tables or individual entries in tables not related to Components can be removed? Thank you. -- Regards, Fyodor Koryazhkin.. - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding ticks to immediate custom actions
You ultimately have to call MsiProcessMessage. The Wix SDK might have some useful functions to make that easier. Scheduling a deferred CA with WcaDoDeferredAction from the Wix SDK is easy because it allows you to specify the ticks as its 3rd parameter. There might be an equivalent for immediate actions. Have a read of the code for WcaDoDeferredAction in the wix sources in wcawrap.cpp if there isn't. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 17 October 2012 10:42 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Adding ticks to immediate custom actions I have a few custom actions that run just before InstallFinalize and I am trying to tidy up my progress bar because at the moment it runs two or three times and looks empty just before the install completes. They are immediate custom actions and I have used ProgressText to show text explaining what they do for the user but I would like to know how to give them ticks so that they are displayed correctly in the progress bar. Can anyone help me please? Kind Regards, Natalie Carr - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding ticks to immediate custom actions
Thanks Peter, I get 4 properties from my MSI in my custom action so that is why it is immediate. Am I correct in thinking you cannot get properties in deferred custom actions? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 17 October 2012 11:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Adding ticks to immediate custom actions You ultimately have to call MsiProcessMessage. The Wix SDK might have some useful functions to make that easier. Scheduling a deferred CA with WcaDoDeferredAction from the Wix SDK is easy because it allows you to specify the ticks as its 3rd parameter. There might be an equivalent for immediate actions. Have a read of the code for WcaDoDeferredAction in the wix sources in wcawrap.cpp if there isn't. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 17 October 2012 10:42 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Adding ticks to immediate custom actions I have a few custom actions that run just before InstallFinalize and I am trying to tidy up my progress bar because at the moment it runs two or three times and looks empty just before the install completes. They are immediate custom actions and I have used ProgressText to show text explaining what they do for the user but I would like to know how to give them ticks so that they are displayed correctly in the progress bar. Can anyone help me please? Kind Regards, Natalie Carr - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding ticks to immediate custom actions
You have to pass properties to deferred CAs in a particular way. Effectively, you concatenate their string values together, with some unique separator, into a property with the same name as your custom action. In the CA you read that property and parse the values back out. Again there are some wix SDK functions to make this simpler but it's not too tricky to do yourself either. The limitations and process are described here http://msdn.microsoft.com/en-us/library/windows/desktop/aa370543%28v=vs.85%29 .aspx The choice between immediate and deferred should be based on whether the action changes the system. Deferred actions run as the system, not as the installing user. I'd recommend reading this section http://msdn.microsoft.com/en-us/library/windows/desktop/aa368268%28v=vs.85%29 .aspx -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 17 October 2012 11:40 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Adding ticks to immediate custom actions Thanks Peter, I get 4 properties from my MSI in my custom action so that is why it is immediate. Am I correct in thinking you cannot get properties in deferred custom actions? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 17 October 2012 11:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Adding ticks to immediate custom actions You ultimately have to call MsiProcessMessage. The Wix SDK might have some useful functions to make that easier. Scheduling a deferred CA with WcaDoDeferredAction from the Wix SDK is easy because it allows you to specify the ticks as its 3rd parameter. There might be an equivalent for immediate actions. Have a read of the code for WcaDoDeferredAction in the wix sources in wcawrap.cpp if there isn't. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 17 October 2012 10:42 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Adding ticks to immediate custom actions I have a few custom actions that run just before InstallFinalize and I am trying to tidy up my progress bar because at the moment it runs two or three times and looks empty just before the install completes. They are immediate custom actions and I have used ProgressText to show text explaining what they do for the user but I would like to know how to give them ticks so that they are displayed correctly in the progress bar. Can anyone help me please? Kind Regards, Natalie Carr - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding ticks to immediate custom actions
Thanks for all that info Peter, had a quick read and immediate custom actions is fine for what I want to do, now just to get them implemented in the progress bar. Also my progress bar fills completely and then resets for copying the files over, I have looked at my log and I can't seem to find what is causing this as I have no custom actions running in this period. Would you have any idea? Thanks -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 17 October 2012 11:52 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Adding ticks to immediate custom actions You have to pass properties to deferred CAs in a particular way. Effectively, you concatenate their string values together, with some unique separator, into a property with the same name as your custom action. In the CA you read that property and parse the values back out. Again there are some wix SDK functions to make this simpler but it's not too tricky to do yourself either. The limitations and process are described here http://msdn.microsoft.com/en-us/library/windows/desktop/aa370543%28v=vs.85%2 9 .aspx The choice between immediate and deferred should be based on whether the action changes the system. Deferred actions run as the system, not as the installing user. I'd recommend reading this section http://msdn.microsoft.com/en-us/library/windows/desktop/aa368268%28v=vs.85%2 9 .aspx -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 17 October 2012 11:40 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Adding ticks to immediate custom actions Thanks Peter, I get 4 properties from my MSI in my custom action so that is why it is immediate. Am I correct in thinking you cannot get properties in deferred custom actions? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 17 October 2012 11:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Adding ticks to immediate custom actions You ultimately have to call MsiProcessMessage. The Wix SDK might have some useful functions to make that easier. Scheduling a deferred CA with WcaDoDeferredAction from the Wix SDK is easy because it allows you to specify the ticks as its 3rd parameter. There might be an equivalent for immediate actions. Have a read of the code for WcaDoDeferredAction in the wix sources in wcawrap.cpp if there isn't. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 17 October 2012 10:42 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Adding ticks to immediate custom actions I have a few custom actions that run just before InstallFinalize and I am trying to tidy up my progress bar because at the moment it runs two or three times and looks empty just before the install completes. They are immediate custom actions and I have used ProgressText to show text explaining what they do for the user but I would like to know how to give them ticks so that they are displayed correctly in the progress bar. Can anyone help me please? Kind Regards, Natalie Carr - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download
Re: [WiX-users] FW: FW: Patch installation asks for a reboot
I had added a dummy property in the ddp file like *Product ...* *Property Id=DummyProperty Value='1' /* *InstallExecuteSequence* ** ** */InstallExecuteSequence* */Product* and added a PropertyRef for the dummy property in the patch. I saw that the new dummy property got added to the patch and on it showed up in the orca tool too in the Property table. However InstallExecuteSequence was still not updated. Can you please explain what you mean when you say referencing the same fragment as the installexecutesequence? In the above dummy code snippet is there something that I need to change? Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, October 17, 2012 3:01 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] FW: Patch installation asks for a reboot Have you anything referencing the fragment that the installexecutesequence is in ? There is no installexecutesequenceRef element so you'll need some way to tell Wix to include the new sequence in the patch. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 17 October 2012 03:09 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] FW: Patch installation asks for a reboot Hi, There is still one more problem. I thought if I change the install execute sequence in the target msi, that will be picked up by the msp. However when I drop the msp on the base msi in Orca tool I do not see any change in the install sequence. All the new components that I have added, modified seem to be there in the tables - basically I can see all other changes that I have made in the patch except for the install execute sequence change. Can you please provide some idea as to what might be happening here? Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, October 16, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patch installation asks for a reboot A patch works by transforming the installed and cached MSI with the patch and then running a repair on the resulting MSI. That's why you see the MSI apparently installing again. Altering the condition to NOT REMOVE AND NOT PATCH in the patch sounds like a reasonable fix, if you're certain that the condition that required the reboot won't occur again. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 16 October 2012 11:23 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Patch installation asks for a reboot Hi, We are creating a patch on top of already shipped product. In the product msi we schedule a reboot like ScheduleReboot sequence=AfterInstallFinalizeNOT REMOVE/ScheduleReboot It appears while installing the patch which targets the above msi, it reruns the msi and a reboot gets scheduled. Is there any way we can avoid the ScheduleReboot while installing the patch? Will changing the schedule reboot condition in product msi to something like *NOT REMOVE AND NOT PATCH* or, *NOT REMOVE AND NOT OLDERPRODUCTFOUND* help? While re-running the msi installsequence does the patch pick up the actions from already installed msi i.e is it runtime event? Or, the msi installsequence run by the patch is determined at compile time (I.e. if I change the condition for reboot in the product msi will it be honored by the patch)? Regards Abhijit -- --- - Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-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. -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too!
Re: [WiX-users] Adding ticks to immediate custom actions
The standard progress messages sent by windows installer cause this. There is, at minimum, one bar for the preparation of the script and then a reset and then another for the execution of the script. You can also have roll back and possibly some other circumstances in which the bars don't just progress from start to finish. Rob has talked about it on his blog in the past. If you want to manipulate the progress and reset messages, you have to write your own external UI which is a lot of work for something most users won't give a second thought to. Burn's own UI presents progress into a sensible way. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 17 October 2012 12:03 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Adding ticks to immediate custom actions Thanks for all that info Peter, had a quick read and immediate custom actions is fine for what I want to do, now just to get them implemented in the progress bar. Also my progress bar fills completely and then resets for copying the files over, I have looked at my log and I can't seem to find what is causing this as I have no custom actions running in this period. Would you have any idea? Thanks -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 17 October 2012 11:52 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Adding ticks to immediate custom actions You have to pass properties to deferred CAs in a particular way. Effectively, you concatenate their string values together, with some unique separator, into a property with the same name as your custom action. In the CA you read that property and parse the values back out. Again there are some wix SDK functions to make this simpler but it's not too tricky to do yourself either. The limitations and process are described here http://msdn.microsoft.com/en-us/library/windows/desktop/aa370543%28v=vs.85%2 9 .aspx The choice between immediate and deferred should be based on whether the action changes the system. Deferred actions run as the system, not as the installing user. I'd recommend reading this section http://msdn.microsoft.com/en-us/library/windows/desktop/aa368268%28v=vs.85%2 9 .aspx -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 17 October 2012 11:40 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Adding ticks to immediate custom actions Thanks Peter, I get 4 properties from my MSI in my custom action so that is why it is immediate. Am I correct in thinking you cannot get properties in deferred custom actions? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 17 October 2012 11:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Adding ticks to immediate custom actions You ultimately have to call MsiProcessMessage. The Wix SDK might have some useful functions to make that easier. Scheduling a deferred CA with WcaDoDeferredAction from the Wix SDK is easy because it allows you to specify the ticks as its 3rd parameter. There might be an equivalent for immediate actions. Have a read of the code for WcaDoDeferredAction in the wix sources in wcawrap.cpp if there isn't. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 17 October 2012 10:42 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Adding ticks to immediate custom actions I have a few custom actions that run just before InstallFinalize and I am trying to tidy up my progress bar because at the moment it runs two or three times and looks empty just before the install completes. They are immediate custom actions and I have used ProgressText to show text explaining what they do for the user but I would like to know how to give them ticks so that they are displayed correctly in the progress bar. Can anyone help me please? Kind Regards, Natalie Carr - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web
Re: [WiX-users] FW: FW: Patch installation asks for a reboot
Your code snippet shows the right way to proceed. If you can see the property change but not the sequence change, it might be because the property and sequence are in different fragments. Are you using admin installations, rather than wixpdbs, to build your patch ? If so, the MSI is automatically fragmented behind the scenes and the property would effectively be in a fragment on its own. I think to get around that, you would need to add CustomActionRefs for any action whose order (sequence number) has changed. I'll try to explain my earlier comment: When you REFerence an element (as in ComponentRef, CustomActionRef), everything in the same fragment is also pulled into the patch. Therefore, if you want your sequence changes in the patch, you must reference something in the same fragment as the execute sequence - because there is no InstallExecuteSequenceRef element. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 17 October 2012 12:18 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] FW: FW: Patch installation asks for a reboot I had added a dummy property in the ddp file like *Product ...* *Property Id=DummyProperty Value='1' /* *InstallExecuteSequence* ** ** */InstallExecuteSequence* */Product* and added a PropertyRef for the dummy property in the patch. I saw that the new dummy property got added to the patch and on it showed up in the orca tool too in the Property table. However InstallExecuteSequence was still not updated. Can you please explain what you mean when you say referencing the same fragment as the installexecutesequence? In the above dummy code snippet is there something that I need to change? Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, October 17, 2012 3:01 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] FW: Patch installation asks for a reboot Have you anything referencing the fragment that the installexecutesequence is in ? There is no installexecutesequenceRef element so you'll need some way to tell Wix to include the new sequence in the patch. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 17 October 2012 03:09 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] FW: Patch installation asks for a reboot Hi, There is still one more problem. I thought if I change the install execute sequence in the target msi, that will be picked up by the msp. However when I drop the msp on the base msi in Orca tool I do not see any change in the install sequence. All the new components that I have added, modified seem to be there in the tables - basically I can see all other changes that I have made in the patch except for the install execute sequence change. Can you please provide some idea as to what might be happening here? Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, October 16, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patch installation asks for a reboot A patch works by transforming the installed and cached MSI with the patch and then running a repair on the resulting MSI. That's why you see the MSI apparently installing again. Altering the condition to NOT REMOVE AND NOT PATCH in the patch sounds like a reasonable fix, if you're certain that the condition that required the reboot won't occur again. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 16 October 2012 11:23 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Patch installation asks for a reboot Hi, We are creating a patch on top of already shipped product. In the product msi we schedule a reboot like ScheduleReboot sequence=AfterInstallFinalizeNOT REMOVE/ScheduleReboot It appears while installing the patch which targets the above msi, it reruns the msi and a reboot gets scheduled. Is there any way we can avoid the ScheduleReboot while installing the patch? Will changing the schedule reboot condition in product msi to something like *NOT REMOVE AND NOT PATCH* or, *NOT REMOVE AND NOT OLDERPRODUCTFOUND* help? While re-running the msi installsequence does the patch pick up the actions from already installed msi i.e is it runtime event? Or, the msi installsequence run by the patch is determined at compile time (I.e. if I change the condition for reboot in the product msi will it be honored by the patch)? Regards Abhijit --- --- --- - Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening
Re: [WiX-users] FW: FW: FW: Patch installation asks for a reboot
*I think to get around that, you would need to add CustomActionRefs for any action whose order (sequence number) has changed.* ** Can we add custom action refs for predefined actions? In InstallExecuteSequence we are changing the conditon for *ScheduleReboot*action. Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, October 17, 2012 5:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] FW: FW: Patch installation asks for a reboot Your code snippet shows the right way to proceed. If you can see the property change but not the sequence change, it might be because the property and sequence are in different fragments. Are you using admin installations, rather than wixpdbs, to build your patch ? If so, the MSI is automatically fragmented behind the scenes and the property would effectively be in a fragment on its own. I think to get around that, you would need to add CustomActionRefs for any action whose order (sequence number) has changed. I'll try to explain my earlier comment: When you REFerence an element (as in ComponentRef, CustomActionRef), everything in the same fragment is also pulled into the patch. Therefore, if you want your sequence changes in the patch, you must reference something in the same fragment as the execute sequence - because there is no InstallExecuteSequenceRef element. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 17 October 2012 12:18 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] FW: FW: Patch installation asks for a reboot I had added a dummy property in the ddp file like *Product ...* *Property Id=DummyProperty Value='1' /* *InstallExecuteSequence* ** ** */InstallExecuteSequence* */Product* and added a PropertyRef for the dummy property in the patch. I saw that the new dummy property got added to the patch and on it showed up in the orca tool too in the Property table. However InstallExecuteSequence was still not updated. Can you please explain what you mean when you say referencing the same fragment as the installexecutesequence? In the above dummy code snippet is there something that I need to change? Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, October 17, 2012 3:01 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] FW: Patch installation asks for a reboot Have you anything referencing the fragment that the installexecutesequence is in ? There is no installexecutesequenceRef element so you'll need some way to tell Wix to include the new sequence in the patch. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 17 October 2012 03:09 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] FW: Patch installation asks for a reboot Hi, There is still one more problem. I thought if I change the install execute sequence in the target msi, that will be picked up by the msp. However when I drop the msp on the base msi in Orca tool I do not see any change in the install sequence. All the new components that I have added, modified seem to be there in the tables - basically I can see all other changes that I have made in the patch except for the install execute sequence change. Can you please provide some idea as to what might be happening here? Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, October 16, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patch installation asks for a reboot A patch works by transforming the installed and cached MSI with the patch and then running a repair on the resulting MSI. That's why you see the MSI apparently installing again. Altering the condition to NOT REMOVE AND NOT PATCH in the patch sounds like a reasonable fix, if you're certain that the condition that required the reboot won't occur again. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 16 October 2012 11:23 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Patch installation asks for a reboot Hi, We are creating a patch on top of already shipped product. In the product msi we schedule a reboot like ScheduleReboot sequence=AfterInstallFinalizeNOT REMOVE/ScheduleReboot It appears while installing the patch which targets the above msi, it reruns the msi and a reboot gets scheduled. Is there any way we can avoid the ScheduleReboot while installing the patch? Will changing the schedule reboot condition in product msi to something like *NOT REMOVE AND NOT PATCH* or,
Re: [WiX-users] FW: FW: FW: Patch installation asks for a reboot
I've never tried it, but I'd expect so. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 17 October 2012 14:27 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] FW: FW: FW: Patch installation asks for a reboot *I think to get around that, you would need to add CustomActionRefs for any action whose order (sequence number) has changed.* ** Can we add custom action refs for predefined actions? In InstallExecuteSequence we are changing the conditon for *ScheduleReboot*action. Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, October 17, 2012 5:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] FW: FW: Patch installation asks for a reboot Your code snippet shows the right way to proceed. If you can see the property change but not the sequence change, it might be because the property and sequence are in different fragments. Are you using admin installations, rather than wixpdbs, to build your patch ? If so, the MSI is automatically fragmented behind the scenes and the property would effectively be in a fragment on its own. I think to get around that, you would need to add CustomActionRefs for any action whose order (sequence number) has changed. I'll try to explain my earlier comment: When you REFerence an element (as in ComponentRef, CustomActionRef), everything in the same fragment is also pulled into the patch. Therefore, if you want your sequence changes in the patch, you must reference something in the same fragment as the execute sequence - because there is no InstallExecuteSequenceRef element. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 17 October 2012 12:18 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] FW: FW: Patch installation asks for a reboot I had added a dummy property in the ddp file like *Product ...* *Property Id=DummyProperty Value='1' /* *InstallExecuteSequence* ** ** */InstallExecuteSequence* */Product* and added a PropertyRef for the dummy property in the patch. I saw that the new dummy property got added to the patch and on it showed up in the orca tool too in the Property table. However InstallExecuteSequence was still not updated. Can you please explain what you mean when you say referencing the same fragment as the installexecutesequence? In the above dummy code snippet is there something that I need to change? Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, October 17, 2012 3:01 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] FW: Patch installation asks for a reboot Have you anything referencing the fragment that the installexecutesequence is in ? There is no installexecutesequenceRef element so you'll need some way to tell Wix to include the new sequence in the patch. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 17 October 2012 03:09 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] FW: Patch installation asks for a reboot Hi, There is still one more problem. I thought if I change the install execute sequence in the target msi, that will be picked up by the msp. However when I drop the msp on the base msi in Orca tool I do not see any change in the install sequence. All the new components that I have added, modified seem to be there in the tables - basically I can see all other changes that I have made in the patch except for the install execute sequence change. Can you please provide some idea as to what might be happening here? Regards Abhijit -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, October 16, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patch installation asks for a reboot A patch works by transforming the installed and cached MSI with the patch and then running a repair on the resulting MSI. That's why you see the MSI apparently installing again. Altering the condition to NOT REMOVE AND NOT PATCH in the patch sounds like a reasonable fix, if you're certain that the condition that required the reboot won't occur again. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 16 October 2012 11:23 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Patch installation asks for a reboot Hi, We are creating a patch on top of already shipped product. In the product msi we schedule a reboot like ScheduleReboot sequence=AfterInstallFinalizeNOT REMOVE/ScheduleReboot It appears while installing the
[WiX-users] Remove table in Patch installation
Hi, I have Patch installation that removes RemoveFile table. The patch can be installed without any problem. Problem begins with the second patch that also missing RemoveFile table: it can be installed alone but both patches cannot be installed on target product in any sequence. The question is: Is it legal to remove table in Patch? I use MSI Schema 200 and installation run on Sever 2008 R2 with MSI 5.0. Thank you. -- Regards, Fyodor Koryazhkin.. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] terminate/stop/close Application when installing
Util:CloseApplication is the Wix way to do it. I've provided an example on this thread http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CloseApplicatio n-td6885610.html#none Also, you can document the requirement or put it in a bootstrapper/chainer. -Original Message- From: Muzikayise Flynn Buthelezi [mailto:muzkay...@gmail.com] Sent: 17 October 2012 15:54 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] terminate/stop/close Application when installing Good afternoon Team, trust everyone is well. whats the best way to terminate an application before installing it? We have an application which we rollout to thousands of machines, sometimes the application is still open on the machine while we do this rollout therefore the rollout does not occur on that machine. So what we want to do is terminate/stop/close current application so that we may carry on installing it. the ideal solution would be to pop up an alert box advising the user that the application will be closed in 10 seconds, after 10 seconds then we terminate/stop/close the application and carry on with install (This would be nice, but first priority is just to terminate/stop/close) thanks in advance for your kind assistance, -- Best always, Muzi 082 594 4807 Light, Love Prosperity in Abundance!!! - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] terminate/stop/close Application when installing
Hi Peter, thanks for kindly getting back to will checkout the thread. Ta. On Wed, Oct 17, 2012 at 5:01 PM, Peter Shirtcliffe pshirtcli...@sdl.com wrote: Util:CloseApplication is the Wix way to do it. I've provided an example on this thread http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CloseApplicatio n-td6885610.html#none Also, you can document the requirement or put it in a bootstrapper/chainer. -Original Message- From: Muzikayise Flynn Buthelezi [mailto:muzkay...@gmail.com] Sent: 17 October 2012 15:54 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] terminate/stop/close Application when installing Good afternoon Team, trust everyone is well. whats the best way to terminate an application before installing it? We have an application which we rollout to thousands of machines, sometimes the application is still open on the machine while we do this rollout therefore the rollout does not occur on that machine. So what we want to do is terminate/stop/close current application so that we may carry on installing it. the ideal solution would be to pop up an alert box advising the user that the application will be closed in 10 seconds, after 10 seconds then we terminate/stop/close the application and carry on with install (This would be nice, but first priority is just to terminate/stop/close) thanks in advance for your kind assistance, -- Best always, Muzi 082 594 4807 Light, Love Prosperity in Abundance!!! - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Best always, Muzi 082 594 4807 Light, Love Prosperity in Abundance!!! -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CloseApplication
I am trying to close Outlook since our product is a add-in for outlook, the uninstall brings the FileInUseProcess which is great, but I also want this for the INSTALL I am doing this but it is not working: util:CloseApplication Id=CloseMicrosoftOutlook Property=FileInUseProcess CloseMessage=no ElevatedCloseMessage=no Description=Microsoft Outlook is open and needs to be closed before this installation continues RebootPrompt=no Target=OUTLOOK.EXE / CustomAction Id=CA_SetProperty_FileInUseProcess Execute=immediate Impersonate=yes Property=[FileInUseProcess] Value=OUTLOOK.EXE/ UI ProgressText Action=CA_SetProperty_FileInUseProcessCA: Setting file in use process.../ProgressText /UI InstallExecuteSequence Custom Action=CA_SetProperty_FileInUseProcess Before=InstallValidate/Custom InstallUISequence Custom Action=CA_SetProperty_FileInUseProcess After=AppSearch/Custom Any suggestions? Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CloseApplication-tp6885610p7581420.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CloseApplication
I am trying to close Outlook since our product is a add-in for outlook, the uninstall brings the FileInUseProcess which is great, but I also want this for the INSTALLI am doing this but it is not working: CA: Setting file in use process...Any suggestions?Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CloseApplication-tp6885610p7581419.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] terminate/stop/close Application when installing
In Vista and above the restart manager closes the app: http://msdn.microsoft.com/en-us/library/windows/desktop/aa373651%28v=vs.85%29.aspx. That is what I use. For Windows XP I have a custom action that closes my app although it looks like I should use Util:CloseApplication. There was a period of time when I didn't have the above implemented and funny thing is that I never had an install stop when the old version of the app I was installing was open. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: October-17-12 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] terminate/stop/close Application when installing Util:CloseApplication is the Wix way to do it. I've provided an example on this thread http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CloseApplicatio n-td6885610.html#none Also, you can document the requirement or put it in a bootstrapper/chainer. -Original Message- From: Muzikayise Flynn Buthelezi [mailto:muzkay...@gmail.com] Sent: 17 October 2012 15:54 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] terminate/stop/close Application when installing Good afternoon Team, trust everyone is well. whats the best way to terminate an application before installing it? We have an application which we rollout to thousands of machines, sometimes the application is still open on the machine while we do this rollout therefore the rollout does not occur on that machine. So what we want to do is terminate/stop/close current application so that we may carry on installing it. the ideal solution would be to pop up an alert box advising the user that the application will be closed in 10 seconds, after 10 seconds then we terminate/stop/close the application and carry on with install (This would be nice, but first priority is just to terminate/stop/close) thanks in advance for your kind assistance, -- Best always, Muzi 082 594 4807 Light, Love Prosperity in Abundance!!! - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CloseApplication
I don't think you can make the filesinuse dialog appear without trying to replace a file in use. Why not close Outlook for the user with CloseMessage=yes ? -Original Message- From: StevenOgilvie [mailto:sogil...@msn.com] Sent: 17 October 2012 16:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] CloseApplication I am trying to close Outlook since our product is a add-in for outlook, the uninstall brings the FileInUseProcess which is great, but I also want this for the INSTALL I am doing this but it is not working: util:CloseApplication Id=CloseMicrosoftOutlook Property=FileInUseProcess CloseMessage=no ElevatedCloseMessage=no Description=Microsoft Outlook is open and needs to be closed before this installation continues RebootPrompt=no Target=OUTLOOK.EXE / CustomAction Id=CA_SetProperty_FileInUseProcess Execute=immediate Impersonate=yes Property=[FileInUseProcess] Value=OUTLOOK.EXE/ UI ProgressText Action=CA_SetProperty_FileInUseProcessCA: Setting file in use process.../ProgressText /UI InstallExecuteSequence Custom Action=CA_SetProperty_FileInUseProcess Before=InstallValidate/Custom InstallUISequence Custom Action=CA_SetProperty_FileInUseProcess After=AppSearch/Custom Any suggestions? Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CloseApplicatio n-tp6885610p7581420.html Sent from the wix-users mailing list archive at Nabble.com. - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] MSI install returning error 1603 when it should return 1638
Hi All,
I have setup my MSI so that it detects when a newer (higher version) is
installed. This works fine from a human interface point of view (i.e. I get a
message saying that a later version is already installed). However when
another product tries to install my MSI they are expecting to get the 1638 MSI
error (ERROR_PRODUCT_VERSION), but instead we are seeing the 1603 MSI error
(ERROR_INSTALL_FAILURE).
Can anyone help?
FYI -- Here are snippets of my wxs file with the relevant info:
Upgrade
Id={2DE4B44F-6886-4b1e-BF91-BD0236D428D9}
UpgradeVersion
Property=OLDERVERSIONBEINGUPGRADED
Minimum=2.7.0.0 Maximum=!(bind.FileVersion.ccsw32.dll)
IncludeMinimum=yes
IncludeMaximum=yes
OnlyDetect=no/
UpgradeVersion Property=NEWERVERSIONDETECTED
Minimum=!(bind.FileVersion.ccsw32.dll)
IncludeMinimum=no
OnlyDetect=yes/
/Upgrade
Condition Message=A later version of [ProductName] is already installed.
Setup will now exit.
NOT NEWERVERSIONDETECTED OR Installed
/Condition
___
I am seeing in the log file that NEWERVERSIONDETECTED property is added.
Thanks in advance for any help.
Carl
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI install returning error 1603 when it should return 1638
Error 1638 isn't related to anything you do internally by denying certain
installs for your own internal reasons. It's returned when the install
cannot even proceed because you're trying to install a package with the same
ProductCode (or PackageCode) as one that's already installed, but with a
different version (and in non maintenance mode).
Phil
-Original Message-
From: Carl Tietjen [mailto:ctiet...@netiq.com]
Sent: Wednesday, October 17, 2012 10:27 AM
To: WiX Users
Subject: [WiX-users] MSI install returning error 1603 when it should return
1638
Hi All,
I have setup my MSI so that it detects when a newer (higher version) is
installed. This works fine from a human interface point of view (i.e. I get
a message saying that a later version is already installed). However when
another product tries to install my MSI they are expecting to get the 1638
MSI error (ERROR_PRODUCT_VERSION), but instead we are seeing the 1603 MSI
error (ERROR_INSTALL_FAILURE).
Can anyone help?
FYI -- Here are snippets of my wxs file with the relevant info:
Upgrade
Id={2DE4B44F-6886-4b1e-BF91-BD0236D428D9}
UpgradeVersion
Property=OLDERVERSIONBEINGUPGRADED
Minimum=2.7.0.0 Maximum=!(bind.FileVersion.ccsw32.dll)
IncludeMinimum=yes
IncludeMaximum=yes
OnlyDetect=no/
UpgradeVersion Property=NEWERVERSIONDETECTED
Minimum=!(bind.FileVersion.ccsw32.dll)
IncludeMinimum=no
OnlyDetect=yes/
/Upgrade
Condition Message=A later version of [ProductName] is already installed.
Setup will now exit.
NOT NEWERVERSIONDETECTED OR Installed /Condition
___
I am seeing in the log file that NEWERVERSIONDETECTED property is added.
Thanks in advance for any help.
Carl
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] terminate/stop/close Application when installing
The devil is in the details. A verbose log is the best way to see exactly what's going on. For example, if Windows already knows that it will need to reboot at the end of the install then it won't bother prompting to close down any apps. What's the point? Phil -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Wednesday, October 17, 2012 9:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] terminate/stop/close Application when installing In Vista and above the restart manager closes the app: http://msdn.microsoft.com/en-us/library/windows/desktop/aa373651%28v=vs.85%2 9.aspx. That is what I use. For Windows XP I have a custom action that closes my app although it looks like I should use Util:CloseApplication. There was a period of time when I didn't have the above implemented and funny thing is that I never had an install stop when the old version of the app I was installing was open. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: October-17-12 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] terminate/stop/close Application when installing Util:CloseApplication is the Wix way to do it. I've provided an example on this thread http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CloseApplicati o n-td6885610.html#none Also, you can document the requirement or put it in a bootstrapper/chainer. -Original Message- From: Muzikayise Flynn Buthelezi [mailto:muzkay...@gmail.com] Sent: 17 October 2012 15:54 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] terminate/stop/close Application when installing Good afternoon Team, trust everyone is well. whats the best way to terminate an application before installing it? We have an application which we rollout to thousands of machines, sometimes the application is still open on the machine while we do this rollout therefore the rollout does not occur on that machine. So what we want to do is terminate/stop/close current application so that we may carry on installing it. the ideal solution would be to pop up an alert box advising the user that the application will be closed in 10 seconds, after 10 seconds then we terminate/stop/close the application and carry on with install (This would be nice, but first priority is just to terminate/stop/close) thanks in advance for your kind assistance, -- Best always, Muzi 082 594 4807 Light, Love Prosperity in Abundance!!! - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CloseApplication
You can write a custom action that uses the MsiProcessMessage (or equivalent) call with INSTALLMESSAGE_FILESINUSE to cause a FilesInUse dialog to display, as long as you populate the required record in the right way. http://msdn.microsoft.com/en-us/library/windows/desktop/aa371614(v=vs.85).as px Phil -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, October 17, 2012 9:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] CloseApplication I don't think you can make the filesinuse dialog appear without trying to replace a file in use. Why not close Outlook for the user with CloseMessage=yes ? -Original Message- From: StevenOgilvie [mailto:sogil...@msn.com] Sent: 17 October 2012 16:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] CloseApplication I am trying to close Outlook since our product is a add-in for outlook, the uninstall brings the FileInUseProcess which is great, but I also want this for the INSTALL I am doing this but it is not working: util:CloseApplication Id=CloseMicrosoftOutlook Property=FileInUseProcess CloseMessage=no ElevatedCloseMessage=no Description=Microsoft Outlook is open and needs to be closed before this installation continues RebootPrompt=no Target=OUTLOOK.EXE / CustomAction Id=CA_SetProperty_FileInUseProcess Execute=immediate Impersonate=yes Property=[FileInUseProcess] Value=OUTLOOK.EXE/ UI ProgressText Action=CA_SetProperty_FileInUseProcessCA: Setting file in use process.../ProgressText /UI InstallExecuteSequence Custom Action=CA_SetProperty_FileInUseProcess Before=InstallValidate/Custom InstallUISequence Custom Action=CA_SetProperty_FileInUseProcess After=AppSearch/Custom Any suggestions? Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CloseApplicati o n-tp6885610p7581420.html Sent from the wix-users mailing list archive at Nabble.com. - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ 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. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] light.exe : error LGHT0001: Illegal characters in path.
Hey all, I'm struggle a bit with 3.6. In my build process via MSBuild (vs2010) I'm now getting the following error: light.exe : error LGHT0001: Illegal characters in path. Exception Type: System.ArgumentException Stack Trace: at System.IO.Path.CheckInvalidPathChars(String path) at System.IO.Path.IsPathRooted(String path) at Microsoft.Tools.WindowsInstallerXml.BinderFileManager.ResolveFile(String source, String type, SourceLineNumberCollection sourceLineNumbers, BindStage bindStage) at Microsoft.Tools.WindowsInstallerXml.Binder.ResolveFields(TableCollection tables, Hashtable cabinets, ArrayList delayedFields) at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String databaseFile) at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String file) at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) Binder temporary directory located at 'C:\Users\Robert\AppData\Local\Temp\lxjy9l92'. Any clues on how I can go about figuring out which .wxs source file causes the problem (or better yet a specific error location)? Any idea why Microsoft.Tools.WindowsInstallerXml.BinderFileManager.ResolveFile() might be getting called with an invalid file name... but one that passes Candle's validation? Is there anything I could run against the .wixobj files that might extract/test the names of files? Thanks, Rob -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bundle self-update feature
Hello, I would like to start using the bundle self-update feature introduced in WiX 3.7 in our installer. Since this is work in progress and the feature is not much documented yet (or am I wrong?) I have several questions. So far I found that the bundle wxs should contain the Update element referencing an update feed. The BA then detects whether a newer version is available and uses the SetUpdate API to set the location of the updated bundle. Burn then during Apply downloads the bundle, starts the new bundle and exits. The update feed uses the http://appsyndication.org/2006/appsyn schema. Is the schema available or documented somewhere? Although it seems that the BA can use any method to detect update and then use SetUpdate, the documentation for the Update element suggests that in the future Burn will be able to detect newer version without BA's intervention, so I should stick to this format, right? What are the OnDetectUpdateBegin/End events good for and when they are invoked? When the SetUpdate has to be called? Should it be after Detect, but before Plan? How is the self-update feature supposed to be integrated into BA? In our installer we have the license agreement on the first page and then an user have to enter some information (e.g. license key, server connection parameters etc.) before he can actually start the installation. If an update is downloaded I don't want the user to enter the information again. Is there a way the old bundle can pass the information to the new one? Thanks, Milan -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] unsubscribe
Email Disclaimerhttp://www.redprairie.com/Content.aspx?id=2471 -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI install returning error 1603 when it should return 1638
Hi Phil,
I am not sure that I understand.
The scenario is that I am trying to install the same product as one that is
already installed but with a different version (i.e. I am trying to install an
older version of the same product, and I am looking to provide a way to fail
gracefully).
FYI -- I have tried a different approach which was to add the
WixExitEarlyWithSuccess, but I cannot seem to get that to work either. I have
followed all of the steps outlined in:
http://wix.sourceforge.net/manual-wix3/wixexitearlywithsuccess.htm but I see
the same results.
Thanks,
Carl
Phil Wilson phil.wil...@mvps.org 10/17/2012 11:31 AM
Error 1638 isn't related to anything you do internally by denying certain
installs for your own internal reasons. It's returned when the install
cannot even proceed because you're trying to install a package with the same
ProductCode (or PackageCode) as one that's already installed, but with a
different version (and in non maintenance mode).
Phil
-Original Message-
From: Carl Tietjen [mailto:ctiet...@netiq.com]
Sent: Wednesday, October 17, 2012 10:27 AM
To: WiX Users
Subject: [WiX-users] MSI install returning error 1603 when it should return
1638
Hi All,
I have setup my MSI so that it detects when a newer (higher version) is
installed. This works fine from a human interface point of view (i.e. I get
a message saying that a later version is already installed). However when
another product tries to install my MSI they are expecting to get the 1638
MSI error (ERROR_PRODUCT_VERSION), but instead we are seeing the 1603 MSI
error (ERROR_INSTALL_FAILURE).
Can anyone help?
FYI -- Here are snippets of my wxs file with the relevant info:
Upgrade
Id={2DE4B44F-6886-4b1e-BF91-BD0236D428D9}
UpgradeVersion
Property=OLDERVERSIONBEINGUPGRADED
Minimum=2.7.0.0 Maximum=!(bind.FileVersion.ccsw32.dll)
IncludeMinimum=yes
IncludeMaximum=yes
OnlyDetect=no/
UpgradeVersion Property=NEWERVERSIONDETECTED
Minimum=!(bind.FileVersion.ccsw32.dll)
IncludeMinimum=no
OnlyDetect=yes/
/Upgrade
Condition Message=A later version of [ProductName] is already installed.
Setup will now exit.
NOT NEWERVERSIONDETECTED OR Installed /Condition
___
I am seeing in the log file that NEWERVERSIONDETECTED property is added.
Thanks in advance for any help.
Carl
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI install returning error 1603 when it should return 1638
The general behavior is that Windows will return the error result
appropriate for the situation, and it decides internally, and it's nothing
to do with any of the ways you might use inside the MSI to say that you
don't want the install to proceed, once it has got through the Windows
checks and actually starts processing.
The term same product isn't very precise! What you're doing is an upgrade,
therefore you most likely have a different ProductCode compared to the
installed product. If it was the same ProductCode, that's when Windows tells
you you're trying to install the exact same product again (as defined by the
ProductCode) and that's when it will tell you error 1638, because a
different version of the same ProductCode is installed. Error 1638 is
nothing to do with an internal decision made by your logic that you want to
stop the install.
Phil
-Original Message-
From: Carl Tietjen [mailto:ctiet...@netiq.com]
Sent: Wednesday, October 17, 2012 3:25 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] MSI install returning error 1603 when it should
return 1638
Hi Phil,
I am not sure that I understand.
The scenario is that I am trying to install the same product as one that is
already installed but with a different version (i.e. I am trying to install
an older version of the same product, and I am looking to provide a way to
fail gracefully).
FYI -- I have tried a different approach which was to add the
WixExitEarlyWithSuccess, but I cannot seem to get that to work either. I
have followed all of the steps outlined in:
http://wix.sourceforge.net/manual-wix3/wixexitearlywithsuccess.htm but I see
the same results.
Thanks,
Carl
Phil Wilson phil.wil...@mvps.org 10/17/2012 11:31 AM
Error 1638 isn't related to anything you do internally by denying certain
installs for your own internal reasons. It's returned when the install
cannot even proceed because you're trying to install a package with the same
ProductCode (or PackageCode) as one that's already installed, but with a
different version (and in non maintenance mode).
Phil
-Original Message-
From: Carl Tietjen [mailto:ctiet...@netiq.com]
Sent: Wednesday, October 17, 2012 10:27 AM
To: WiX Users
Subject: [WiX-users] MSI install returning error 1603 when it should return
1638
Hi All,
I have setup my MSI so that it detects when a newer (higher version) is
installed. This works fine from a human interface point of view (i.e. I get
a message saying that a later version is already installed). However when
another product tries to install my MSI they are expecting to get the 1638
MSI error (ERROR_PRODUCT_VERSION), but instead we are seeing the 1603 MSI
error (ERROR_INSTALL_FAILURE).
Can anyone help?
FYI -- Here are snippets of my wxs file with the relevant info:
Upgrade
Id={2DE4B44F-6886-4b1e-BF91-BD0236D428D9}
UpgradeVersion
Property=OLDERVERSIONBEINGUPGRADED
Minimum=2.7.0.0 Maximum=!(bind.FileVersion.ccsw32.dll)
IncludeMinimum=yes
IncludeMaximum=yes
OnlyDetect=no/
UpgradeVersion Property=NEWERVERSIONDETECTED
Minimum=!(bind.FileVersion.ccsw32.dll)
IncludeMinimum=no
OnlyDetect=yes/
/Upgrade
Condition Message=A later version of [ProductName] is already installed.
Setup will now exit.
NOT NEWERVERSIONDETECTED OR Installed /Condition
___
I am seeing in the log file that NEWERVERSIONDETECTED property is added.
Thanks in advance for any help.
Carl
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for
free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
