Hi All,
I have developed a* un-managed BA* for the BURN. For handling Powe-Off
scenarios, I am checking for "*BOOTSTRAPPER_RESUME_TYPE_INTERRUPTED*" in the
"*pCommand->resumeType*" structure and if found, I am giving complete
control to BURN engine by calling detect, plan and apply with default ac
We are using BURN and have developed our entire installer UI using C++ / MFC.
For non-admin users who are installing our product, we would NOT want them
to navigate through our entire BURN UI Dialog sequence and then finally
click on the "Install" button, to get the UAC prompt; and then realize th
Thank you so much for your reply Bob.
I will look forward to this.
Thanks again.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Running-Burn-driven-installer-in-quiet-mode-command-line-parameters-tp5913001p7586199.html
Sent from the wix-users mail
I spent some more time looking at the problem and it seems to that there is
some other problem.
I am pasting the log of the Burn installation here.
===
[1E3C:0530][2013-05-27T18:55:05]i001: Burn v3.7.1224.0, Windows v6.0
On Fri, May 24, 2013 at 12:04 PM, kanirudha14 [via Windows Installer XML
(WiX) toolset] wrote:
> Hello Rob, (and everyone who is concerned)
>
> I have created a MSI with Wix v3.7 and added a launch condition in it.
>
> I have used a Standard Burn Bootstrapper Application
Hello Rob, (and everyone who is concerned)
I have created a MSI with Wix v3.7 and added a launch condition in it.
I have used a Standard Burn Bootstrapper Application to create a EXE
pacakge.
Now when I Silently run my EXE package from Administrative Command Prompt by
giving command like
"mypack
6 matches
Mail list logo
