Thanks David, I will try this and let you know
On 21-03-2014 19:48, David Watson wrote:
> You need to persist the VIRTUAL_DIR_VAL (store it in the registry) so the
> uninstaller knows it has changed otherwise it will use the default values.
>
> http://robmensching.com/blog/posts/2010/5/2/the-wix
Classification: Public
Look at modifying a theme
i.e. customize the burn theme
xml:
#(loc.HelpHeader)
#(loc.HelpText)
#(loc.HelpCloseButton)
.wxl
Setup Help
/install | /repair | /uninstall | /layout [directory] -
installs, repairs, uninstalls or creates a complete local copy o
What version of Wix are you using? Are you customizing the theme and/or
languages at all?
The WXL should have a HelpText string defined by default.
-Original Message-
From: Shane Corbin [mailto:shane_cor...@selinc.com]
Sent: Monday, March 24, 2014 3:56 PM
To: wix-users@lists.sourcefor
You don't need an addon bundle if you just want to embed a bundle within a
bundle. An addon is useful if you want users to install bundles outside of the
main install say to add new features to your software or maybe a language pack.
Then burn is smart enough to remove all addon bundles when t
It hides the addon (or any type) bundle as well. The progress is then shown on
main bundle like Jacob said.
Wes
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: March-24-14 5:13 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Wh
I'm using the wixstdba to create my bundle. When I run .exe /?
I get an empty dialog box. How do I add help text?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wixstdba-help-dialog-tp7593720.html
Sent from the wix-users mailing list archive at
Exe protocol will allow the primary bundle to display messages from the add-on
bundle.
-Original Message-
From: Scott Moyer [mailto:scott.mo...@appliedvision.com]
Sent: Monday, March 24, 2014 2:31 PM
To: 'General discussion about the WiX toolset.'
Subject: Re: [WiX-users] What is the bes
You can't... Your BA isn't elevated by design. If these need to run elevated,
put them in the chain as exe packages.
-Original Message-
From: gowri.malas...@non.agilent.com [mailto:gowri.malas...@non.agilent.com]
Sent: Monday, March 24, 2014 2:28 PM
To: wix-users@lists.sourceforge.net
S
For scenarios that involve running the installer past the detect stage, I
moved code to a test box, and I tried to use WinDbg. I installed windbg as
the default debugger and got it to attach when the code hits a
System.Diagnostics.Debugger.Break(); line in the mba's Run() function, but I
did not f
System.Diagnostics.Debugger.Launch() at the beginning of your CA will do the
job nicely :)
-Original Message-
From: gowri.malas...@non.agilent.com [mailto:gowri.malas...@non.agilent.com]
Sent: March-24-14 3:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Debugging Managed
I added ExeProtocol="burn" to the ExePackage element in the first bundle, and
I added to the
Fragment in the second/driver bundle.
Not sure if that is correct as it does not appear to make any difference, good
or bad, to the installation.
-Original Message-
From: Hoover, Jacob [mailto:
Hi, I have a managed BA that tries to launch few external executables on
package complete event. My problem is that it works only with UAC turned off!!
How can I make it work with UAC on? What is causing it to fail with UAC?
Basically those executables writes some information to registry, copies
Hello, how to debug MBA written in C#?
I tried this
(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-debug-Managed-BA-Burn-td6630791.html)
of course without steps 1 & 2 as I didn't want to debug engine. But no luck. I
just launches the program but it never steps into my cod
It doesn't work that way, so you may need to provide more info. It's
never required, so you probably have some assumptions about the way
things work that I'm not aware of.
If you rebuild the MSI and up with the same ProductCode you cannot
install it twice - it will go into maintenance/modify/repai
http://wix.tramontana.co.hu/
> From: Joel Palmer [mailto:jpalmer1...@comcast.net]
> Sent: Monday, March 24, 2014 6:17 PM
>
> Can you give me the code to check for a previously installed
> version of my app? Then, prevent install if it is there?
>
> Currently, I am allowed to install the same a
Classification: Public
Joel,
If you search the user list for major upgrade you will get your code from that
(for old install)
If you install your application MSI then install it again it tries to do a
"fresh" install? That doesn't sound right...
Steve
-Original Message-
From: Joel Pa
Can you give me the code to check for a previously installed version of my
app? Then, prevent install if it is there?
Currently, I am allowed to install the same app twice and I want to prevent
that.
Also, do you have example code on how to check for an "old" version
installed? Then, unin
My installer looks like it's doing everything except running the postdeployment
script for the database setup project. Has anyone used that before? Does
anyone know how to trigger its execution?
Thanks
Woody
--
Learn
Have two bundles; The first containing your prerequisites and core application
install and a second bundle containing the drivers. Yes, it would be an Exe
package with ExeProtocol=burn. In the "driver" bundle, I believe you'd want to
look at the RelatedBundle element.
http://blogs.msdn.com/b/h
Thanks for the response.
Just to clarify...
You can have more than one in a Bootstrapper.wxs?
Or by "second bundle" do you mean second Bootstrapper.exe? As in targeting a
second Bootstrapper (Bootstrapper2.exe) as the SourceFile in an ExePackage in
the first Bootstrapper (Bootstrapper1.exe)?
I have a machine running Windows 8.1 where the Burn uninstaller is
failing since it appears that the call to CoInitialize() is failing:
Burn v3.9.203.0, Windows v6.3 (Build 9600: Service Pack 0), path:
C:\ProgramData\Package Cache\{GUID}\product.exe, cmdline:
'/uninstall /quiet /norestart -burn.un
There isn't any communication between the MSI and the BA for returning property
values. Since you've written your own BA, you have a bit more latitude but you
can't modify the plan in between packages in Apply. To me it almost seems like
it would make sense (and be easier and not require a cust
Thanks for the reply.
I already have four MSIs for the two drivers (two x64 and two x86), and I am
familiar with passing variables from a BA to an MSI. I just need to figure out
how to pass information back from the MSI so the BA can access it. I do not
understand how to persist a variable and
This process can also be implemented using MSBuild by overriding the
predefined Targets SignBundleEngine and SignBundle. There is more
information in the wix source at src\tools\WixTasks\wix200x.targets
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.
These the docs you are referring to, correct?
http://wixtoolset.org/documentation/manual/v3/overview/insignia.html
At first I thought they weren't relevant in this case because there is no
external cab file.
However, I followed the instructions halfway down the page and the result
worked (thanks
I am in a similar boat, converting an old IS script project to Wix/msi. So I
am also learning, and very impressed with WIX. Most of my time so far has
been trying to sort out oddball configuration issues for drivers. In my
case in some scenarios I need to get printer drivers installed as
print-t
First of all, I think WiX is pretty awesome, but I am having some trouble
understanding how to implement some of the advanced customization/extension
capabilities, and what is the best way to design and implement ...
My new assignment wants me to modernize and cleanup a 15-year old IS6 install
Hi,
In my installer am creating DB and running create/alter table scripts.
if any script fails, how can i handle the error from wix?
pls find the below code
*Component Id="cmp39152CBE55BD4B39B74F75CAC45B7B87"
Directory="INSTALLLOCATION" Guid="07B7EF72-F434-46DB-A94A-59C35534651E"
KeyPath ="yes"
28 matches
Mail list logo
