Re: Deleting files in a patch. Applying the same logic to a patch does not work. We set the component id for new files that do not need to be registered to null. (to allow for deletion in future patches) Then apply the patch. Resulting in the null component id files not getting installed.
-----Original Message----- From: wix-users-requ...@lists.sourceforge.net [mailto:wix-users-requ...@lists.sourceforge.net] Sent: Tuesday, January 14, 2014 11:40 AM To: wix-users@lists.sourceforge.net Subject: WiX-users Digest, Vol 92, Issue 23 Send WiX-users mailing list submissions to wix-users@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/wix-users or, via email, send a message with subject or body 'help' to wix-users-requ...@lists.sourceforge.net You can reach the person managing the list at wix-users-ow...@lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of WiX-users digest..." Today's Topics: 1. (Please Ignore earlier mail)Creating an installer with spaces in the name with LIGHT command (Suvrajyoti Panda) 2. Re: How to get package version using burn API (Phill Hogland) 3. Re: How to get package version using burn API (Rob Mensching) 4. Re: How to get package version using burn API (Phill Hogland) 5. Re: How to get package version using burn API (Phill Hogland) 6. Re: Deleting files in a patch... (Phil Wilson) 7. Re: How to get package version using burn API (Hoover, Jacob) ---------------------------------------------------------------------- Message: 1 Date: Tue, 14 Jan 2014 15:57:00 +0530 From: Suvrajyoti Panda <suvrajyo...@contata.co.in> Subject: [WiX-users] (Please Ignore earlier mail)Creating an installer with spaces in the name with LIGHT command To: "General discussion about the WiX toolset." <wix-users@lists.sourceforge.net> Message-ID: <52d510f4.9040...@contata.co.in> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi All, I want to create an installer in WIX that has spaces in its name something as shown below: light -out C:\Pipeline Scheduler Tortoise.msi C:\TortInstall.wixobj C:\db.wixobj How can i achieve the same? Please help on this if any body has encountered this before. Regards, SuvraJyoti ------------------------------ Message: 2 Date: Tue, 14 Jan 2014 09:56:45 -0800 (PST) From: Phill Hogland <phogl...@rimage.com> Subject: Re: [WiX-users] How to get package version using burn API To: wix-users@lists.sourceforge.net Message-ID: <1389722205148-7591749.p...@n2.nabble.com> Content-Type: text/plain; charset=us-ascii As Tom indicated I added custom tables with BootstrapperApplicationData="yes" and then the following link was helpful in deserializing the data. http://stackoverflow.com/questions/12846421/getting-display-name-from-packageid -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-package-version-using-burn-API-tp7591717p7591749.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------ Message: 3 Date: Tue, 14 Jan 2014 18:06:30 +0000 From: Rob Mensching <r...@robmensching.com> Subject: Re: [WiX-users] How to get package version using burn API To: General discussion about the WiX toolset. <wix-users@lists.sourceforge.net> Message-ID: <fcdde0fe73f24f0c9a69d28d01cc7...@bn1pr07mb181.namprd07.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" :( Wish someone would help improve the WiX toolset instead of everyone doing workarounds. :( -----Original Message----- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Tuesday, January 14, 2014 9:57 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to get package version using burn API As Tom indicated I added custom tables with BootstrapperApplicationData="yes" and then the following link was helpful in deserializing the data. http://stackoverflow.com/questions/12846421/getting-display-name-from-packageid -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-package-version-using-burn-API-tp7591717p7591749.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------ Message: 4 Date: Tue, 14 Jan 2014 11:12:02 -0800 (PST) From: Phill Hogland <phogl...@rimage.com> Subject: Re: [WiX-users] How to get package version using burn API To: wix-users@lists.sourceforge.net Message-ID: <1389726722830-7591751.p...@n2.nabble.com> Content-Type: text/plain; charset=us-ascii I implemented the approach to passing data from my bundle via the BootstrapperApplicationData.xml to the mba some time ago. But today I came across a much easier approach. I commented out the custom table and the BootsrapperApplicationData class (which I had modified from the sample code in the link mentione earlier) and replaced it with the following. In the bundle wxs I created a variable like this: <Variable Name='MyBundleVer' Value='$(var.ProductVer)' Type='string' Persisted='yes' /> Since I am only displaying the data I did not need the bal:Overridable='yes' in the above element. And in the mba to get this string variable I do: public string Version { get { //return MymbaUX.BootApplicationData.Data.Version; return MymbaUX.Model.Engine.StringVariables["MyBundleVer"]; } } I'm sure there are advantages to the other approach for large amounts of data, but I just needed to display the version of the bundle in the title of my main window. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-package-version-using-burn-API-tp7591717p7591751.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------ Message: 5 Date: Tue, 14 Jan 2014 11:15:55 -0800 (PST) From: Phill Hogland <phogl...@rimage.com> Subject: Re: [WiX-users] How to get package version using burn API To: wix-users@lists.sourceforge.net Message-ID: <1389726955682-7591752.p...@n2.nabble.com> Content-Type: text/plain; charset=us-ascii >>>Wish someone would help improve the WiX toolset instead of everyone >>>doing workarounds. I am very interested in doing that, however aside from some sickness in the family that took me offline last week, I am still struggling with understanding the git push - pull process. I hear that the way I download the source from codeplex as a zip package is "unsupported" (but it also builds works for me). -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-package-version-using-burn-API-tp7591717p7591752.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------ Message: 6 Date: Tue, 14 Jan 2014 11:29:15 -0800 From: Phil Wilson <phildgwil...@gmail.com> Subject: Re: [WiX-users] Deleting files in a patch... To: "General discussion for Windows Installer XML toolset." <wix-users@lists.sourceforge.net> Message-ID: <CACZvpRZkcKk5z_XAk8ZdRchhJpcmwo1OH5+4AS5AuohBtXz=x...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 It looks like you hijacked an existing discussion thread, so I'll start a new one. ... Yes, that's the way it works. That might not be the best way to remove files if you decide you want them back later. An alternative is to make the component transitive and use a property to make the actual file be present or absent, so if you later decide you want the file present just set the property value. It can be tricky to make that work in all cases, such as adding/removing features, repair, patches etc because you need to preserve the property value that is keeping the file present or absent. "The msdn doc says the following for component id in the column table. ComponentId --> If this column is null the installer does not register the component and the component cannot be removed or repaired by the installer. This might be intentionally done if the component is only needed during the installation, such as a custom action that cleans up temporary files or removes an old product. It may also be useful when copying data files to a user's computer that do not need to be registered. Does this mean in the full msi, components with null id will not be registered and if deleted then will not put the msi in repair? Which further indicates that at patch time we can call a custom action to delete these components , and this will not throw the msi in repair mode?" Phil Wilson ------------------------------ Message: 7 Date: Tue, 14 Jan 2014 19:39:56 +0000 From: "Hoover, Jacob" <jacob.hoo...@greenheck.com> Subject: Re: [WiX-users] How to get package version using burn API To: General discussion about the WiX toolset. <wix-users@lists.sourceforge.net> Message-ID: <61d0a1ed0452f744bd7fe991abc2196fbdb02...@exbox2.greenops.com> Content-Type: text/plain; charset="us-ascii" Tis not too difficult, and there are plenty willing to help from wix-devs. http://wixtoolset.org/development/ http://wixtoolset.org/documentation/manual/v3/wixdev/ Skeleton cliff notes are: 1) Join wix-devs 2) Sign the assignment agreement 3) Fork the git repository on codeplex (https://wix.codeplex.com/SourceControl/latest) 4) Clone your fork (git clone https://git01.codeplex.com/forks/<username>/<fork name>) 5) Checkout the branch you want to work on (git checkout -b origin/wix39) << This creates a local branch for tracking the origin/wix39 branch, and then checks it out. 6) Create a feature branch (git branch uberfeature) 7) Check out feature branch (git checkout uberfeature) 8) Make changes 9) Commit changes (git add ..., git commit -m "Uber feature!" 10) Push changes to your fork (git push origin uberfeature) At that point, you could go to codeplex and submit a pull request. If uberfeature is behind the upstream/wix39 branch, then there may be a need to add an upstream and merge those commits into your origin/wix39 and local wix39 branches. From there, my preference is to rebase uberfeature on the updated wix39 branch and push it. -----Original Message----- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Tuesday, January 14, 2014 1:16 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to get package version using burn API >>>Wish someone would help improve the WiX toolset instead of everyone >>>doing workarounds. I am very interested in doing that, however aside from some sickness in the family that took me offline last week, I am still struggling with understanding the git push - pull process. I hear that the way I download the source from codeplex as a zip package is "unsupported" (but it also builds works for me). -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-package-version-using-burn-API-tp7591717p7591752.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------ ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users End of WiX-users Digest, Vol 92, Issue 23 ***************************************** ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
