What is the benefit of a custom action defined as i) an installed .NET installer class vs ii) a custom action attached to an installation.
What advantages does inheriting the installer class in 1) have over ii) ? I am having issues with i) as I do not want to install the custom action which would require cleaning up afterward and may contain some licensing/security scripts that I don't want to risk people decoding. Hence I'd prefer option ii) but I understand from the help guide that you can use VB.NET
In what situation would you use the different types?
I understand that in the help section that VB.NET cannot be used for type ii) see below for example in C# using WIX incorporation.
http://www.advancedinstaller.com/user-g ... rp-ca.html
HOWEVER, is this true? As I understand WIXnow offers support for VB.NET. Can a type ii) custom action now be defined for VB.NET? See below:
http://www.infoq.com/news/2009/02/WiX30
By supporting managed Custom Actions (CA’s) using Deployment Tools Foundation (DTF) in WiX, developers no longer need to use C++ or scripting (VB Script or JavaScript) to author CA’s. DTF has a managed .NET wrapper on top of the msi.dll giving users access to the complete MSI API. A CA method in C# looks like this:
cheers
FOLLOW US
Get the latest news in Application Packaging