Hmm, sounds like Burn did not fully rollback the Bundle when your MSI
failed. In that case, you might want to uninstall the previous Bundle before
trying the new one. Also, the Burn log file should show you (during Detect)
whether a package was already cached or not.
The Package @Compress and @Cac
YRC.
On Tue, Jul 12, 2011 at 12:14 PM, jhennessey wrote:
> >From reading other posts on the list, this is currently not possible. That
> means you need to use the standard boostrapper application or write your
> own.
>
> However, IIRC, Rob mentioned that this might be something that gets added
>
ExePackage progress without a Protocol is very gross right now. You
basically get a tick at the beginning (aka: I'm going to do something) and a
tick at the end (I did something). Fine tuning progress will be a thing we
do after we get some of the bugs fixed since progress has to layer through
ever
The Fragment seems like it should have worked. Fastest thing might be to
open the Merge Module using Orca and see if your Component definition is in
there. If not, then I'm a little surprised since that ComponentGroupRef
should do it. if it is in the Merge Module then you'll want to check your
Mer
If you give the Bundle a "Name" it registers itself in ARP. To do that, it
caches the executable so it is available for repair and uninstall.
There are still some trickier bugs where if things go wrong the ARP
registration remains even though it should have been removed. As a result,
it is very ea
The WixStdba currently prompts before downloading from internet. That was
very useful for testing some cases but the default is planned to change to
just do it...
On Tue, Jul 12, 2011 at 9:28 AM, Roy Chastain wrote:
> I have a simple Burn bundle with a prerequisite exe package and a single
> ms
Nope, first email.
Can you share the log? Only thing I saw that might be minutely related is:
http://www.appdeploy.com/msierrors/detail.asp?id=134
It's possible something really strange is going on in your Directory tree
(like maybe it isn't rooted in TARGETDIR/SourceDir?).
On Tue, Jul 12, 2011
You need something like:
That's the code from wix\src\Setup\Bundle\Netfx.wxs how the WiX toolset uses
it.
On Tue, Jul 12, 2011 at 5:52 AM, Kryschan <
christian.hennig@wincor-nixdorf.com> wrote:
> Sorry but I still don't know what to do now to make my bootstrapper build
>
Not yet, but there should be. Documentation on the theming in Burn I think
says, "Write more here" right now... so yeah, more documentation and
configurability is necessary.
On Tue, Jul 12, 2011 at 6:48 AM, Roy Chastain wrote:
> Is there a way to remove the "Options" button in the resulting
> bo
>From reading other posts on the list, this is currently not possible. That
means you need to use the standard boostrapper application or write your
own.
However, IIRC, Rob mentioned that this might be something that gets added
later though.
--
View this message in context:
http://windows-insta
I have a Burn package with a MSI that is marked as Compressed="yes".
The Cache attribute was left off the MsiPackage element.
I run that copy of Burn and my MSI failed to install (due to errors in
the MSI). The bootstrapper application shows as installed.
I rebuild the Burn package with a new MS
I'm not sure if this is a bug or not:
Out of all my packages, the biggest one by far is SQL Server. However, the
progress bar seems(?) to jump a large amount compared to the others when it
STARTS processing SQL Server rather than AFTER it completes and moves on to the
next. Has anyone else no
I was testing a bootstrapper package this afternoon and when I happened
to look at the Add/Remove programs, I found about 8 copies of the
bootstrapper installed. What was more surprising was that I could run
uninstall on each one.
This seems like very strange behavior. This implies that the
boot
Hello,
My goal is to create a merge module where my module/package elements are
defined in one .wxs file, and the module's directories/components in
another. I currently have:
***MyModule.wxs***
ht
We have an old project whose installer was built using VS. I need to
replace one of the files, so I want to create an installer with WIX
which just installs a single file. The "hotfix" installer I've created
works fine when installed, but when it gets uninstalled, it removes the
file. I'd like it t
I have a requirement that I'm trying to research the best solution for.
Basically my development team has an application that has a dependency on a
third party dll that has some known issues. I'm stuck between a rock and a
hard place in that they will not eliminate the dependency and no one
I have a simple Burn bundle with a prerequisite exe package and a single
msi. The exe package is for dotNetFx35Setup.exe with a download link to
http://go.microsoft.com/fwlink/?linkid=118076 and compressed=no. The
framework is already installed and the Burn log indicates that it was
detected. Ho
I have a simple Burn bundle with a prerequisite exe package and the
target msi package. When it runs, the MSI package appears to be running
in silent mode. (The install log has the following content -
"Client-side and UI is none or basic: Running entire install on the
server.") How do I make the M
Hi all,
Is it possible to launch an exe at the end of the second or 3rd msi installer
has run via a bootstrap process?
Thanks,
DOMINIQUE LOUIS | SENIOR IS DEVELOPER
AMX EUROPE | 6TH FLOOR SALISBURY HOUSE | LONDON | EC2M 5QQ
MOBILE: +44 (0) 7799.82.46.85 | PHONE: +44 (0) 207.652.9472
dominiqu
Our product does utilize a bootstrapper so this is a distinct possibility.
Just wondering if there is a more illustrative tutorial or example somewhere
that does what you describe?
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: Tuesday, July 12, 2011 12:35 AM
T
I apologize if this email appears to be a duplicate. Although I'm registered my
previous email was deleted.
It seems I can't get rid of this 2343 Error no matter how I set the
WIXUI_INSTALLDIR property. As an experiment I created an installer that only
contains a Product.wxs which only loads th
Is there a way to remove the "Options" button in the resulting
bootstrapper without using
WixStandandardBootstrapperApplication.Foundation and completely theming
the install? If so, how? If not, is there ANY documentation (beyond
the schema reference) on the theming process etc? If not, is my be
Sorry but I still don't know what to do now to make my bootstrapper build
again. Can you please give me a hint on that or do I have to wait for the
documentation update?
Best regards
Kryschan
Rob Mensching-7 wrote:
>
> Ug, sorry, I forgot to update the documentation about the breaking change.
>
Ug, sorry, I forgot to update the documentation about the breaking change.
Yes, that is expected. Those WixVariables replace the "MbaPreqNetfx"
Bundle/Variables used to indentify the prerequisite package and license.
I'll get the documentation fixed before the next build.
On Tue, Jul 12, 2011 at
Yes, using the same input file from the VS guys is definitely something we
want to try and accomplish.
On Tue, Jul 12, 2011 at 5:02 AM, Roy Chastain wrote:
> Well, the peanut gallery is back.
>
> > Wow, no faith from the peanut gallery.
>
> > If the file is signed (something else we calculate du
Well, the peanut gallery is back.
> Wow, no faith from the peanut gallery.
> If the file is signed (something else we calculate during build when
> referencing the file) we will use the signature of the file not the
hash. If
> the signature on the file changed in between the point that you built
Hi,
after upgrading to WiX version 3.6.1908.0 I get two errors when building a
bootstrapper project using the ManagedBootstrapperApplicationHost:
- The Windows Installer XML variable !(wix.WixMbaPrereqPackageId) is
unknown. ...
- The Windows Installer XML variable !(wix.WixMbaPrereqLicenseUrl) i
27 matches
Mail list logo
