Both InstallShield and MSI 4.5 have done some work in this area to address your
concerns. Prereqs are no longer required to be done up front. You can fire up
your UI and then associate the prereq to feature action state and then roll
through your packages using one big transaction. It's really neat stuff.
Eitherway, I found this article today which I like alot for the kinds of
installs I've been writing lately.
http://blogs.msdn.com/tims/archive/2008/05/12/introducing-the-third-major-release-of-windows-presentation-foundation.aspx
Neil Enns <[EMAIL PROTECTED]> wrote:
.EmailQuote { PADDING-LEFT: 4pt; MARGIN-LEFT: 1pt; BORDER-LEFT: #800000
2px solid } P { MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px } The problem
with option 1 is that it means we have to give up control of the end-to-end
install and out of box experience for our product. When you are trying to
construct a carefully designed user experience and impression of your
application, a bootstrapper is a pretty fugly addition to the mix. Contrast
that with our DirectX 9.0 install, which we can seamlessly fold into our
installer with no need for intervention by the user.
I'm sure there are plenty of reasons why the .NET team had to go with the
distribution solution they did. It just means our final experience winds up
being less than we'd hoped. Ah well.
Neil
---------------------------------
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Adam Majer [EMAIL
PROTECTED]
Sent: Sunday, May 18, 2008 6:21 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing .NET 3.5 redist?
Christopher Painter wrote:
> The WiX `philosophy` seems to be don't add .NET dependencies to your
> install and don't redist the framework. Just do an AppSearch/Launch
> Condition and tell the user to go do it on their own. Personally
> this conflicts with my needs and results in one of the many reasons why
> I can't use WiX even though I'd like to.
The limitation is with Windows Installer, *not* WiX. The correct way of
doing this is either,
1. a bootstrapper that will check for MSI and install it if needed, or
2. just ship your MSI with the requirement condition and let the
destination deal with installing .NET 3.5.
For corporate deployments, #2 is probably best while option #1 is better
for the home user.
MSI is just a single-transaction-at-a-time installer. It is not like
Debian's APT that can install dozens if not more dependencies for you at
the same time as it installs or upgrades hundreds of other applications.
- Adam
--
Mail Etiquette
==============
* Quote properly or not at all. Top posters, this applies to you!
* When replying to posts on mailing lists, only address the mailing list
unless poster explicitly requested you include them in CC
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
