Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Can ClickOnce and Setup & Deployment Projects replace Wix?
 

Can ClickOnce and Setup & Deployment Projects replace Wix?

Hi All

Currently we are using Wix to create msi files. I feel it's difficult to maintain and look for another way for our build automation. What's the other options? We want to setup build automation either from TFS, or from CruiseControl.Net (prefered).

I feel we need a programmer to maintain Wix, such as writing Custom Actions.

Thanks
Jirong
Jirong Hu  Thursday, July 23, 2009 8:47 PM
If you've decided to use custom actions in an MSI based install then the tool you use (WiX or Setup&Deployment project) is irrelevant. Migrate from WiX to a Setup Project to build an MSI file to InstallShield or whatever,a custom action is the Windows Installer way you run your code, not something that depends on the tool. A custom action is a design decision, not a tool-dependent capability.You'll be maintaining your custom action code in all these tools anyway. If anything you would be worse off using a Setup Project to build an MSI file because WiX comes with dozens of its own custom actions that you don't have to write or maintain. My experience is that peple are always adding too many custom actions to setup projects anyway, as well as being unaware of the things that the tools will do for you without custom actions. They are the single most common reason why installs have problems.



Phil Wilson
PhilWilson  Friday, July 24, 2009 10:49 PM
If you've decided to use custom actions in an MSI based install then the tool you use (WiX or Setup&Deployment project) is irrelevant. Migrate from WiX to a Setup Project to build an MSI file to InstallShield or whatever,a custom action is the Windows Installer way you run your code, not something that depends on the tool. A custom action is a design decision, not a tool-dependent capability.You'll be maintaining your custom action code in all these tools anyway. If anything you would be worse off using a Setup Project to build an MSI file because WiX comes with dozens of its own custom actions that you don't have to write or maintain. My experience is that peple are always adding too many custom actions to setup projects anyway, as well as being unaware of the things that the tools will do for you without custom actions. They are the single most common reason why installs have problems.



Phil Wilson
PhilWilson  Friday, July 24, 2009 10:49 PM

You can use google to search for other answers

Custom Search

More Threads

• ClickOnce problem
• need delay in vb script
• ClickOnce installing old assemblies from cache
• Weird ClickOnce Issue.
• Defining the path of an install for a setup project
• VisualStudio 2008 Beta2 ClickOnce
• problem with loading external dll
• editing the *.exe.config.deploy file
• Launch Condition in setup project
• 'Not enough storage is available to complete this operation.