Re: [WiX-users] Removing through the UI mode does not prompt for privileges
I already have that condition in the code...So that didn't help with elevation. I really think that it's the feature installation condition, because when I made the feature install without a conditional set of it's level, it worked as I want it to... So there must be a reason why this happens... -Original Message- From: Sameer Arora [mailto:arora...@gmail.com] Sent: 22 December 2011 22:41 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not prompt for privileges If the requirement was to invoke elevation prompt for both install and uninstall (be it in from Program and Features or through the Maintenance mode) will this work?: add this condition somewhere in the scope Privileged I understand "Admin privileges" may mean different from "Elevation" that you were looking for. Sameer On Thu, Dec 22, 2011 at 5:23 AM, Stelios Kyprou wrote: > Ok it seems that Remove=ALL was not set for the following reason: > One of the features had a conditional installation, as following: > > Level="0"> > > > > > > And when uninstalling via the UI REMOVE was not set to ALL. > ALSO, I noticed the components of that Feature were not removed from > the installation directory either... > Is there a scenario where STSADM2010 gets set when installing and NOT > when re-running the installer for removal? > This is how I set the property in product.wxs: > > >Path="[CommonFiles64Folder]Microsoft Shared\web server extensions\14\bin"> > > > > > Thanks, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 16:06 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > Sorry I am not a UI expert as we use a chainer for our UI. > > I think your Maintenance UI needs to be setting the REMOVE to all somehow. > Try looking in the wix standard or mondo UI to see how that does it. > > If your CA needs to be dependent on the MSI being uninstalled it needs > to be scheduled appropriately, i.e. after the REMOVE has been set correctly. > > Dave > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:45 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > By the way my CA is scheduled AFTER InstallInitialize > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:42 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > You are right David, REMOVE was set to the features that were installed. > So I changed the condition so that the CA runs. > One problem down. > Now after completion, I can still see the product in "Products and > Features", and the files are not removed from the install location. > What do I need to do so that my Remove action via ui does the same > thing as when running the uninstallation process via "Products and Features"? > > Thanks in advance, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 14:52 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > When is your custom action scheduled? > > When you uninstall through the MSI your MSI is in maintenance mode. > This probably means that REMOVE is not set to ALL by default in case > you choose some other behaviour. > Check a log to see when REMOVE is being set and what to. > > > -Original Message- > From: Dan Gough [mailto:goug...@gmail.com] > Sent: 21 December 2011 13:20 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > I'm new to WiX so don't know how to do it, but I think you need the > elevation shield attribute 0x0080 set in the Control table on the > button used to uninstall the application. Try editing the msi package > using InstEd to see if it fixes the problem, then you can figure out > how to achieve it in WiX. > On Dec 21, 2011 11:55 AM, "Stelios Kyprou" wrote: > > > I don't think that is the problem...I need to provide same > > functionality when uninstalling from Programs and Features for when > > I uninstall through the MSI. > > I found in the logs the following: > > > > MSI (s) (C0:08) [11:23:34:638]: Skipping action: > > UninstallWsp2010PowerShell (condition is false) The condition is: > > which should be true when > > uninstalling(Executes from Programs and Features, but not from the > "Remove" > > action of the msi). > > > > > > -Original Message- > > From: Karthick R [mailto:karthi...@sync
Re: [WiX-users] Removing through the UI mode does not promptfor privileges
Feature conditions are always a pain to work out. Could you move the condition onto the component(s)? -Original Message- From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] Sent: 23 December 2011 09:47 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not promptfor privileges I already have that condition in the code...So that didn't help with elevation. I really think that it's the feature installation condition, because when I made the feature install without a conditional set of it's level, it worked as I want it to... So there must be a reason why this happens... -Original Message- From: Sameer Arora [mailto:arora...@gmail.com] Sent: 22 December 2011 22:41 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not prompt for privileges If the requirement was to invoke elevation prompt for both install and uninstall (be it in from Program and Features or through the Maintenance mode) will this work?: add this condition somewhere in the scope Privileged I understand "Admin privileges" may mean different from "Elevation" that you were looking for. Sameer On Thu, Dec 22, 2011 at 5:23 AM, Stelios Kyprou wrote: > Ok it seems that Remove=ALL was not set for the following reason: > One of the features had a conditional installation, as following: > > Level="0"> > > > > > > And when uninstalling via the UI REMOVE was not set to ALL. > ALSO, I noticed the components of that Feature were not removed from > the installation directory either... > Is there a scenario where STSADM2010 gets set when installing and NOT > when re-running the installer for removal? > This is how I set the property in product.wxs: > > >Path="[CommonFiles64Folder]Microsoft Shared\web server extensions\14\bin"> > > > > > Thanks, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 16:06 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > Sorry I am not a UI expert as we use a chainer for our UI. > > I think your Maintenance UI needs to be setting the REMOVE to all somehow. > Try looking in the wix standard or mondo UI to see how that does it. > > If your CA needs to be dependent on the MSI being uninstalled it needs > to be scheduled appropriately, i.e. after the REMOVE has been set correctly. > > Dave > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:45 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > By the way my CA is scheduled AFTER InstallInitialize > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:42 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > You are right David, REMOVE was set to the features that were installed. > So I changed the condition so that the CA runs. > One problem down. > Now after completion, I can still see the product in "Products and > Features", and the files are not removed from the install location. > What do I need to do so that my Remove action via ui does the same > thing as when running the uninstallation process via "Products and Features"? > > Thanks in advance, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 14:52 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > When is your custom action scheduled? > > When you uninstall through the MSI your MSI is in maintenance mode. > This probably means that REMOVE is not set to ALL by default in case > you choose some other behaviour. > Check a log to see when REMOVE is being set and what to. > > > -Original Message- > From: Dan Gough [mailto:goug...@gmail.com] > Sent: 21 December 2011 13:20 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > I'm new to WiX so don't know how to do it, but I think you need the > elevation shield attribute 0x0080 set in the Control table on the > button used to uninstall the application. Try editing the msi package > using InstEd to see if it fixes the problem, then you can figure out > how to achieve it in WiX. > On Dec 21, 2011 11:55 AM, "Stelios Kyprou" wrote: > > > I don't think that is the problem...I need to provide same > > functionality when uninstalling from Programs and Features for when > > I uninstall through the MSI. > > I found in the logs the follo
Re: [WiX-users] Removing through the UI mode does not promptfor privileges
Yeah could do! I'm not showing the feature selection screen so it shouldn't matter. Will let you know if it works -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: 23 December 2011 10:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not promptfor privileges Feature conditions are always a pain to work out. Could you move the condition onto the component(s)? -Original Message- From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] Sent: 23 December 2011 09:47 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not promptfor privileges I already have that condition in the code...So that didn't help with elevation. I really think that it's the feature installation condition, because when I made the feature install without a conditional set of it's level, it worked as I want it to... So there must be a reason why this happens... -Original Message- From: Sameer Arora [mailto:arora...@gmail.com] Sent: 22 December 2011 22:41 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not prompt for privileges If the requirement was to invoke elevation prompt for both install and uninstall (be it in from Program and Features or through the Maintenance mode) will this work?: add this condition somewhere in the scope Privileged I understand "Admin privileges" may mean different from "Elevation" that you were looking for. Sameer On Thu, Dec 22, 2011 at 5:23 AM, Stelios Kyprou wrote: > Ok it seems that Remove=ALL was not set for the following reason: > One of the features had a conditional installation, as following: > > Level="0"> > > > > > > And when uninstalling via the UI REMOVE was not set to ALL. > ALSO, I noticed the components of that Feature were not removed from > the installation directory either... > Is there a scenario where STSADM2010 gets set when installing and NOT > when re-running the installer for removal? > This is how I set the property in product.wxs: > > >Path="[CommonFiles64Folder]Microsoft Shared\web server extensions\14\bin"> > > > > > Thanks, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 16:06 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > Sorry I am not a UI expert as we use a chainer for our UI. > > I think your Maintenance UI needs to be setting the REMOVE to all somehow. > Try looking in the wix standard or mondo UI to see how that does it. > > If your CA needs to be dependent on the MSI being uninstalled it needs > to be scheduled appropriately, i.e. after the REMOVE has been set correctly. > > Dave > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:45 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > By the way my CA is scheduled AFTER InstallInitialize > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:42 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > You are right David, REMOVE was set to the features that were installed. > So I changed the condition so that the CA runs. > One problem down. > Now after completion, I can still see the product in "Products and > Features", and the files are not removed from the install location. > What do I need to do so that my Remove action via ui does the same > thing as when running the uninstallation process via "Products and Features"? > > Thanks in advance, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 14:52 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > When is your custom action scheduled? > > When you uninstall through the MSI your MSI is in maintenance mode. > This probably means that REMOVE is not set to ALL by default in case > you choose some other behaviour. > Check a log to see when REMOVE is being set and what to. > > > -Original Message- > From: Dan Gough [mailto:goug...@gmail.com] > Sent: 21 December 2011 13:20 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > I'm new to WiX so don't know how to do it, but I think you need the > elevation shield attribute 0x0080 set in the Control table on the > button used to uninstall the application. Try editing the msi
Re: [WiX-users] Removing through the UI mode does not promptfor privileges
That didn't seem to work either ... -Original Message- From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] Sent: 23 December 2011 11:04 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not promptfor privileges Yeah could do! I'm not showing the feature selection screen so it shouldn't matter. Will let you know if it works -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: 23 December 2011 10:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not promptfor privileges Feature conditions are always a pain to work out. Could you move the condition onto the component(s)? -Original Message- From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] Sent: 23 December 2011 09:47 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not promptfor privileges I already have that condition in the code...So that didn't help with elevation. I really think that it's the feature installation condition, because when I made the feature install without a conditional set of it's level, it worked as I want it to... So there must be a reason why this happens... -Original Message- From: Sameer Arora [mailto:arora...@gmail.com] Sent: 22 December 2011 22:41 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not prompt for privileges If the requirement was to invoke elevation prompt for both install and uninstall (be it in from Program and Features or through the Maintenance mode) will this work?: add this condition somewhere in the scope Privileged I understand "Admin privileges" may mean different from "Elevation" that you were looking for. Sameer On Thu, Dec 22, 2011 at 5:23 AM, Stelios Kyprou wrote: > Ok it seems that Remove=ALL was not set for the following reason: > One of the features had a conditional installation, as following: > > Level="0"> > > > > > > And when uninstalling via the UI REMOVE was not set to ALL. > ALSO, I noticed the components of that Feature were not removed from > the installation directory either... > Is there a scenario where STSADM2010 gets set when installing and NOT > when re-running the installer for removal? > This is how I set the property in product.wxs: > > >Path="[CommonFiles64Folder]Microsoft Shared\web server extensions\14\bin"> > > > > > Thanks, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 16:06 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > Sorry I am not a UI expert as we use a chainer for our UI. > > I think your Maintenance UI needs to be setting the REMOVE to all somehow. > Try looking in the wix standard or mondo UI to see how that does it. > > If your CA needs to be dependent on the MSI being uninstalled it needs > to be scheduled appropriately, i.e. after the REMOVE has been set correctly. > > Dave > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:45 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > By the way my CA is scheduled AFTER InstallInitialize > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:42 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > You are right David, REMOVE was set to the features that were installed. > So I changed the condition so that the CA runs. > One problem down. > Now after completion, I can still see the product in "Products and > Features", and the files are not removed from the install location. > What do I need to do so that my Remove action via ui does the same > thing as when running the uninstallation process via "Products and Features"? > > Thanks in advance, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 14:52 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > When is your custom action scheduled? > > When you uninstall through the MSI your MSI is in maintenance mode. > This probably means that REMOVE is not set to ALL by default in case > you choose some other behaviour. > Check a log to see when REMOVE is being set and what to. > > > -Original Message- > From: Dan Gough [mailto:goug...@gmail.com] > Sent: 21 December 2011 13:20 > To: General discussion for Windows Installer XML toolset. > Subje
[WiX-users] Cascading Merg Modules
I have a question about design of installer and merge modules. I have a COM server as base component. This is reusable and must be used a by a tool. Further this tool may be part of a product. BaseComponent + Tool -> ToolInstaller BaseComponent + Tool + Application -> ProductInstaller I want to design the best set of WiX projects. Since the base component is reusable it should be implemented with a merge module, shouldn't it? When I build the tool installer I will use a WiX product project to generate a MSI file. But how should I integrate the tool installation in the product? One solution would be a tool merge module. But does the product always have to add the tool merge module and the base component merge module. Or can I design the tool merge module to "include" the base component? How can a wix library help here? -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Cascading Merg Modules
Hi, You only need to use merge modules if you want to supply them to third parties for use in their installations that do not use wix. If you do not have this requirement then you can split your installer up to use a Base and tool wixlib when then can be linked into the tool and product MSIs. Think of a wixlib as a c static linked library, you would have two separate ones and link them both into the resultant MSI. You can also have several wix fragments and build each MSI from combining the appropriate source files without bothering with a wixlib. Dave -Original Message- From: Andreas [mailto:andreassand...@gmx.net] Sent: 23 December 2011 13:42 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Cascading Merg Modules I have a question about design of installer and merge modules. I have a COM server as base component. This is reusable and must be used a by a tool. Further this tool may be part of a product. BaseComponent + Tool -> ToolInstaller BaseComponent + Tool + Application -> ProductInstaller I want to design the best set of WiX projects. Since the base component is reusable it should be implemented with a merge module, shouldn't it? When I build the tool installer I will use a WiX product project to generate a MSI file. But how should I integrate the tool installation in the product? One solution would be a tool merge module. But does the product always have to add the tool merge module and the base component merge module. Or can I design the tool merge module to "include" the base component? How can a wix library help here? - - Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Removing through the UI modedoes not promptfor privileges
At this stage it may be trial an error of removing suspect looking bits from your MSI and retesting. It would be helpful to see a log probably. -Original Message- From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] Sent: 23 December 2011 11:29 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI modedoes not promptfor privileges That didn't seem to work either ... -Original Message- From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] Sent: 23 December 2011 11:04 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not promptfor privileges Yeah could do! I'm not showing the feature selection screen so it shouldn't matter. Will let you know if it works -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: 23 December 2011 10:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not promptfor privileges Feature conditions are always a pain to work out. Could you move the condition onto the component(s)? -Original Message- From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] Sent: 23 December 2011 09:47 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not promptfor privileges I already have that condition in the code...So that didn't help with elevation. I really think that it's the feature installation condition, because when I made the feature install without a conditional set of it's level, it worked as I want it to... So there must be a reason why this happens... -Original Message- From: Sameer Arora [mailto:arora...@gmail.com] Sent: 22 December 2011 22:41 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing through the UI mode does not prompt for privileges If the requirement was to invoke elevation prompt for both install and uninstall (be it in from Program and Features or through the Maintenance mode) will this work?: add this condition somewhere in the scope Privileged I understand "Admin privileges" may mean different from "Elevation" that you were looking for. Sameer On Thu, Dec 22, 2011 at 5:23 AM, Stelios Kyprou wrote: > Ok it seems that Remove=ALL was not set for the following reason: > One of the features had a conditional installation, as following: > > Level="0"> > > > > > > And when uninstalling via the UI REMOVE was not set to ALL. > ALSO, I noticed the components of that Feature were not removed from > the installation directory either... > Is there a scenario where STSADM2010 gets set when installing and NOT > when re-running the installer for removal? > This is how I set the property in product.wxs: > > >Path="[CommonFiles64Folder]Microsoft Shared\web server extensions\14\bin"> > > > > > Thanks, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 16:06 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > Sorry I am not a UI expert as we use a chainer for our UI. > > I think your Maintenance UI needs to be setting the REMOVE to all somehow. > Try looking in the wix standard or mondo UI to see how that does it. > > If your CA needs to be dependent on the MSI being uninstalled it needs > to be scheduled appropriately, i.e. after the REMOVE has been set correctly. > > Dave > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:45 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode doesnot prompt > forprivileges > > By the way my CA is scheduled AFTER InstallInitialize > > -Original Message- > From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im] > Sent: 21 December 2011 15:42 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > You are right David, REMOVE was set to the features that were installed. > So I changed the condition so that the CA runs. > One problem down. > Now after completion, I can still see the product in "Products and > Features", and the files are not removed from the install location. > What do I need to do so that my Remove action via ui does the same > thing as when running the uninstallation process via "Products and Features"? > > Thanks in advance, > Stelios > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 21 December 2011 14:52 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Removing through the UI mode does not prompt > forprivileges > > When is your custom action scheduled? > > When you uninstall
