Kevin Richardson wrote:
> It looks like the current bootstrapper calls msiexec.exe, rather than
> using the APIs. I inherited the code and it looks like it was done
> that way to make it convenient to pass command line arguments, among
> other things.
>
> If I continue to call the executable,
> It looks like the current bootstrapper calls msiexec.exe, rather than
> using the APIs. I inherited the code and it looks like it was done
> that way to make it convenient to pass command line arguments, among
> other things.
>
> If I continue to call the executable, I assume that I'll need to
>
Thanks, Bob.
It looks like the current bootstrapper calls msiexec.exe, rather than
using the APIs. I inherited the code and it looks like it was done
that way to make it convenient to pass command line arguments, among
other things.
If I continue to call the executable, I assume that I'll n
Kevin Richardson wrote:
> Is it "OK" to bundle both MSIs into a single, 32-bit, bootstrapper
> executable?
>
> Of course, I'd need to add logic to the executable to install the
> correct architecture's package, but my question is about whether the
> correct processes will be called. Will Wind
4 matches
Mail list logo
