Setup project accepting Command-Line params?

[briano]

I can get my setup application to display a dialog and pass entered
values to the Installer class of my app. How do I get this from the
Command-Line?

Currently, setting ENVNAME1=QA, just as I have a custom action with
/EnvironmentName =[ENVNAME1].

Am I misinterpreting the functionality here?

[sze tan]

it should look something like:

my.msi ENVNAME1=QA

or

msiexec /i my.msi ENVNAME1=QA

[briano]

Thanks! That is very helpful. I found that by removing the Dialog in
the Setup project;s user interface, the command line options passed are
read from Context.
Thanks again for your reply.
Brian

[briano]

One more thing. Just in case my developers refuse my adding an
installer class to our application, I want to be able to do install
work in a custom action calling a VBS script file. I am having some
success reading the value of Session.Propert y("CustomAction Data") but
no other property. I tried the syntax discussed above, and found the
MSI does indeed create all the properties I send, but I get only empty
string using the syntax Session.Propert y() in my VBS Script. If I
simply insert one value [ENVNAME1] into the custom action data, I can
read it using Session.Propert y("CustomAction Data"). But I may need to
pass multiple values.

Any ideas here?

TIA -
Brian

[Todd Derksen [MSFT]]

Brian I would suggest passing those values into the script from the
arguments property of the custom action.

Todd Derksen
--------------------
Visual Basic Deployment Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

From: br****@avanade. com
Newsgroups: microsoft.publi c.dotnet.langua ges.csharp
Subject: Re: Setup project accepting Command-Line params?

One more thing. Just in case my developers refuse my adding an
installer class to our application, I want to be able to do install
work in a custom action calling a VBS script file. I am having some
success reading the value of Session.Propert y("CustomAction Data") but
no other property. I tried the syntax discussed above, and found the
MSI does indeed create all the properties I send, but I get only empty
string using the syntax Session.Propert y() in my VBS Script. If I
simply insert one value [ENVNAME1] into the custom action data, I can
read it using Session.Propert y("CustomAction Data"). But I may need to
pass multiple values.

Any ideas here?

TIA -
Brian