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] 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 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
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
[WiX-users] Creating localizable setups
I was trying to create a localized setup in Wix. Lets say I support 20 languages. So, objective is to produce all the 20 mst's. Using InstallShield in one build I can create the msi and the and all the 20 transform files. Now I want to achieve this process using WIX. What I have figured out so far reading the documentation is 1. I would create the wixobj file using candle. 2. and then I could use light.exe to link with the wixobj(from step 1) with .wxl to create the language specific msi files. So, this way I need to create all the 20 msi files, for the 20 languages. 3. Now using torch.exe , I'm planning to take the diff. and create the .mst files 20 times for 20 languages. My concern is this above process is getting a bit complex. Is there a way I can do something to minimize the steps and make it little simple. Any help is greatly appreciated. Thanks, Kajal -- 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
Re: [WiX-users] Creating patch for minor upgrade
Thanks Peter. It works. But one more question, in the patch I've added a new feature and a component under it. In the patch metadata I'm not referencing this new component and then also the component is shown in the diff. Any clue? Thanks once again, Kajal -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, October 03, 2012 8:13 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Creating patch for minor upgrade Only the changes you reference will be included in the patch, so componentrefs for components and propertyrefs for properties. Just add PropertyRef Id=ProductVersion / into your family. -Original Message- From: Kajal Kumar Biswas [mailto:kbis...@adobe.com] Sent: 03 October 2012 14:32 To: wix-users@lists.sourceforge.net Cc: Akshat Kumar Jain Subject: [WiX-users] Creating patch for minor upgrade Hi, I'm creating a patch using the wix toolset (not using the pcp technique). I can create the patch successfully and can orca the msi and view the contents of the patch. But the problem is the ProductVersion does not get bumpted up while I open the patch over the target msi in orca. Steps followed are referred from http://wix.sourceforge.net/manual-wix3/wix_patching.htm Again when I create mst file by diffing the two msi's, and then view the target msi + the mst in orca, then I can see the version number has got bumped. Can somebody please throw some light on it? Thanks, Kajal - - 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 -- 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
[WiX-users] Creating patch for minor upgrade
Hi, I'm creating a patch using the wix toolset (not using the pcp technique). I can create the patch successfully and can orca the msi and view the contents of the patch. But the problem is the ProductVersion does not get bumpted up while I open the patch over the target msi in orca. Steps followed are referred from http://wix.sourceforge.net/manual-wix3/wix_patching.htm Again when I create mst file by diffing the two msi's, and then view the target msi + the mst in orca, then I can see the version number has got bumped. Can somebody please throw some light on it? Thanks, Kajal -- 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
