[WiX-users] RemoveFoldersEX error in VS2005

Hi, I am trying to use the new RemoveFoldersEx facility in 3.6.1321.0 Build using VS2005 gives an Error - Error4The Component element contains an unhandled extension element 'util:RemoveFolderEx'. Please ensure that the extension for elements in the 'http://schemas.microsoft.com/wix/W

Re: [WiX-users] Unmanaged c++ window service installation

FWIW, we use the built in functionality that Christopher is talking about in 4 different services and have not had any issues with it... -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Saturday, February 12, 2011 9:48 PM To: General discussion

Re: [WiX-users] Unmanaged c++ window service installation

You are welcome!   This simple answer is the source of my frustration for the last 5 years.  If you create a .NET service and run it from the command line it will even say something to the effect of "you must use installutil"    and if you go to the local bookstore and pick up any book on .N

Re: [WiX-users] Unmanaged c++ window service installation

Thank You. That would make sense. If .net service installer is out of the picture then SCM is all what matters and then service is a service. -Original Message- From: Christopher Painter Sent: Saturday, February 12, 2011 5:21 PM To: General discussion for Windows Installer XML toolset. S

Re: [WiX-users] Unmanaged c++ window service installation

That's a bit of a trick question because it assumes one should use custom actions in the first place.   I always use the built-in standard actions as encapsulated by the WiX elements ServiceInstall and ServiceControl. A service is a service is a service.  The Service Control Manager has an API

[WiX-users] Unmanaged c++ window service installation

1. Is there any difference between installing managed windows services versus unmanaged ones using standard custom actions? 2. If yes then what is the best way to install unmanaged windows service (any examples?) I just wanted to get some feedback from you guys to save some time since I am not

Re: [WiX-users] Unable to change or propagate the value of a directory whose parent is changed via custom action

Try using the "Directory" attribute instead of the "Property" attribute in your custom actions. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unable-to-change-or-propagate-the-value-of-a-directory-whose-parent-is-changed-via-custom-action-tp601665

Re: [WiX-users] Immediate custom actions with and without UI

Thanks all for the replies. CustomAction/@Execute = "firstSequence" is exactly what I needed (I do indeed need the custom action to run before the UI). -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Stu