[WiX-users] Component Guids - Version Changes
Hey WIX Users, I am using WIXv3 3.0.2921 build. And I am able to use automatic component guid generation as stated by Derek in: http://installing.blogspot.com/2006/09/automatically-generating-component.html I also understand that this is a new feature in WIXv3 and may not be stable enough to use. I have the following questions regarding this: 1)As component guids are generated for every build, if I just do a candle+light twice on my WIX code with just same binaries I get two different guids. Am I right? 2)When are these guids generated? At compile time OR link time? Candle time or light time? Because, we have a fragment which is locale independent one and needs to carry the same GUID across all locale specific MSIs where this fragment is absorbed. Hence, I am ok if it generates at compile/candle time. Can someone confirm? 3)Can component guids change across service packs for the same binary? That is, to generate a patch I will have a RTM MSI and then SP1 MSI which I diff using MSP related tools to get a msp. Since, RTM MSI and SP1 MSI have different GUIDs for same component (but same component id) how the MSP gets effected? Thanks a lot. Thanks, Laxmi - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Default regsearch values and upgrading
Hi, I'm new to WiX and have been trying the WiXEdit tool to build an installer. I have been working through a turorial and successfully built the initial MSI file with a custome dialog to collect user information that will be written to the registry but now I have come up against a few issues I can't get around: 1 - Default value of a propoerty I have 2 properties that are populated by a regirstry search. These property values then form the default values in textboxes on my custom form. This works OK. When the registry key is not there or empty how can I give the property a default value? Property Id=MDBFULLPATH RegistrySearch Id=MDBPathRegistry Type=raw Root=HKLM Key=Software\eProject Name=DataSource / /Property 2 - Upgrade / overwright existing installation I'm getting a bit confused about this. I was previously using the freeware AdvancedInstaller to build by MSI http://www.advancedinstaller.com/ . There was a simple tick box in the editor that meant the MSI file created would automatically upgrade older versions of the product already installed. How can I achieve this in WiX? I am happy for every minor upgrade to be treated as a major upgrade but I can't get past the MSI detecting that another version of the product is already installed. This is as far as I have managed to get http://www.nabble.com/file/p13170370/eProject.wxs eProject.wxs http://www.nabble.com/file/p13170370/eprojectwixui.wixlib eprojectwixui.wixlib TIA Russ Green -- View this message in context: http://www.nabble.com/Default-regsearch-values-and-upgrading-tf4611878.html#a13170370 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FileSearch doesn't work (Wix 2.0)
Have you checked out https://sourceforge.net/tracker/? func=detailatid=642714aid=1656236group_id=105970 yet? One trick is to set a property with the folder first and than add a filesearch using that property. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 11, 2007, at 2:59 PM, fiordean dacian wrote: Hi, I'm trying to unsinstall an app other then the one I install (by calling its uninstall.exe). Here is how I do this: Property Id=APPUNINSTALL DirectorySearch Id=SearchAppDir Path=[INSTALLDIR] Depth=3 FileSearch Id=SearchAppFile LongName=uninstall.exe/ /DirectorySearch /Property ... CustomAction Id=UninstallApp Property=APPUNINSTALL ExeCommand='/S' Return=check Execute=deferred/ ... InstallExecuteSequence ... Custom Action=UninstallApp After=RemoveFiles ![CDATA[(FullInstallation = 2)]] AND (! FullInstallation = 3) AND APPUNINSTALL /Custom ... /InstallExecuteSequence Well, I want the custom action executed only on desinstallation of the 'FullInstallation' feature. The directory stucture is like below: C:\Program Files\Company\ProductName file1 file2 ... AppFolderContainingUninstallExe file1 file2 ... uninstall.exe The problem is my APPUNINSTALL isn't set at all (I'm pretty sure the uninstall.exe is in there, the Depth attribute equals 3 is arbitrary). I also tries something like: Property Id=APPUNINSTALL DirectorySearch Id=SearchAppDir Path=[INSTALLDIR] AppFolderContainingUninstallExe Depth=0 FileSearch Id=SearchAppFile LongName=uninstall.exe/ /DirectorySearch /Property which doesn't work either I'm using Wix 2.0 Any suggestions? Thanks, Dacian Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. -- --- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Default regsearch values and upgrading
To set a default property value use the Value attribute in the Property tag. If the search does not find a value that value should be used. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 12, 2007, at 9:18 AM, RussGreen wrote: Hi, I'm new to WiX and have been trying the WiXEdit tool to build an installer. I have been working through a turorial and successfully built the initial MSI file with a custome dialog to collect user information that will be written to the registry but now I have come up against a few issues I can't get around: 1 - Default value of a propoerty I have 2 properties that are populated by a regirstry search. These property values then form the default values in textboxes on my custom form. This works OK. When the registry key is not there or empty how can I give the property a default value? Property Id=MDBFULLPATH RegistrySearch Id=MDBPathRegistry Type=raw Root=HKLM Key=Software\eProject Name=DataSource / /Property 2 - Upgrade / overwright existing installation I'm getting a bit confused about this. I was previously using the freeware AdvancedInstaller to build by MSI http:// www.advancedinstaller.com/ . There was a simple tick box in the editor that meant the MSI file created would automatically upgrade older versions of the product already installed. How can I achieve this in WiX? I am happy for every minor upgrade to be treated as a major upgrade but I can't get past the MSI detecting that another version of the product is already installed. This is as far as I have managed to get http://www.nabble.com/file/p13170370/eProject.wxs eProject.wxs http://www.nabble.com/file/p13170370/eprojectwixui.wixlib eprojectwixui.wixlib TIA Russ Green -- View this message in context: http://www.nabble.com/Default- regsearch-values-and-upgrading-tf4611878.html#a13170370 Sent from the wix-users mailing list archive at Nabble.com. -- --- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] IniFile - Getting user input
The value from the UI is stored in a Property which you can then use in the IniFile under a Component. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 11, 2007, at 6:09 PM, 0x001A4 wrote: I have a dialog in which users are going to be entering information. I know I can use IniFile to write to a file. But I cant use IniFile in a Dialog or UI so what would be the best way to write this information to a file after the user enters it? -- View this message in context: http://www.nabble.com/IniFile--- Getting-user-input-tf4608297.html#a13159174 Sent from the wix-users mailing list archive at Nabble.com. -- --- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Default regsearch values and upgrading
Here is what you need to do to make your install package smart to recognize removing itself if it is already installed. 1. Product tag line, the Id= GUID needs to be Unique each time you build the package (and the version number needs to be incremented each time as well) 2. In the InstallExecuteSequene section, add the following: RemoveExistingProducts After=InstallInitialize / 3. For an Upgrade detection of the product, do something similar to the following where the GUID is the UpgradeCode of your installation Upgrade Id=226F3469-D558-498a-AA7A-AD9072549EF4 UpgradeVersion OnlyDetect=no Property=DETECTED IncludeMaximum=yes IncludeMinimum=yes Maximum=1.5.1.2 Minimum=1.5.1.2/ /Upgrade -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RussGreen Sent: Friday, October 12, 2007 12:18 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Default regsearch values and upgrading Hi, I'm new to WiX and have been trying the WiXEdit tool to build an installer. I have been working through a turorial and successfully built the initial MSI file with a custome dialog to collect user information that will be written to the registry but now I have come up against a few issues I can't get around: 1 - Default value of a propoerty I have 2 properties that are populated by a regirstry search. These property values then form the default values in textboxes on my custom form. This works OK. When the registry key is not there or empty how can I give the property a default value? Property Id=MDBFULLPATH RegistrySearch Id=MDBPathRegistry Type=raw Root=HKLM Key=Software\eProject Name=DataSource / /Property 2 - Upgrade / overwright existing installation I'm getting a bit confused about this. I was previously using the freeware AdvancedInstaller to build by MSI http://www.advancedinstaller.com/ . There was a simple tick box in the editor that meant the MSI file created would automatically upgrade older versions of the product already installed. How can I achieve this in WiX? I am happy for every minor upgrade to be treated as a major upgrade but I can't get past the MSI detecting that another version of the product is already installed. This is as far as I have managed to get http://www.nabble.com/file/p13170370/eProject.wxs eProject.wxs http://www.nabble.com/file/p13170370/eprojectwixui.wixlib eprojectwixui.wixlib TIA Russ Green -- View this message in context: http://www.nabble.com/Default-regsearch-values-and-upgrading-tf4611878.h tml#a13170370 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Silent Installation
My name is Guna S. Am very new to Wix Installer This is regariding to Silent Installation My questions are 1. How to create and add DLL file 2. For silet instllation if user gives command(for ex xxx.msi/quite), so for this how the confiuration file should be 3. How/where to put condition for silent installation and normal installation 4. Is there any good tool/tutorial for silent installation Thanks in advance Thanks, Guna S - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] IniFile - Getting user input
At which point in the install should I add this though? Should I add this somewhere in my main wxs file with all of my other components? If I were to go about it that way, would I then be able to put the info in an ini file after all of my installation files are copied over? Sorry for the newbie questions, but I'm very new to WiX and I'm still trying to grasp some of the concepts. Thanks for the help. Sebastian Brand-2 wrote: The value from the UI is stored in a Property which you can then use in the IniFile under a Component. -- View this message in context: http://www.nabble.com/IniFile---Getting-user-input-tf4608297.html#a13174211 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Share a directory using WIx on install
The FileShare element should do that. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 11, 2007, at 11:58 AM, Craig0ss wrote: Hi I need to know if its possible to share a directory as part of the install?? If this is possible any ideas on how to go about it Thanks -- View this message in context: http://www.nabble.com/Share-a- directory-using-WIx-on-install-tf4606151.html#a13152564 Sent from the wix-users mailing list archive at Nabble.com. -- --- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Default regsearch values and upgrading
On your Package element I'd change your Id= GUID to be the question marks so it auto generates each time. Or just change the GUID manually. Package Id=---- autogenuuid (Simple Type) Description Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-generated by writing all question marks like this: ----. Also allows PUT-GUID-HERE for use in examples. Pattern Type Must match the regular expression: '[{(]?[0-9A-Fa-f]{8}\-?[0-9A-Fa-f]{4}\-?[0-9A-Fa-f]{4}\-?[0-9A-Fa-f]{4}\ -?[0-9A-Fa-f]{12}[})]?|[{(]?\?{8}\-\?{4}\-\?{4}\-\?{4}\-\?{12}[})]?|PUT\ -GUID\-HERE'. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RussGreen Sent: Friday, October 12, 2007 9:37 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Default regsearch values and upgrading Thanks Chad, I tried that. I built the installer and installed it on a test machine. I then changed the product version from 2.3.2836.20968 to 2.3.2836.20970 and generated a new product GUIDeverything else stayed the same. I then rebuilt the MSI and ran it again on my test machine and got the Change\Repair\Remove dialog on the installer. This is my edited wxs file http://www.nabble.com/file/p13177036/eProject.wxs eProject.wxs What am I still missing? -- View this message in context: http://www.nabble.com/Default-regsearch-values-and-upgrading-tf4611878.h tml#a13177036 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Default regsearch values and upgrading
Thanks Chad, I tried that. I built the installer and installed it on a test machine. I then changed the product version from 2.3.2836.20968 to 2.3.2836.20970 and generated a new product GUIDeverything else stayed the same. I then rebuilt the MSI and ran it again on my test machine and got the Change\Repair\Remove dialog on the installer. This is my edited wxs file http://www.nabble.com/file/p13177036/eProject.wxs eProject.wxs What am I still missing? -- View this message in context: http://www.nabble.com/Default-regsearch-values-and-upgrading-tf4611878.html#a13177036 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to Browse network path using the BrowseDlg
I use the same control in my installer to allow the user to choose the destination folder. I purposely set Remote=no and Removable=no so they can't install to those locations. But, just out of curiosity, I set them both back to yes and rebuilt my installer. When I get to the dialog with that control the Combo dropdown does show both Removable (floppy A) and Remote (network Z) drives. I did need to map the network drive prior to being able to see it in the combo. It won't show a UNC, which seems obvious enough. I'm using WiX 2.0.5325.0 and with that version it seems to work as described. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig0ss Sent: Friday, October 12, 2007 7:05 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to Browse network path using the BrowseDlg hi there i am currently having the same, and have not yet found a salution, however if you want your floppy to be seen in the combo try this Control Id=DirectoryCombo Type=DirectoryCombo X=70 Y=55 Width=220 Height=80 Property=_BrowseProperty Removable=yes Fixed=yes Remote=yes BhaveshG wrote: Hi, I would like to select network path using the browse dialog. I do have the following code in my wxs file. Control Id=DirectoryCombo Type=DirectoryCombo X=70 Y=55 Width=220 Height=80 Property=_BrowseProperty Indirect=yes Fixed=yes Remote=yes That should now disply the floppy in the combo Even if I have set Remote=yes, I am only able to view fixed drives in the combo. Also if I have Floppy=yes, I don't see floppy drive appear in the combo as well. What could be the reason for network path not appearing? === Bhavesh -- View this message in context: http://www.nabble.com/How-to-Browse-network-path-using-the-BrowseDlg-tf3 978329.html#a13175861 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to Browse network path using the BrowseDlg
hi there i am currently having the same, and have not yet found a salution, however if you want your floppy to be seen in the combo try this Control Id=DirectoryCombo Type=DirectoryCombo X=70 Y=55 Width=220 Height=80 Property=_BrowseProperty Removable=yes Fixed=yes Remote=yes BhaveshG wrote: Hi, I would like to select network path using the browse dialog. I do have the following code in my wxs file. Control Id=DirectoryCombo Type=DirectoryCombo X=70 Y=55 Width=220 Height=80 Property=_BrowseProperty Indirect=yes Fixed=yes Remote=yes That should now disply the floppy in the combo Even if I have set Remote=yes, I am only able to view fixed drives in the combo. Also if I have Floppy=yes, I don't see floppy drive appear in the combo as well. What could be the reason for network path not appearing? === Bhavesh -- View this message in context: http://www.nabble.com/How-to-Browse-network-path-using-the-BrowseDlg-tf3978329.html#a13175861 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Default regsearch values and upgrading
Russ, I believe you're possibly missing the fact that (if I remember correctly) Windows Installer only looks as major, minor and revision (fields 1 - 3) when deciding if the version has changed... not the fourth (typically build number) field in the product version information. Check the mailing list archives for confirmation of this feature. Regards, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RussGreen Sent: Friday, October 12, 2007 12:37 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Default regsearch values and upgrading Thanks Chad, I tried that. I built the installer and installed it on a test machine. I then changed the product version from 2.3.2836.20968 to 2.3.2836.20970 and generated a new product GUIDeverything else stayed the same. I then rebuilt the MSI and ran it again on my test machine and got the Change\Repair\Remove dialog on the installer. This is my edited wxs file http://www.nabble.com/file/p13177036/eProject.wxs eProject.wxs What am I still missing? -- Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Quixote Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] QFE authoring after service pack release
Thanks Peter and Chad! I tried option 1. I may be interpreting this wrong, but I tried this without sucess: upgradeImage = newMSI (v.2002) targetImage = rtmMSI (v.1000) upgradeImage = newMSI (v.2002) targetImage = sp1MSI (v.2000) The error I get from msimsp.exe is: UpgradedImages.Upgraded = 'blah': PackageCode {4E63E3D3-591B-4403-B0D2-8065687CCC61} is not unique. I cannot find this GUID anywhere. 'blah' is Id the the second UpgradeImage I specified. Also, how do I find out more info about the validation bits? Thanks! Ning On 10/10/07, Peter Marcu [EMAIL PROTECTED] wrote: The transforms in patches usually only apply to a single baseline. In your case, you chose your RTM as your baseline. A patch can carry multiple transforms but you will need to include both in the patch if you want your patch to apply to both scenarios. The other option is to carry the single transform and set the transform validation bits to say that the transform applies to 1.0.2000 and earlier. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Chad Petersen *Sent:* Wednesday, October 10, 2007 9:26 AM *To:* Ning Lin; wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] QFE authoring after service pack release I believe the last digit of the version is ignored. You might have better luck using 1.0.2020 instead. Just a hunch. Might be worth a try. -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Ning Lin *Sent:* Wednesday, October 10, 2007 9:16 AM *To:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] QFE authoring after service pack release Resend ... Appreciate any pointers! Thanks! Ning Hello, So our scenario is this 1) Product RTM'ed (say version 1.0.1000) 2) We created and shipped a service pack 1 (say version 1.0.2000) 3) Now we realize we need to ship a QFE (say version 1.0.2002) So we created a QFE patch that is basically a diff between versions 1.0.1000 and versions 1.0.2002 -- it tries to update 1 file to version 1.0.2002. Now this QFE patch works on a machine that only has the RTM version installed, that 1 binary is updated to version 2002 as expected. On a machine that has SP1 installed, it simply does nothing! On the verbose log, it shows that it's trying to update the file to version 2000, since version 2000 is already on the machine, it does nothing. So my question is, should we author the QFE by diff'ing it to the RTM CD, or diff'ing it to the SP1 CD? Thank you for any input! Ning - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] vs help integration vsextension usage ?
Hi all, I'd like to integrate my sandcastle generated api documentation into Visual Studio and it seems that the VSExtension in Wix3 supports this. However I cannot seem to get it to compile (let alone work). I'm guessing there's something fundamental I'm missing here. What I've done: - Created the HxS file and think I've managed to create the other Hx? files appropriately. - Added the merge modules HTML_Help_Registration__RTL_X86_---.msm and VSIPCC_Collection_Files_RTL_---_---.msm - rescheduled InstallFinalize later Now I'm down to 2 errors: Error2ICE03: Not a valid foreign key; Table: HelpPlugin, Column: HelpNamespace_Parent, Key(s): MS_VSIPCC_v80.MS_VSCC_v80light.exe0 1Foo.Installer Error3ICE03: Not a valid foreign key; Table: HelpPlugin, Column: HelpNamespace_Parent, Key(s): MS_VSIPCC_v80.MS_VSExpressCC_v80light.exe 01Foo.Installer How do I fix these/successfully install the help files ? The following code is heavily inspired by the Postsharp installer and the following (and no, I don't speak russian so I'm not even sure if that is a question or answer *s*) In case it isn't obvious already the water level above my head is quite high... regards, Simon Component Id=ApiDocComponent Guid=PUT-GUID-HERE !-- Help files -- File Id=Foo.HxS Name=Foo.HxS DiskId=1 Vital=no vs:HelpFile Id=Foo.HxS Name=Foo10/ /File File Id=Foo.Documentation.HxC Name=Foo.Documentation.HxC DiskId=1 Vital=no vs:HelpCollection Id=Foo.Documentation.HxC Name=Foo10 Description=Foo 1.0 Documentation vs:HelpFileRef Id=Foo.HxS/ vs:PlugCollectionInto TableOfContents=Foo.Documentation_Toc.HxT TargetCollection=MS_VSIPCC_v80 TargetTableOfContents=FL_vsipcc_hxt_86880.3643236F_FC70_11D3_A536_0090278A1BB8/ /vs:HelpCollection /File File Id=Foo.Documentation_Toc.HxT Name=Foo.Documentation_Toc.HxT DiskId=1 Vital=no/ File Id=Foo.Documentation_AIndex.HxK Name=Foo.Documentation_AIndex.HxK DiskId=1 Vital=no/ File Id=Foo.Documentation_FIndex.HxK Name=Foo.Documentation_FIndex.HxK DiskId=1 Vital=no/ File Id=Foo.Documentation_KIndex.HxK Name=Foo.Documentation_KIndex.HxK DiskId=1 Vital=no/ File Id=Foo.Documentation_NamedUrls.HxK Name=Foo.Documentation_NamedUrls.HxK DiskId=1 Vital=no/ /Component - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users