UNOFFICIAL I am using Wix version 3.9
Regards Scott Brown -----Original Message----- From: wix-users-requ...@lists.sourceforge.net [mailto:wix-users-requ...@lists.sourceforge.net] Sent: Wednesday, May 20, 2015 3:15 AM To: wix-users@lists.sourceforge.net Subject: WiX-users Digest, Vol 108, Issue 30 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. Re: Error 2911: Could not remove the folder C:\Config.Msi\. (Rob Mensching) 2. Re: Need help with uninstall (Rob Mensching) 3. Re: Wix and FinalBuilder - InvalidOperationException: Collection was modified; enumeration operation may not execute [SEC=UNOFFICIAL] (Rob Mensching) 4. Re: Burn does not show close application warning during uninstall (Phill Hogland) 5. Re: Getting ProductVersion of an msi from wix (Phil Wilson) 6. Re: How Wix bootstrapper uninstall msi package that has been upgraded (Phill Hogland) ---------------------------------------------------------------------- Message: 1 Date: Tue, 19 May 2015 16:40:28 +0000 From: Rob Mensching <r...@firegiant.com> Subject: Re: [WiX-users] Error 2911: Could not remove the folder C:\Config.Msi\. To: General discussion about the WiX toolset. <wix-users@lists.sourceforge.net> Message-ID: <by2pr04mb0475e20580d958829db936ba7...@by2pr04mb047.namprd04.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Sounds like a Windows Installer problem. _____________________________________________________________ Short replies here. Complete answers over there: http://www.firegiant.com/ -----Original Message----- From: Miroslav Rodic [mailto:rod...@arco011.com] Sent: Saturday, May 16, 2015 2:56 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Error 2911: Could not remove the folder C:\Config.Msi\. > I think that I succeeded to localize the issue, but I can not find the > solution. I forgot to say what I succeeded to localize. When there is a File element in the msi package then error message is displayed. If there is no File element at all, then the light complains that msi package is without any file ("warning LGHT1079 : The cabinet 'afile.cab' does not contain any files..."), but uninstall log of such a package does not contain the above mentioned error message. Regards, Miroslav ------------------------------ Message: 2 Date: Tue, 19 May 2015 16:42:30 +0000 From: Rob Mensching <r...@firegiant.com> Subject: Re: [WiX-users] Need help with uninstall To: General discussion about the WiX toolset. <wix-users@lists.sourceforge.net> Message-ID: <by2pr04mb04771ad70525c734d41076aa7...@by2pr04mb047.namprd04.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Did you use MSIENFORCEUPGRADECOMPONENTRULES? http://robmensching.com/blog/posts/2007/1/4/doing-a-small-update-or-minor-upgrade-in-msi-use/ _____________________________________________________________ Short replies here. Complete answers over there: http://www.firegiant.com/ -----Original Message----- From: victorwhiskey [mailto:victorhwhis...@yahoo.com] Sent: Monday, May 18, 2015 8:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Need help with uninstall Hello all, I'm having trouble with uninstalling my product after I do a minor upgrade. So I test with installing my program and then uninstalling the program and that works fine. Then the next test is install the program (v.1.0.0.x) then do a minor upgrade (upgrade to v.1.0.2.y). That works fine. Next I try to uninstall the program. Here's where I run into my problem. The program gets removed from ARP making it seem like it's uninstalled, however, all directories and files still exist after the uninstall. I've compared the logs and the difference I see is when it lists the components and their states, in the "good" log it says "...Request: Absent; Action: Absent" signifying a remove. However in the "bad" log it says " Request: Null, Action: Null" signifying no action. The Product.wxs contains. ... <Product Id="$(var.ProductCode)" Name="$(var.ProductName)" Language="1033" Version="!(bind.FileVersion.fil12413D1AEB784C72BBAD4277614C2F22)" Manufacturer="$(var.Manufacturer)" UpgradeCode="$(var.UpgradeCode)"> ... <MajorUpgrade AllowDowngrades="no" AllowSameVersionUpgrades="yes" Disallow="no" DowngradeErrorMessage="A newer version of [ProductName] is already installed." IgnoreRemoveFailure="no" MigrateFeatures="yes" Schedule="afterInstallInitialize"/> ... I'm running this from a bundle using wix3.8 and will try to attach the logs. Any help appreciated! Thanks good.log <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7600353/good.log> bad.log <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7600353/bad.log> ------------------------------ Message: 3 Date: Tue, 19 May 2015 16:45:01 +0000 From: Rob Mensching <r...@firegiant.com> Subject: Re: [WiX-users] Wix and FinalBuilder - InvalidOperationException: Collection was modified; enumeration operation may not execute [SEC=UNOFFICIAL] To: General discussion about the WiX toolset. <wix-users@lists.sourceforge.net> Message-ID: <by2pr04mb0473c85d3110e9e68f9cf65a7...@by2pr04mb047.namprd04.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Always possible. There's a probably a couple 100,000 lines of code in the WiX toolset. Dropping .pdbs next to the tools and getting the resulting call stack would narrow it down to which line of code is offending. Plus, knowing which version of the WiX toolset would help too since the code keeps changing with each build. _____________________________________________________________ Short replies here. Complete answers over there: http://www.firegiant.com/ -----Original Message----- From: Scott Brown [mailto:scott.br...@aec.gov.au] Sent: Tuesday, May 19, 2015 1:06 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix and FinalBuilder - InvalidOperationException: Collection was modified; enumeration operation may not execute [SEC=UNOFFICIAL] UNOFFICIAL Hi Wix Users While running a build in FinalBuilder, when it gets up to the Wix installer project and runs the linker light.exe, I get the following error "InvalidOperationException: Collection was modified; enumeration operation may not execute." Does anyone know what could cause this? This error is supposed to occur when adding or removing items while looping over a collection. Does light.exe do this? Regards Scott Brown ------------------------------ Message: 4 Date: Tue, 19 May 2015 10:01:38 -0700 (MST) From: Phill Hogland <phogl...@rimage.com> Subject: Re: [WiX-users] Burn does not show close application warning during uninstall To: wix-users@lists.sourceforge.net Message-ID: <1432054898967-7600367.p...@n2.nabble.com> Content-Type: text/plain; charset=us-ascii I use a bundle to drive my msi packages. Generally I use util:RestartResource but some time ago I used util:CloseApplication. I do not recall observing the scenario that you described, however I do know that the underlying API used in either case, util:RestartResource or util:CloseApplication, depends on the ability to send a Widows Message from one application context to another. IF the targeted application is running in a different user context then there can be issues with passing any Windows Message from one Winstation/Desktop to another. (With regard to this issue related to util:RestartResource there is more info here <http://wixtoolset.org/issues/4592/> .) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-does-not-show-close-application-warning-during-uninstall-tp7593156p7600367.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------ Message: 5 Date: Tue, 19 May 2015 10:02:27 -0700 From: Phil Wilson <phildgwil...@gmail.com> Subject: Re: [WiX-users] Getting ProductVersion of an msi from wix To: "General discussion about the WiX toolset." <wix-users@lists.sourceforge.net> Message-ID: <CACZvpRZyp4_=8s411ugpizz2jgm9haby6qmbnk9zkvdtpfg...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 To me at least that's not the problem you're describing - that's a restatement of your solution, the implementation of which is to block an MSI install if another product is already installed. Anyway, it looks like you'll need to write code to do this as outlined earlier based on detection of an installed product with that UpgradeCode. Would it be a hardship to move to 3.9 WiX? If there is way of dealing with your problem by doing it in the MSI with an upgrade element to "onlydetect" the installed product, and have the MSI behave differently then that would be a possible solution, which is why it might help to know the problem your detection of that product is going to solve. --------------- Phil Wilson On Mon, May 18, 2015 at 4:24 PM, Rajesh Nagpal <rnag...@microsoft.com> wrote: > Hi Phil, > > Comments inline for your queries: > /It might help to say why you want to do this and what problem it > solves./ > > I need to add a blocking condition based on whether a particular msi > is installed or not and hence I need a way to figure out whether that > msi is installed or not. > > /You don't mention version either except in the subject line, so some > clarification about that might help. / Not sure which version you are > talking about. I'm using Wix 3.8 if that's what you wanted to know. > > I got around this problem by finding a registry that gave me the > version(same as product version). > > Thanks for your response. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Getting- > ProductVersion-of-an-msi-from-wix-tp7600320p7600357.html > Sent from the wix-users mailing list archive at Nabble.com. > > ---------------------------------------------------------------------- > -------- One dashboard for servers and applications across > Physical-Virtual-Cloud Widest out-of-the-box monitoring support with > 50+ applications Performance metrics, stats and reports that give you > Actionable Insights Deep dive visibility with transaction tracing > using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------ Message: 6 Date: Tue, 19 May 2015 10:15:10 -0700 (MST) From: Phill Hogland <phogl...@rimage.com> Subject: Re: [WiX-users] How Wix bootstrapper uninstall msi package that has been upgraded To: wix-users@lists.sourceforge.net Message-ID: <1432055710640-7600369.p...@n2.nabble.com> Content-Type: text/plain; charset=us-ascii In each msi use the MajorUpgrade element and increment the first three sections of the MSI version (i.e 1.0.0.0 to 1.0.1.0, and not 1.0.0.1) When building the second release of the bootstrapper, leave all of the MSIs in the first release in the chain and only change the MSI B if that is what is changing. Burn will update only what has changed, but the unchanged MSI A must be there to avoid uninstalling it. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-Wix-bootstrapper-uninstall-msi-package-that-has-been-upgraded-tp7600359p7600369.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------ ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users End of WiX-users Digest, Vol 108, Issue 30 ****************************************** UNOFFICIAL DISCLAIMER: If you have received this transmission in error please notify us immediately by return email and delete all copies. If this email or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the email or attachments. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
