I have successfully set up a custom action .NET class following the tips at http://devcity.net/Articles/339/3/article.aspx
I am able to successfully launch and DEBUG the custom action when building the Installer from the Advanced Installer GUI.
I am unable to pass a user defined custom action parameter to the custom action. The parameter is called "pluginfolder" say that is assigned the value of a user defined search parameter [PLUGIN_PATH] obtained from a Search on the Registry for a particular key.
I have tested the search in the Advanced Installer GUI and it retuned the correct value for [PLUGIN_PATH] prior to running the installer.
As a test I assigned a defined string value of "test" to the custom action parameter "pluginfolder"
in DEBUG, when I use the Context.Parameters("pluginfolder") it correctly returns the value of "test". Hence I am able to correctly pass some parameters correctly and the problem has to be that I cannot pass a value of [PLUGIN_PATH}. Is this a limitation of Advanced Installer? I cant believe so as it would be pretty pointless if you cant pass such parameters obtained form a Search. Im presuming a Search is Carried out before the custom action? Is there a watch widnow to monitor custom parameters as it is building/debugging?
I am using VS2012 Pro, .NET 4.0, VB.NET and Advanced Installer 10. I am trying to install a 32 but assembly on a windows 7 x64,
cheers