![]() In the DLL (you can also java script or visual basic script) you get the installer properties using: Then you pass the properties (case matters) on the command line like DEBUG="true" or PORT=1024 and also put them into the Advanced Installer's > Custom Action > action data field in brackets like debug= port=. I created a simple DLL using MS Visual Studio that exposed a simple validation routine and an editing routine for the install and commit phases respectively. ![]() In my case, the magic happens in the Advanced Installer > Custom Actions > Install and Commit phases. While you cannot get the full command line as a single property, you can pass individual properties. The post install included editing an application config file to include some of the command line parms. My pre-processing included verification of the command line parms such that if it failed, then the actual install would stop before a single file was extracted. ![]() ![]() My installation has many command line parameters and I needed to do a lot of processing on those parameters both before and after installation of the files. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |