@Nir, Yep I figured that out. I used REMOVE~=ALL based on Rob's answer
given at http://stackoverflow.com/a/321874/2634612 .
On Tue, Mar 24, 2015 at 12:30 PM, Nir Bar nir@panel-sw.com wrote:
You should use REMOVE, not Remove - case matters.
-
Nir Bar
Freelance Developer
Mail:
You should use REMOVE, not Remove - case matters.
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX InstallShield
--
View this message in context:
You can condition it on REMOVE
https://msdn.microsoft.com/en-us/library/aa371194%28v=vs.85%29.aspx
property instead of Installed.
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX InstallShield
@Nir Bar, I tried to Use Remove property instead of Installed. But the
Custom Action didn't Run when the Remove Property was set.
@Rob I tried to use util:RemoveFolderEx based on this link =
https://www.hass.de/content/wix-how-use-removefolderex-your-xml-scripts but
without using Registry
Hi Rob, Thanks. I think RemoveFolderEx is present in WixUtil. I will give
it a go. For the user to prevent running installer again, if product is
installed, How do I show a pop up indicating the product is installed?
Thanks.
On Mon, Mar 23, 2015 at 10:12 PM, Rob Mensching r...@firegiant.com
Was there a reason you wrote a CA to remove the file? Would RemoveFile / not
suffice?
On Mar 23, 2015, at 10:53 AM, Nir Bar nir@panel-sw.com wrote:
You can condition it on REMOVE
https://msdn.microsoft.com/en-us/library/aa371194%28v=vs.85%29.aspx
property instead of Installed.
I need to Remove Folders as well. RemoveFile only works to delete the File,
I think so. The executable could create Folder within folder and files too.
On Mon, Mar 23, 2015 at 9:41 PM, Hoover, Jacob jacob.hoo...@greenheck.com
wrote:
Was there a reason you wrote a CA to remove the file? Would
Generally you don't need to worry about the user running the same MSI
again. For example, if you are using a Wix UI then running the same
MSI again results in a Change/Repair/Remove dialog. Running the same
MSI again doesn't result in installing the product again (or a copy of
it) but it does
I have created two custom actions that does the following jobs:
1. Create a file based on the property passed to the installer. eg
msiexec /i installer.msi /l*v out.txt IPADDRESS=192.168.2.2.08
The custom action will create a file that will contain the data as:
{
ip:192.168.2.208
}
2. Another
RemoveFoldersEx?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Sarvagya Pant [mailto:sarvagya.p...@gmail.com]
Sent: Monday, March 23, 2015 9:05 AM
To: General discussion
Wix handles that scenario by default. If you run an install for a product
installed, it will typically take you to maintenance mode(repair/remove).
-Original Message-
From: Sarvagya Pant [mailto:sarvagya.p...@gmail.com]
Sent: Monday, March 23, 2015 9:44 AM
To: General discussion about
You can also use msiext http://dblock.github.io/msiext/ extension that
has a DeleteFiles element.
It should be conditioned like you would a custom action, unlike
RemoveFolderEx which is conditioned by default by it's containing
component's action.
-
Nir Bar
Freelance Developer
Mail:
Modifying resources should be tied to Components.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Nir Bar [mailto:nir@panel-sw.com]
Sent: Monday, March 23, 2015 11:17
13 matches
Mail list logo
