Hi,
you have mentioned in the response
The Command structure always shows you what was provided via the
command-line. It will not change until you pass a new command-line to the
engine.
Am using the Windows form application, so how to change the command-line for
action as Uninstall?
Please
Pass -uninstall on the command-line.
On Sun, Jul 8, 2012 at 11:19 PM, Kannan24 skan...@syncfusion.com wrote:
Hi,
you have mentioned in the response
The Command structure always shows you what was provided via the
command-line. It will not change until you pass a new command-line to the
100% agreed.
On Sun, Jul 8, 2012 at 5:23 AM, Christopher Painter chr...@iswix.comwrote:
Sean-
I have prerequisites for InstallShield (PRQ files) but I can't say that I
use them anymore. MSI 3.1 is included in Server 2003 SP1 and Windows XP
SP3. All of my employers and customers have
Nothing Burn does requires a restart. A package in the chain may require a
restart and Burn will respect that.
On Sun, Jul 8, 2012 at 9:34 PM, Nick Ramirez nickra...@hotmail.com wrote:
Okay, an update: Actually, if I click my Uninstall button after the reboot,
it does eventually uninstall the
On 09/07/2012 05:34, Nick Ramirez wrote:
Okay, an update: Actually, if I click my Uninstall button after the reboot,
it does eventually uninstall the bundle. Is it /supposed/ to require a
restart to uninstall a Burn bundle? And does that restart only become
mandatory when you want to
Hi,
Thanks for your quick replay.
From your update, i have passed the uninstall action as command line. Now i
get the plan action is Uninstall, but unable to uninstall the setup. I used
the following code.
SyncBA.Model.Engine.Detect();
SyncBA.hwnd = IntPtr.Zero;
Hi,
Could you please update for the InternalUI, to change the values from
BA.dll?
Thanks,
Kannan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-MsiPackage-and-DisplayInternalUI-tp7484106p7579353.html
Sent from the wix-users mailing list
To request a new feature, please use this link
http://sourceforge.net/tracker/?group_id=105970atid=642717
-Original Message-
From: Kannan24 [mailto:skan...@syncfusion.com]
Sent: 09 July 2012 13:20
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn, MsiPackage and
This has all helped. Apparently, I've been testing too many things at once
and must have been experimenting with the ForceReboot element in my MSI.
Removing that should make things run much smoother!
--
View this message in context:
Hey, I was wondering if it's possible when creating an installer to install a
.NET assembly that installs a given assembly to a particular GAC.
I've got an assembly that I'd like installed to the .NET 2.0 GAC, but
apparently it just wants to install it to the 4.0 GAC.
Any ideas?
Hi,
it seems like wixstdba now supports overriding variables from the command line
(looking at the variable element in the help, as well as defects 3480653 and
3489809 apparently fixed).
However, I have no success.
I am using WiX v3.6.3109.0 Release (from wix36-binaries.zip)
I define a
You can't build WixStdBA without balinfo.h.
Should it be included in the binary distribution under sdk/inc?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat
I just figured out how this works looking through the WixStdBA source code.
This was implemented in time for the RC release on May 21.
(https://sourceforge.net/tracker/index.php?func=detailaid=3489809group_id=105970atid=642714)
To pass command line arguments, it goes something like this:
Wix
Result.NoAction is like saying Nothing to do here. smile/
On Mon, Jul 9, 2012 at 9:52 AM, Nick Ramirez nickra...@hotmail.com wrote:
Thanks, I've added an event handler for the ResolveSource event and that
gets
me past this issue. My bundle installs! I am following the WiX setup
example
by
On 09-Jul-12 17:26, Darwin Baines wrote:
You can't build WixStdBA without balinfo.h.
Should it be included in the binary distribution under sdk/inc?
Yes. Please file a bug so it doesn't get lost in e-mail.
--
sig://boB
http://joyofsetup.com/
On 09-Jul-12 15:13, chro...@comcast.net wrote:
Variable Name=MYVAR Value=myvalue Type=string Overridable =yes/
error CNDL0004 : The Variable element contains an unexpected attribute
'Overridable'.
The attribute lives in the WixBalExtension namespace, so you need to
prefix it.
--
sig://boB
Thanks Bob,
I just saw an answer from Darwin Baines, in answer to an older, similar
message.
Using
Variable Name=CommandLineArg bal:Overridable=yes/
does the trick.
Christophe
--
Live Security Virtual Conference
17 matches
Mail list logo
