[WiX-users] Conditions not working at all
Hi I'm trying to uninstall an old app that was made with suxxx NSIS installer and need to upgrade it to MSI. What could be the best way? I tried to make a registry search and set the UNINSTALLNSIS property. I ran MSI with debug mode and see the property has been set: MSI (c) (78:40) [15:40:42:577]: PROPERTY CHANGE: Adding UNINSTALLNSIS property. Its value is 'C:\Program Files (x86)\MyApp\uninstall.exe'. But the Condition Message I have added for debugging does not popup. I tried UNINSTALLNSIS and UNINSTALLNSIS AND NOT Installed both no success. This should only be evaluated on install as a side note. Property Id=UNINSTALLNSIS RegistrySearch Id=UNINSTALLNSIS_REGSEARCH Root=HKLM Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MyApp Name=UninstallString Type=raw / /Property Condition Message=Previous version of MyApp installed.UNINSTALLNSIS AND NOT Installed/Condition Here is the full example about what I planed to do: Property Id=UNINSTALLNSIS RegistrySearch Id=UNINSTALLNSIS_REGSEARCH Root=HKLM Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MyApp Name=UninstallString Type=raw / /Property Property Id=QtExecCmdLine Value=UNINSTALLNSIS /S/ CustomAction Id=QtMyAppUninstallWithNSIS BinaryKey=WixCA DllEntry=CAQuietExec Execute=immediate Return=check/ InstallExecuteSequence Custom Action=QtMyAppUninstallWithNSIS After=InstallInitialize/ /InstallExecuteSequence I also need to run RemoveFolderEx somewhere directly after the silent uninstall custom action as these NSIS uninstall is *very* buggy... many stale files in there. Any chance to get this RemoveFolderEx executed only if the app is removed with NSIS silent setup so I do not need to run RemoveFolderEx On=install? A newbie example would be of great help. This has been tested on WiX 3.6.1922. Regards Marc -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building Source/Learning Burn
Someone else noted recently that uninstalls aren't happening in all cases. If you have a Burn log file showing the problem, please open a bug. It sounds like something is wrong in there. On Fri, Jul 29, 2011 at 9:06 PM, JesseBearden jesse.bear...@oce.com wrote: With a little tweaking 5 out of 8 projects built, but the Setup\UX did and that was the main one I was interested in(I think). I'm still relatively new to this, and sort of tackling each different piece at the same time. For the time being I used the WixStandardBootstrapperApplication.RtfLicense to play around with with a few /extremely/ simple MSI's that I've created with WiX. For some reason the bootstrapper didn't seem to detect them when I uninstalled though. Further investigation shows that after adding ALL_USERS=1 to the installations, they uninstall with burn as expected. I won't be doing per-user installs anyhow, but is that supposed to work? Did I just miss a property somewhere? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Building-Source-Learning-Burn-tp6632488p6635575.html Sent from the wix-users mailing list archive at Nabble.com. -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] computing space requirements - takes a long time
The Windows Installer always adds a backslash to paths. I'd be really surprised if it is the adding of the backslash that takes a lot of time. When upgrading lots of existing files the Windows Installer is also preparing for how to rollback all those files that would be replaced. This is why repair/upgrade/patching can take so much longer than initial install. Remember, initial install is the trivial case. It's the other once that are harder. smile/ On Fri, Jul 29, 2011 at 10:58 AM, gapearce mr_gapea...@yahoo.com wrote: I've got an installer that has to install several hundred files, and it seems to take a long time to compute the space requirements, especially on an upgrade. During this phase, I see in a verbose log that there is a lot of work going on to just add a backslash to the end of all of the folder names being updated. There's a message like this in the log for each folder: MSI (c) (FC:1C) [13:25:08:257]: PROPERTY CHANGE: Adding dir892D072CCFBC52F1571AE901E4A5BC6F property. Its value is 'C:\Program Files (x86)\Our highest-level folder\some-lower-folder'. Then, almost immediately, there is this message following that: MSI (c) (FC:1C) [13:25:08:286]: PROPERTY CHANGE: Modifying dir892D072CCFBC52F1571AE901E4A5BC6F property. Its current value is 'C:\Program Files (x86)\Our highest-level folder\some-lower-folder'. Its new value: 'C:\Program Files (x86)\Our highest-level folder\some-lower-folder\'. The difference is that MSI added a backslash to this folder name. Is there some way to eliminate this extra work, and (even slightly) reduce the amount of time this takes? One cannot add a backslash to the name= attribute of the directory ID specification - tried that. Anyone have any suggestions? Or any suggestions in general to improve this performance? Thanks -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/computing-space-requirements-takes-a-long-time-tp6634392p6634392.html Sent from the wix-users mailing list archive at Nabble.com. -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] UAC Prompt on Minor Upgrade
All, In the past ( Windows XP ) I could install an MSI from a network share that was set up as ALLUSERS=1 / Managed. This was a properly designed/ behaving MSI ( tested with /jm ). I could then create a new installer following minor upgrade rules and drop it into the same directory on the share and my standard / non-priv. users could perform a minor upgrade. I am now trying this on Windows 7 with UAC enabled and I'm getting into a bind in that my install is requesting elevation credentials. What am I missing? One of several things that I've tried is setting the MSIDEPLOYMENTCOMPLIANT property. There is something here that I should probably already understand but for some reason I am drawing a blank. Thanks, Chris --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] UAC Prompt on Minor Upgrade
Nevermind, I figured it out. I cleared bit 3 of the Word Count Summary Property and all is behaving as I need it now. --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me From: Christopher Painter chr...@deploymentengineering.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Saturday, July 30, 2011 3:01 PM Subject: [WiX-users] UAC Prompt on Minor Upgrade All, In the past ( Windows XP ) I could install an MSI from a network share that was set up as ALLUSERS=1 / Managed. This was a properly designed/ behaving MSI ( tested with /jm ). I could then create a new installer following minor upgrade rules and drop it into the same directory on the share and my standard / non-priv. users could perform a minor upgrade. I am now trying this on Windows 7 with UAC enabled and I'm getting into a bind in that my install is requesting elevation credentials. What am I missing? One of several things that I've tried is setting the MSIDEPLOYMENTCOMPLIANT property. There is something here that I should probably already understand but for some reason I am drawing a blank. Thanks, Chris --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
