What do I need to include in my installation in order to build
bundles/bootstrapper applications on my client's machine (excluding the
obvious)?
--
Slashdot TV.
Video for Nerds. Stuff that matters.
In WiX 3.5 I was able to open a handle to the MSI, edit some internal user
properties that I created during development of the MSI, and save the MSI
with these updates. With WiX 3.6 the bundle that is created is a shell for
the internal MSI and other associated files for bootstrapping. Is there
Too bad I still can't figure out why my previous bundle won't complete the
uninstallation.
Thanks for the information I may just go with a native approach as well.
On Sep 22, 2012 11:06 AM, Neil Sleightholm n...@x2systems.com wrote:
Thanks to Rob's input I have finally got same version upgrades
Any answer to this?
Greg Beaty
greg.bea...@gmail.com
On Tue, Sep 18, 2012 at 1:00 PM, Neil Sleightholm n...@x2systems.comwrote:
This is what I tried, in OnDetectRelatedBundle() save the operation. In
OnPlanRelatedBundle() if the saved operation ==
BOOTSTRAPPER_RELATED_OPERATION_NONE (which
, Rob Mensching r...@robmensching.comwrote:
I'm a bit confused. Why do you call Detect and Apply twice? I assume you
called Plan in there some place as well, right?
On Mon, Sep 17, 2012 at 8:36 PM, Gregory Beaty greg.bea...@gmail.com
wrote:
So after doing a ton of analysis I figured out my
the version; the cause was multiple entries in ARP. It
might we worth checking this, I found if I removed all the versions then
the upgrades started working.
Neil
-Original Message-
From: Gregory Beaty [mailto:greg.bea...@gmail.com]
Sent: 16 September 2012 17:36
To: General
the Bundle but keep the version the
same, you have multiple bundles registered on your machine. Go to
ProgramsFeatures (aka: ARP) and remove them all. Package reference
counting with all those Bundles still installed will likely be very
confusing. smile/
On Mon, Sep 17, 2012 at 4:38 AM, Gregory Beaty
is
failing. You should see the new Bundle kick off an uninstall of the old
Bundle at the end of the new Bundle's install.
If you take a walk through the log files you should be able to see all the
calls.
On Mon, Sep 17, 2012 at 10:06 AM, Gregory Beaty greg.bea...@gmail.com
wrote:
Sorry for all
source code for the wixstddba?)
Greg Beaty
greg.bea...@gmail.com
On Mon, Sep 17, 2012 at 1:54 PM, Gregory Beaty greg.bea...@gmail.comwrote:
I don't have access to the logs right now but Rob I think you are right. I
remember when I provided an uninstall button inside of the upgraded bundle
the NETFX 3.5 may be trickier but
creating an ExePackage and referencing that via the WixMbaPrereqPackageId
is all the same.
On Thu, Sep 13, 2012 at 9:18 PM, Gregory Beaty gbe...@spsu.edu wrote:
Thanks Rob.
I do have another issue. How do I disable the ability for the BA to
install
Also I just re-ran the upgrade and the versions are different, but it still
places two different versions into the Add/Remove programs list.
Greg Beaty
greg.bea...@gmail.com
On Sun, Sep 16, 2012 at 10:26 AM, Gregory Beaty greg.bea...@gmail.comwrote:
1. Wix supports same version major upgrades
but can't find it now.
Neil
-Original Message-
From: Gregory Beaty [mailto:greg.bea...@gmail.com]
Sent: 16 September 2012 15:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
1. Wix supports same version major upgrades
Thanks for the reference.
Greg Beaty
greg.bea...@gmail.com
On Sun, Sep 16, 2012 at 12:35 PM, Gregory Beaty greg.bea...@gmail.comwrote:
Even my different version upgrades don't remove the previous installed
version. I seem to have problems uninstalling a previous bundle from an
upgraded
had this issue when I had done some same version installs and then
started changing the version; the cause was multiple entries in ARP. It
might we worth checking this, I found if I removed all the versions then
the upgrades started working.
Neil
-Original Message-
From: Gregory Beaty
Hello,
My WiX MSI package allows same version upgrades with: MajorUpgrade
Schedule=afterInstallInitialize AllowSameVersionUpgrades=yes
DowngradeErrorMessage=A newer version of [ProductName] is already
installed. /.
However when using this with my Manager Bootstrapper Application I never
get the
and never installs my program.
My application is instead replaced by UI shell that the framework installer
uses. Does that make sense, and if so is that a bug?
*Thanks,
Greg Beaty
*
*LinkedIn http://www.linkedin.com/pub/gregory-beaty-jr/42/b6a/a96 |
Personal http://goog_419374978**Website http
know. In WiX v3.7 you also get the
relation type which will further inform you that you have a related Bundle
that is an upgrade but it's operation is None (i.e not upgrade and not
downgrade).
On Thu, Sep 13, 2012 at 4:54 AM, Gregory Beaty greg.bea...@gmail.com
wrote:
Hello,
My WiX MSI
Sorry for the double post.
Greg Beaty
greg.bea...@gmail.com
On Fri, Sep 14, 2012 at 12:19 AM, Gregory Beaty greg.bea...@gmail.comwrote:
Thanks Rob.
I do have another issue. How do I disable the ability for the BA to
install multiple versions of my application? It seems that during
Hello I have created a custom BootstrapperApplication based on the Wix 3.6
Installer. I am now up to point where I am ready to test actual
installations. The log indicates that the log gets up to the point where it
creates a system restore point then it does nothing. After closing the
19 matches
Mail list logo
