Hi,
Following scenario:
WiX 3.6, build same solution as 2 bundles: one all containing for the web
and another for a CD image.
Now I have the issue that PackageWeb runs even when PackageCD is already
installed. Digging in the mailing list I understood that here some
kind of BundleID
is set at each
Hi,
Can you please how to create the online installation setup?
Is possible to create the online installation by bootstrapper?
If yes, then share any documentation related to web installer creation.
Thanks,
Kannan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687
No, this matches the behavior of uninstalling MSI files from ARP.
On Mon, Apr 15, 2013 at 4:23 PM, Christopher West C <
christopher.c.w...@ericsson.com> wrote:
>
> Using Wix 3.7, I have created a default burn bootstrapper using the
> "WixStandardBootstrapperApplication.RtfLicense". I have been
Take a look at the src\Setup\Bundle\Bundle.wxs which is the web installer
for the WiX toolset itself.
On Tue, Apr 16, 2013 at 2:45 AM, Kannan24 wrote:
> Hi,
>
> Can you please how to create the online installation setup?
>
> Is possible to create the online installation by bootstrapper?
>
> If
MsiPackage element is used by Bundles. That data is provided in the
BootstrapperApplicationData.xml file provided to BootstrapperApplications
running in Burn. Not clear if you are writing a custom BA or if you have a
custom bootstrapper engine. For the latter, you'll have to write all the
infrastru
There are no plans to make the Bundle Id settable. There are so many things
that would start to fall apart if that value was the same for two Bundles.
Huge numbers of conflicts. RelatedBundle is a fantastic way to
address the problem. You could even Bundle/@Tag the different bundles and
use a uni
Based on what I am seeing , the behavior of the burn .exe uninstalling the
chained .msi is not matching the behavior if I install/uninstall the .msi
directly.
If I install the msi directly, and then uninstall the msi from ARP, the UILevel
is "3" during the uninstall of the .msi. I verify this
Ahh, sorry. Misread the question. Did you set DisplayInternalUI='yes' on
the MsiPackage? If no, then the MSIs are always run silently.
On Tue, Apr 16, 2013 at 7:13 AM, Christopher West C <
christopher.c.w...@ericsson.com> wrote:
> Based on what I am seeing , the behavior of the burn .exe uninsta
To interject. If you do have two related bundles. The one you are installing
must be a higher version than the one already installed in order for the
installed one to be uninstalled. Is this correct? If both are installed and
at same version then you'd have two entries in ARP?
Wes
-Ori
Yes, I do have the DisplayInternalUI="yes" set on the MsiPackage element.
Following is the entire MsiPackage element.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, April 16, 2013 9:31 AM
To: General discussion for Windows Installer XML too
Not necessarily. Bundles can be related in a few different ways. What you
are describing is an "upgrade" Related Bundle. In that case, it behaves as
you describe. However, you can use "detect" Related Bundles and the engine
will send you back the information about all the Bundles that share an
iden
PS: Why does it matter? I'm curious.
On Tue, Apr 16, 2013 at 7:52 AM, Rob Mensching wrote:
> Ug. I know Bob changed some things here last because there were some
> issues. I thought it was as my memory remembered but I was apparently
> wrong. Hopefully, he can chime in and correct my understand
Ug. I know Bob changed some things here last because there were some
issues. I thought it was as my memory remembered but I was apparently
wrong. Hopefully, he can chime in and correct my understanding and why it
is the way it is. There was something...
On Tue, Apr 16, 2013 at 7:37 AM, Christophe
I am trying the same thing and I don't understand your response :(
I am doing MyBurnEXE.exe MYVAR=Something
Then in the MSIPackage:
In the burn/bootstrapper log file I see cmdline: 'MYVAR=Something blah
blah...'
so I know it is being picked up,
But later on in burn/boot
On 12-Apr-13 21:38, Hein Htat wrote:
> Hey guys. I'm using the WixUI extension and having trouble flipping the title
> bar of the installer for RTL languages. Changing my display language
> correctly flips my desktop but the title bar of the installer won't budge.
> The buttons say on the right.
On 16-Apr-13 10:53, Rob Mensching wrote:
> PS: Why does it matter? I'm curious.
Seconded. Because...
>> Ug. I know Bob changed some things here last because there were some
>> issues. I thought it was as my memory remembered but I was apparently
>> wrong. Hopefully, he can chime in and correct my
Ok I understand. So if you have a custom BA you can use detect and handle the
removal yourself. Thanks.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April-16-13 11:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Ha
Do you want the MYVAR Burn Variable to be saved after the initial install?
If so add Persist='yes' to the Variable definition of MYVAR. Otherwise, it
will be reset every time the Bundle runs.
On Tue, Apr 16, 2013 at 8:03 AM, StevenOgilvie wrote:
> I am trying the same thing and I don't understa
I figured that question was coming...
We have multiple products that can be installed by the customer. We have a
core product, and then some additional add-on products that can installed as
well, each product having its own .msi. Previously we were installing the .msi
files directly and were
There is no removal for "detect" Related Bundles. Removal only happens with
"upgrade", "addon", "patch" Related Bundles.
On Tue, Apr 16, 2013 at 8:15 AM, Wesley Manning wrote:
> Ok I understand. So if you have a custom BA you can use detect and handle
> the removal yourself. Thanks.
>
> -
Ahh, why not use ::MsiProcessMessage() to display the dialog? If you do
that, then the message would be routed all the way through Burn to the BA
and the BA would then get the message and display it correctly based on its
UI level.
Trying to throw ::MessageBox() inside a custom action is only usef
No it is only for install time... In the MSI I create a registry entry based on
the command line parameter CONFIGURATION=Something
But you didn't answer my question...
I see that burn is reading the command line parameter but I am not able to pass
it to the MSI package as a Property... what am
But you can write code in your custom BA to do that. That's what I meant.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April-16-13 12:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Handling Web + CD bundle with same
Sorry, thought that part was working. Did you add bal:Overridable='yes' to
the MYVAR Variable definition?
On Tue, Apr 16, 2013 at 8:34 AM, Steven Ogilvie wrote:
> No it is only for install time... In the MSI I create a registry entry
> based on the command line parameter CONFIGURATION=Something
Yes, true. The engine will call OnRelatedBundleDetected() so your custom BA
can do whatever with the detected Related Bundles.
On Tue, Apr 16, 2013 at 8:38 AM, Wesley Manning wrote:
> But you can write code in your custom BA to do that. That's what I meant.
>
> -Original Message-
> Fro
. And determining the "size" of an MSI can be a royal pain. If you mean
"when it's about to be installed" then it will be accurate only after the
costing is complete because features have been picked and Windows has worked
out which files are actually going to be installed. If you just want a
g
Bundles essentially do all that for you, adding the data to the
BootstrapperApplicationData.xml file.
On Tue, Apr 16, 2013 at 8:46 AM, Phil Wilson wrote:
> . And determining the "size" of an MSI can be a royal pain. If you mean
> "when it's about to be installed" then it will be accurate on
AWESOME :)
Here is what I did:
Ran the burn/boostrapper as MyBurn.EXE CONFIGURATION=Something
And it worked :)
Thanks!
Steve
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April-16-13 11:41 AM
To: General discussion for Windows
I have a Burn bootstrapper that need to reboot the system to complete
installation, when the system reboot the Burn setup restart but it doesn't
restart from the point where it finish before reboot.It restart from begin with
the detect process, is it a bug or is there some configuration to set?
I have this ExePackage definition in my Burn project
I want to know if I have to set the ExitCode for each value or if there are
default values that I haven't need to add.If I don't add the ExitCode which
will be the behavior of the Burn setup?
After restart, the process starts over. However, Detect should see that a
bunch of things are already on the machine and thus Planning will only do
what is next.
This is important because machine state could change significantly between
the time the restart was requested and the restart actually o
But in this case how can I detect that the installation is complete?For the
uninstall I have seen the wix setup, on the DetectComplete it Plan again the
operation of uninstall (invoking automatic plan for uninstall).For the
installation as I have to collect user information about wich feature in
Hi All,
My company is evaluating two different Windows installer solutions, WiX and
Nullsoft installer (NSIS). I was wondering if anyone has had experience with
both, and could weigh in on the pros and cons, benefits, limitations, etc.
Thanks,
Nick
-
A few months ago, we were in a similar position. Although we didn't delve very
deep into NSIS, I have no regrets whatsoever about choosing WiX. As with any
new technology, there is a learning curve, but there are tutorials and online
posts/resources that do a very good job at teaching the basics
Last time I looked NSIS hasn't been updated since 2009. I also contemplated
using NSIS.
What attracted me to Wix is that it is based on MSI which (at the time) you
needed to get app Windows certified. And that it is XML based which I knew.
And the bootstrapper, burn, because I needed to inst
I'm obviously biased but non-declarative installation technologies like
NSIS are a complete non-starter for me. I don't want to write scripts that
install files then have to remember write more scripts to uninstall those
files.
I had a couple consulting gigs to convert setups from NSIS. It amazed m
The Command structure passed to your BA will tell you if the Bundle is
starting after restart. You can also persist values in Variables before the
original Apply() and they will be there after restart.
On Tue, Apr 16, 2013 at 3:08 PM, Marco Tognacci wrote:
> But in this case how can I detect th
On 16/04/2013 23:44, Nick Miller wrote:
> My company is evaluating two different Windows installer solutions, WiX and
> Nullsoft installer (NSIS). I was wondering if anyone has had experience with
> both, and could weigh in on the pros and cons, benefits, limitations, etc.
You might think XML i
Thanks for your quick reply.
I checked with Bundle.wxs file, but i can't find the web installer related.
The below code are under the bundle tag to pack the msi.
I tried the to remove the source file attribute and used the DownloadUrl,
but compilation failed with data\Wix36.msi not foun
39 matches
Mail list logo
