In a command line you'd say:
msiexec /i <path to msi> MYLOC=C:\Whatever\this.config
and pass [MYLOC] to the program being run as a custom action.
but that's rather odd - most people expect to double-click an MSI file and
it just works. Where does the config file come from and why can't you locate
it automatically?
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280 [quoted text, click to view] "ABCL" <ohmp05@hotmail.com> wrote in message
news:1134732039.009359.34920@f14g2000cwb.googlegroups.com...
> Hi all,
> I am new to deployment of application. If any one please help me on it
> , that will be great.
> During the installation of project, Installer will execute an utility(
> It will display Winform with all empty Textboxes . If user want to
> make changes in config file, user has to click on button to browse
> config file so it displays configuration file values on Form., and
> USer can make changes on it and save it to config file).
> Is there any way that when this utility will execute, The winform will
> be prepopulated with config file values( so user does not need to click
> a button to load config file ).I know that can be done by passing
> config file location( FilePath) vis command line
> How and where can I pass command line parameter ( config filePath) in
> Installer and how can I read it and where can I read So this from will
> be prepopulated with configuration file value.?
>
> Please help me to find the solution. Any sample code will be great
> help.
> Thanks in advance
> ABCL
>