So they have to be passed to the installer. But the user has no control over the custom action. This has to be passed to the custom action. But often, these custom tasks may require some values for their operation to be supplied. They can be used to copy files, modify settings, start/stop services or any other type of task that are not covered as a part of the installer. It will enable creation of silent installs by taking the advantage of supplied command line parameters.Ĭustom actions are basically script or executable which is invoked before or after a specific event during installation. This blog will help you understand ‘passing command line parameters to your Custom Actions written in setup projects’. One such scenario is passing command line arguments to custom actions. With Visual Studio a lot of things have changed especially after they have dropped the support for setup projects and instead promoting InstallShield for creating setup projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |