Silent Mode not working

[Christopher McAtackney]

Hi,

I've built a bootstrapper for my MSI using version 2.2.727.0 of dotNetInstaller, but I'm unable to get "silent" mode working.

Whenever I use the following command line;

<myBootStrapper>.exe /q

..then the UI for my MSI appears. I had expected /q to work like the silent mode for msiexec - am I mistaken in believing this?

Thanks for any help you can give,

Chris

[Daniel Doubrovkine]

Please collect the log with /log /logfile install.log. See what the command is used to launch your MSI.

--

dB. | Moscow - Geneva - Seattle - New York
dblock.org - @dblockdotorg

[Christopher McAtackney]

Hi Daniel,

Here's the output from the log;

2013-01-09 09:29:15 Silent mode: automatically starting install

<snip>

2013-01-09 09:29:15 Executing: msiexec /i "C:\Users\chris\AppData\Local\Temp\{467198F3-91C3-4E93-8B8D-6A07AF7ADFAB}\MySetup.msi"

So, it does report that it is going to run a silent install, but the msiexec command doesn't run with the appropriate switch (/qn).

Is there any reason why this might be the case?

Thanks,

Chris

[Daniel Doubrovkine]

DNI thinks you're in silent mode, good.

How is this MSI component configured? I bet you it's a cmd component with msiexec written by you in the configuration. DNI's MSI components automatically get the right parameters.

Post your config please if this doesn't help.

[Christopher McAtackney]

Hi again Daniel,

I took a look at my configuration and noticed this attribute;

cmdparameters_silent="" 

Am I correct in saying that I should put "/qn" in as the value of this parameter? I tried this and it seemed to do the trick, the MSI installed silently.

Thanks for all your help, much appreciated.

Chris

[Daniel Doubrovkine]

Yes, although you should not use a cmd component to run MSIs. Add your MSI as an "msi" component and it will take care of itself.

[Christopher McAtackney]

Ok, will take that under consideration - thanks for your help Daniel!