silent install
Hi all,
I'm new to deployment. I'm have a VS C++ app. I'm doing the deployment through VS as well.
I'm able to manage to do the silent install with the .msi, but that's only part of what I want. I need to provide a unique install file to the user, that accepts an input argument.
Basically, I need something like this: "setup.exe arg"
where setup.exe will perform the install and call the newly installed program with the given argument. The install should be hidden from the user, whereas the user will only see the installed program window.
Can anyone help me accomplishing that?
Thanks,
--
Joao
I'm new to deployment. I'm have a VS C++ app. I'm doing the deployment through VS as well.
I'm able to manage to do the silent install with the .msi, but that's only part of what I want. I need to provide a unique install file to the user, that accepts an input argument.
Basically, I need something like this: "setup.exe arg"
where setup.exe will perform the install and call the newly installed program with the given argument. The install should be hidden from the user, whereas the user will only see the installed program window.
Can anyone help me accomplishing that?
Thanks,
--
Joao
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Forget building a set-up stub and stick with a plain MSI. Stubs just get in the way and most PCs will be set up to "run" an MSI by double-clicking anyway.
To pass data to an MSI, you'd typically use a public property and set its value via the command line. Let's say you call the property USERARGUMENT (public properties have to be in all upper-case): your command line would look like this:
......MSIExec /i [path_to_and-name_of_MSI] USERARGUMENT="whatever" [other command line switches]
Your MSI would need to contain the property, set up with some default value (typically '0') and you would probably need to add conditions to either features or components which branch according to that property's value, e.g., If USERARGUMENT <> 0
Given that requirement, I'd suggest abandoning VS as your authoring tool, as its capabilities are severely limited. If you're developing software and have sprung for VS, the stretch to a proper tool for packaging ought to be a no-brainer. Of course, you *can* use Orca or InstEdit to edit the MSI directly but you would need to be much more familiar with Windows Installer than you seem to currently be.
To pass data to an MSI, you'd typically use a public property and set its value via the command line. Let's say you call the property USERARGUMENT (public properties have to be in all upper-case): your command line would look like this:
......MSIExec /i [path_to_and-name_of_MSI] USERARGUMENT="whatever" [other command line switches]
Your MSI would need to contain the property, set up with some default value (typically '0') and you would probably need to add conditions to either features or components which branch according to that property's value, e.g., If USERARGUMENT <> 0
Given that requirement, I'd suggest abandoning VS as your authoring tool, as its capabilities are severely limited. If you're developing software and have sprung for VS, the stretch to a proper tool for packaging ought to be a no-brainer. Of course, you *can* use Orca or InstEdit to edit the MSI directly but you would need to be much more familiar with Windows Installer than you seem to currently be.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
