This behaviour is not stable. When I removed everything and repeated
test again - file patched. This makes me frightened that on some
clients' machines patch will work ok, but on some will fail. It is the
worst variant, when I can not reproduce bug on my PC.
30.01.2012 21:46, Wilson, Phil пишет
Put the following line in your Package:
It will tell MSI not to include it in Add/Remove Programs.
Dieter Lunn
http://ubiety.ca
On Tue, Jan 31, 2012 at 7:02 PM, Alexander Lamaison wrote:
> My burn bootstrapper/bundle/thingiemagig is just a wrapper around my
> MSI installer; it chooses betwe
My burn bootstrapper/bundle/thingiemagig is just a wrapper around my
MSI installer; it chooses between an x86 and an x64 version but will
only ever install one. So I just want one entry for my program in
Add/Remove programs.
I seem to have achieved this by removing the Name attribute from the
Bun
It seems I can't reproduce it anymore.
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Moving-payload-to-Cache-Directory-tp7237441p7241383.html
Sent from the wix-users mailing list archive at Nabble.com.
On 31/01/2012 20:02, Bruce Cran wrote:
> On 31/01/2012 19:14, Dieter Lunn wrote:
>> Even with a managed bootstrapper you don't need .NET installed
>> initially if I remember correctly.
> That's right - Burn will bootstrap .NET first. But I just don't like the
> idea of requiring extra software to b
On 31/01/2012 19:14, Dieter Lunn wrote:
> Even with a managed bootstrapper you don't need .NET installed
> initially if I remember correctly.
That's right - Burn will bootstrap .NET first. But I just don't like the
idea of requiring extra software to be installed just for the installer.
--
Bruc
Even with a managed bootstrapper you don't need .NET installed
initially if I remember correctly.
Dieter Lunn
http://ubiety.ca
On Tue, Jan 31, 2012 at 1:00 PM, Bruce Cran wrote:
> On 31/01/2012 15:37, Alexander Lamaison wrote:
>> Is this hard to do? Can it be done in C++ or must I use .net?
On 31/01/2012 15:37, Alexander Lamaison wrote:
> Is this hard to do? Can it be done in C++ or must I use .net? Can
> you point me to something to get me started (I've searched online and
> in the source but can't find anything)?
Fortunately you can use C++. I certainly don't like the idea of
re
You can do it in native or managed code.
Take a look at the burn solution file in the source (src\burn\burn.sln). You
can see both the wixstdba (native) and WixBA (managed) projects for
examples. I haven't come across any tutorials or anything like that though.
--
View this message in context:
On 31-Jan-12 09:12, Alexander Lamaison wrote:
> Is it possible to have a bootstrapper made with burn that doesn't show any UI?
The WixStdBA supports the /silent switch for no-UI installations.
--
sig://boB
http://joyofsetup.com/
--
On 31 January 2012 15:07, jhennessey wrote:
> Looks like you need to write your own BA:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bootstrap-a-single-MSI-not-showing-BA-UI-at-all-td6926187.html
Is this hard to do? Can it be done in C++ or must I use .net? Can
you point
Several action don't seem to be intended to be found in MSMs. Maybe
AppSearch is one of them.
Do you distribute your MSM publically? If not, I've got a couple of ideas.
1) Run a couple of SQL queries against the MSM to remove them from the two
Module*Sequence tables. 2) Change from using MSMs and
Looks like you need to write your own BA:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bootstrap-a-single-MSI-not-showing-BA-UI-at-all-td6926187.html
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bootstrap-a-single-MSI-not-showing-BA-UI-at-all-td6926187.h
I've validated my MSM in Orca. At first, I got a lot of ICE33 warnings
because of some COM registration logic. To rule out that this was
causing my problems, I removed this registration logic and validated the
MSM again. Now the validation completes, but ends with:
Execution ERROR There is
Is it possible to have a bootstrapper made with burn that doesn't show any UI?
All I want my bootstrapper to do is decide what platform it's running
on (x86 or x64), extract the appropriate MSI installer from within
itself and run it. At the moment, the Burn UI takes over. Is there a
no-UI optio
15 matches
Mail list logo
