This collection also houses the well known parameters such as TARGETDIR, and others. The trick to the solution is that the command line parameters are added to a special collection inside the guts of the setup framework. I'm going to lightly cover adding the custom action, but I'm going to focus on passing the command line parameters to the custom action, and managing the data through to the uninstallation of the application. There are loads of articles out on the internet that show you how to create custom actions that your setup package can run to show custom dialogs, and perform other types of actions during an installation. There were several stumpers that I encountered while working on this solution, which instantly got my documentation juices flowing, so now it's article time! The Solution
An install that is called from a batch file or a package that needs to supply data that the user would normally enter.Īfter spending some time Googling in the internet, I was finally able to guess my way into a method of passing this data that would work in my target setup situations:.An unattended install that would record a product key into the registry.An unattended install that is being deployed into multiple environments that would need to access web services at environment specific URLs.This article will illustrate how to pass command line parameters to Install Custom Actions so that you can enable silent setups that can take advantage of command line supplied parameters without having to recompile the setups.
0 kommentar(er)
