Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-12 Thread Evans, Jim
As per Rob's suggestion, here's a letter to the SQL team RE: the SQL
Express installer.
-
Dear SQL Server Team:

SQL Server 2005 Express Edition has become a platform that many
developers have come to count on in building applications. It provides a
flexible, redistributable database engine, suitable for the creation of
database applications.

One problem many developers face is in the deployment of their
solutions. Currently, there is no way to seamlessly integrate the setup
of SQL Server 2005 Express Edition into the setup of a developer's
application. The developer is forced to either install silently,
providing the user with no progress feedback during the installation;
install with minimal UI, which displays a non-integrated progress meter
for a suboptimal end user experience; or to force the user to install
SQL Server 2005 Express Edition as a separate install prerequisite. None
of these options are palatable for developers wishing to provide a
smooth, integrated installation experience for their users.

The .NET Framework redistributable had much the same problem until
version 3.0. Beginning with the 3.0 version, the framework bootstrapper
responds to an argument passed on the command line (the /progress
switch) which allows the developer to register for progress messages
transmitted back to his code via a named pipe. A whitepaper describing
how developers can take advantage of their approach is available on the
MSDN website (found at
http://msdn.microsoft.com/en-us/library/aa663365.aspx at the time of
this writing). Implementing a similar solution for the SQL Server
Express Edition installer would go a long way toward helping developers
who need to use the product, but would like to present their users with
a custom setup UI.

Looking toward the future, the WiX toolset is looking to add a custom
bootstrapper in a future version. Without a progress reporting solution
in place, consumers of that bootstrapper will not be able to seamlessly
integrate SQL Server Express Edition into their setups. Please consider
this a request to implement what should be a low-cost, low-risk feature
into the SQL Server installer.

Sincerely,
Jim Evans, Numara Software

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday, June 06, 2008 1:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

If you write it, I'll add my name.  I'd even be happy to try to find the
right people to send it to.  smile/

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim
Sent: Friday, June 06, 2008 10:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

RE: SQL Express installer progress:
I only recently learned of the .NET Framework's installation progress
solution, and am planning on using it. As near as I can tell, SQL
Express does not provide a similar solution, so I guess we should start
working on that letter. grin/

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday, June 06, 2008 1:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

There is a feature planned to provide progress to parent processes of
the bootstrapper.  The .NET Framework does this already, we'll probably
do the identical thing (presuming it is rich enough).  I don't know if
SQL Express does the same... if not, then the progress for that
component will be dismal and we should all collectively send a letter to
the team to ask them to implement a solution like the .NET Framework.
grin/

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim
Sent: Friday, June 06, 2008 10:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

Bob Arnson wrote:
 It's unlikely to change the date when the bootstrapper becomes
 available. Working on it in the v4 branch gives us the flexibility to
 ship it in stages and not be forced to do a more limited release
just
 to ship v3. Also note that there's nothing that ties the bootstrapper
to
 a particular build of WiX; you can easily use v3 to build your setups
 and v4 for the bootstrapper.

Fair enough. I'm at the point in my project where I was hoping that I
didn't have to build my own bootstrapper. I guess I'll refactor when the
bootstrap framework is available.

 What aspects of the design are you interested in? The biggest piece is

 all internal: e.g., how the worker thread handles installations and
 communicates progress with the UX thread.

Communicating progress is really one of the things I struggle with. How
do you communicate progress with wrapped package

Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-12 Thread Christopher Painter


YAHOO.Shortcuts.hasSensitiveText = true;
YAHOO.Shortcuts.sensitivityType = [adult];
YAHOO.Shortcuts.doUlt = false;
YAHOO.Shortcuts.location = us;
YAHOO.Shortcuts.document_id = 0;
YAHOO.Shortcuts.document_type = ;
YAHOO.Shortcuts.document_title = Re: [WiX-users] Proposed adjustments the WiX 
v2 and WiX v3 roadmap.;
YAHOO.Shortcuts.document_publish_date = ;
YAHOO.Shortcuts.document_author = [EMAIL PROTECTED];
YAHOO.Shortcuts.document_url = ;
YAHOO.Shortcuts.document_tags = ;
YAHOO.Shortcuts.document_language = english;
YAHOO.Shortcuts.annotationSet = {lw_1213276941_0:{text:Deployment 
Engineering 
Blog,extended:0,startchar:590,endchar:616,start:590,end:616,extendedFrom:,predictedCategory:,predictionProbability:0,weight:1,type:[shortcuts:\/us\/instance\/identifier\/hyperlink\/http],category:[IDENTIFIER],context:MSFT
 )  playing in the 4.5 work?Christopher Painter, Author of Deployment 
Engineering Blog Have a hot tip, know a secret or read 
a,metaData:{linkHref:http:\/\/blog.deploymentengineering.com\/,linkProtocol:http,linkRel:nofollow,linkTarget:_blank,visible:true},ult:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AoSSTIRppXtngw5XaFq3Kj5jk70X,ult_hover:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AhYwqFeDli8apbeRi6HrXrNjk70X},lw_1213276941_1:{text:E-Mail
 
Me,extended:0,startchar:846,endchar:854,start:846,end:854,extendedFrom:,predictedCategory:,predictionProbability:0,weight:1,type:[shortcuts:\/us\/instance\/identifier\/hyperlink\/mailto],category:[IDENTIFIER],context:secret
 or read a really good thread that deserves attention? E-Mail Me   --- On Thu, 
6\/12\/08, Evans, Jim  wrote:   From: Evans,
 Jim,metaData:{linkHref:mailto:[EMAIL 
PROTECTED]#39;s,linkProtocol:mailto,linkRel:nofollow,linkTarget:_blank,linkYmailto:mailto:[EMAIL
 
PROTECTED]#39;s,visible:true},ult:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AnlPMO09QjRwS1TtvDukVjdjk70X,ult_hover:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AjuK5oLxLe.0TzZs303WkSFjk70X},lw_1213276941_2:{text:[EMAIL
 
PROTECTED],extended:0,startchar:915,endchar:942,start:915,end:942,extendedFrom:,predictedCategory:,predictionProbability:0,weight:1,type:[shortcuts:\/us\/instance\/identifier\/email_address],category:[IDENTIFIER],context:that
 deserves attention? E-Mail Me   --- On Thu, 6\/12\/08, Evans, Jim  wrote:   
From: Evans, Jim  Subject: Re: [WiX-users] Proposed
 
adjustments,metaData:{visible:true},ult:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AsxBRK25ygTopf8miwmDDvpjk70X,ult_hover:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=Aom8HQuUCutOUsBvlTLm6Ghjk70X},lw_1213276941_3:{text:wix-users@lists.sourceforge.net,extended:0,startchar:1269,endchar:1299,start:1269,end:1299,extendedFrom:,predictedCategory:,predictionProbability:0,weight:1,type:[shortcuts:\/us\/instance\/identifier\/email_address],category:[IDENTIFIER],context:v3
 roadmap. To: \General discussion for Windows Installer XML toolset.\  Date: 
Thursday, June 12, 2008, 7:43 AM   As per
 
Rob's,metaData:{visible:true},ult:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AocFZfjj.XlfX8KaouFUF7Zjk70X,ult_hover:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AiZXlzazuutwkzWANoAvvFtjk70X},lw_1213276941_4:{text:http:\/\/msdn.microsoft.com\/en-us\/library\/aa663365.aspx,extended:0,startchar:2849,endchar:2901,start:2849,end:2901,extendedFrom:,predictedCategory:,predictionProbability:0,weight:1,type:[shortcuts:\/us\/instance\/identifier\/URL],category:[IDENTIFIER],context:their
 approach is available on the MSDN website (found at 
http:\/\/msdn.microsoft.com\/en-us\/library\/aa663365.aspx at the time of this 
writing). Implementing a similar
 
solution,metaData:{visible:true},ult:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AonFKzUS3ECh_0st3xKQCk9jk70X,ult_hover:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AhgYQrlZSWBMNXODV7oE3IBjk70X},lw_1213276941_5:{text:Numara
 
Software,extended:0,startchar:3560,endchar:3574,start:3560,end:3574,extendedFrom:,predictedCategory:,predictionProbability:0,weight:1.07686,type:[shortcuts:\/concept],category:[CONCEPT],context:low-risk
 feature into the SQL Server installer. Sincerely, Jim Evans, Numara Software 
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
Behalf Of Rob
 
Mensching,metaData:{visible:true},ult:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=AuQtZ7o3LVreiuXmC.pM1j5jk70X,ult_hover:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt=Asclim0XytozA7AIsLFP3rtjk70X},lw_1213276941_6:{text:[EMAIL
 
PROTECTED],extended:0,startchar:3610,endchar:3648,start:3610,end:3648,extendedFrom:,predictedCategory:,predictionProbability:0,weight:1,type:[shortcuts:\/us\/instance\/identifier\/email_address],category:[IDENTIFIER],context:Server
 installer. Sincerely, Jim Evans, Numara Software -Original Message- 
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching 
Sent: Friday, June
 
06,metaData:{visible:true},ult:http:\/\/fe.shortcuts.search.yahoo.com\/build;_ylt

Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-12 Thread Blair Murri

In my opinion, the biggest current issue is the fact that you still have to 
have a bootstrapper to install MSI 4.5 before you can start your MSI, followed 
by a lack of desire to take on distributing MSI 4.5 for those of us deploying 
over the internet.

The fact that almost no one knows about it is probably bigger, however.

From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Christopher Painter 
[EMAIL PROTECTED]
Sent: Thursday, June 12, 2008 6:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

cut-big-blob-of-text/

I've not done much with MSI 4.5 and it's embedded chainer.nbsp;nbsp; Is there 
a larger platform issue to tackle in getting all of thenbsp; various ISV's ( 
including the hundreds of teams at MSFT )nbsp; playing in the 4.5 work?

nbsp;


Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves 
attention? E-Mail Me

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-06 Thread Rob Mensching
http://robmensching.com/blog/archive/2008/06/06/Proposed-adjustments-the-WiX-v2-and-WiX-v3-roadmap.aspx

Based on the feedback left by those of you here and elsewhere, I've posted some 
proposed adjustments to our current roadmap.  I am curious what people think 
about trimming the next releases of WiX v2 and WiX v3 to get done sooner.  
Feedback here or as comments on my blog is appreciated.


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-06 Thread Bob Arnson
Evans, Jim wrote:
 This is sorely disappointing to me personally. Quite frankly, I need the
 bootstrapper. I hate that I'll be waiting for WiX v4 to get it. 

It's unlikely to change the date when the bootstrapper becomes 
available. Working on it in the v4 branch gives us the flexibility to 
ship it in stages and not be forced to do a more limited release just 
to ship v3. Also note that there's nothing that ties the bootstrapper to 
a particular build of WiX; you can easily use v3 to build your setups 
and v4 for the bootstrapper.

 In an
 earlier email, Rob, you mentioned that your team had the design pretty
 well nailed down, though the code has a long way to go. Is there any
 chance that the community could get a peek at that design?
   

What aspects of the design are you interested in? The biggest piece is 
all internal: e.g., how the worker thread handles installations and 
communicates progress with the UX thread.

-- 
sig://boB
http://joyofsetup.com/



-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-06 Thread Rob Mensching
To provide a bit more detail on what Bob said, the biggest difference between 
the planned WiX bootstrapper and the other bootstrappers discussed here is to 
create something with built in layers so that you can use only the 
functionality that you want.  Additionally, the hope is to make the binary very 
tiny (definitely  500K, and I personally want to come in  120K) with very few 
dependencies.  No earth shattering patentable functionality just very tight 
C/C++ code.

Also, Bob pointed out that this is the same struggle I had when we forked WiX 
v3 off of WiX v2.  There was feature creep affecting the WiX v2 schedule so we 
just had to cut the new stuff free.  Thus WiX v3 was born.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Friday, June 06, 2008 09:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

Evans, Jim wrote:
 This is sorely disappointing to me personally. Quite frankly, I need the
 bootstrapper. I hate that I'll be waiting for WiX v4 to get it.

It's unlikely to change the date when the bootstrapper becomes
available. Working on it in the v4 branch gives us the flexibility to
ship it in stages and not be forced to do a more limited release just
to ship v3. Also note that there's nothing that ties the bootstrapper to
a particular build of WiX; you can easily use v3 to build your setups
and v4 for the bootstrapper.

 In an
 earlier email, Rob, you mentioned that your team had the design pretty
 well nailed down, though the code has a long way to go. Is there any
 chance that the community could get a peek at that design?


What aspects of the design are you interested in? The biggest piece is
all internal: e.g., how the worker thread handles installations and
communicates progress with the UX thread.

--
sig://boB
http://joyofsetup.com/



-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-06 Thread Evans, Jim
Bob Arnson wrote:
 It's unlikely to change the date when the bootstrapper becomes 
 available. Working on it in the v4 branch gives us the flexibility to 
 ship it in stages and not be forced to do a more limited release
just 
 to ship v3. Also note that there's nothing that ties the bootstrapper
to 
 a particular build of WiX; you can easily use v3 to build your setups 
 and v4 for the bootstrapper.

Fair enough. I'm at the point in my project where I was hoping that I
didn't have to build my own bootstrapper. I guess I'll refactor when the
bootstrap framework is available.

 What aspects of the design are you interested in? The biggest piece is

 all internal: e.g., how the worker thread handles installations and 
 communicates progress with the UX thread.

Communicating progress is really one of the things I struggle with. How
do you communicate progress with wrapped package installations? In
other words, if I wanted to bootstrap a prerequisite package that the
manufacturer distributes only as an executable setup.exe (not a
standalone MSI file)* to provide my user with a unified installation
experience, how does your design propose to allow me to do that?

*Examples of said packages are the .NET Framework installer and the SQL
Server 2005 Express installer. Both are common prerequisites for
applications, both are MSI-based installs, but do not provide standalone
.MSI installers. Unifying the installation experience for applications
that install these packages is difficult-to-impossible.

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-06 Thread Rob Mensching
There is a feature planned to provide progress to parent processes of the 
bootstrapper.  The .NET Framework does this already, we'll probably do the 
identical thing (presuming it is rich enough).  I don't know if SQL Express 
does the same... if not, then the progress for that component will be dismal 
and we should all collectively send a letter to the team to ask them to 
implement a solution like the .NET Framework.  grin/

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim
Sent: Friday, June 06, 2008 10:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

Bob Arnson wrote:
 It's unlikely to change the date when the bootstrapper becomes
 available. Working on it in the v4 branch gives us the flexibility to
 ship it in stages and not be forced to do a more limited release
just
 to ship v3. Also note that there's nothing that ties the bootstrapper
to
 a particular build of WiX; you can easily use v3 to build your setups
 and v4 for the bootstrapper.

Fair enough. I'm at the point in my project where I was hoping that I
didn't have to build my own bootstrapper. I guess I'll refactor when the
bootstrap framework is available.

 What aspects of the design are you interested in? The biggest piece is

 all internal: e.g., how the worker thread handles installations and
 communicates progress with the UX thread.

Communicating progress is really one of the things I struggle with. How
do you communicate progress with wrapped package installations? In
other words, if I wanted to bootstrap a prerequisite package that the
manufacturer distributes only as an executable setup.exe (not a
standalone MSI file)* to provide my user with a unified installation
experience, how does your design propose to allow me to do that?

*Examples of said packages are the .NET Framework installer and the SQL
Server 2005 Express installer. Both are common prerequisites for
applications, both are MSI-based installs, but do not provide standalone
.MSI installers. Unifying the installation experience for applications
that install these packages is difficult-to-impossible.

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-06 Thread Evans, Jim
RE: SQL Express installer progress:
I only recently learned of the .NET Framework's installation progress
solution, and am planning on using it. As near as I can tell, SQL
Express does not provide a similar solution, so I guess we should start
working on that letter. grin/

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday, June 06, 2008 1:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

There is a feature planned to provide progress to parent processes of
the bootstrapper.  The .NET Framework does this already, we'll probably
do the identical thing (presuming it is rich enough).  I don't know if
SQL Express does the same... if not, then the progress for that
component will be dismal and we should all collectively send a letter to
the team to ask them to implement a solution like the .NET Framework.
grin/

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim
Sent: Friday, June 06, 2008 10:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

Bob Arnson wrote:
 It's unlikely to change the date when the bootstrapper becomes
 available. Working on it in the v4 branch gives us the flexibility to
 ship it in stages and not be forced to do a more limited release
just
 to ship v3. Also note that there's nothing that ties the bootstrapper
to
 a particular build of WiX; you can easily use v3 to build your setups
 and v4 for the bootstrapper.

Fair enough. I'm at the point in my project where I was hoping that I
didn't have to build my own bootstrapper. I guess I'll refactor when the
bootstrap framework is available.

 What aspects of the design are you interested in? The biggest piece is

 all internal: e.g., how the worker thread handles installations and
 communicates progress with the UX thread.

Communicating progress is really one of the things I struggle with. How
do you communicate progress with wrapped package installations? In
other words, if I wanted to bootstrap a prerequisite package that the
manufacturer distributes only as an executable setup.exe (not a
standalone MSI file)* to provide my user with a unified installation
experience, how does your design propose to allow me to do that?

*Examples of said packages are the .NET Framework installer and the SQL
Server 2005 Express installer. Both are common prerequisites for
applications, both are MSI-based installs, but do not provide standalone
.MSI installers. Unifying the installation experience for applications
that install these packages is difficult-to-impossible.


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-06 Thread Rob Mensching
If you write it, I'll add my name.  I'd even be happy to try to find the right 
people to send it to.  smile/

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim
Sent: Friday, June 06, 2008 10:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

RE: SQL Express installer progress:
I only recently learned of the .NET Framework's installation progress
solution, and am planning on using it. As near as I can tell, SQL
Express does not provide a similar solution, so I guess we should start
working on that letter. grin/

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday, June 06, 2008 1:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

There is a feature planned to provide progress to parent processes of
the bootstrapper.  The .NET Framework does this already, we'll probably
do the identical thing (presuming it is rich enough).  I don't know if
SQL Express does the same... if not, then the progress for that
component will be dismal and we should all collectively send a letter to
the team to ask them to implement a solution like the .NET Framework.
grin/

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim
Sent: Friday, June 06, 2008 10:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

Bob Arnson wrote:
 It's unlikely to change the date when the bootstrapper becomes
 available. Working on it in the v4 branch gives us the flexibility to
 ship it in stages and not be forced to do a more limited release
just
 to ship v3. Also note that there's nothing that ties the bootstrapper
to
 a particular build of WiX; you can easily use v3 to build your setups
 and v4 for the bootstrapper.

Fair enough. I'm at the point in my project where I was hoping that I
didn't have to build my own bootstrapper. I guess I'll refactor when the
bootstrap framework is available.

 What aspects of the design are you interested in? The biggest piece is

 all internal: e.g., how the worker thread handles installations and
 communicates progress with the UX thread.

Communicating progress is really one of the things I struggle with. How
do you communicate progress with wrapped package installations? In
other words, if I wanted to bootstrap a prerequisite package that the
manufacturer distributes only as an executable setup.exe (not a
standalone MSI file)* to provide my user with a unified installation
experience, how does your design propose to allow me to do that?

*Examples of said packages are the .NET Framework installer and the SQL
Server 2005 Express installer. Both are common prerequisites for
applications, both are MSI-based installs, but do not provide standalone
.MSI installers. Unifying the installation experience for applications
that install these packages is difficult-to-impossible.


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-06 Thread Peterson, Joel
That all sounds fine to me personally, as long as I can start investing
my time in refactoring all of our installers with WiX v4 (and its
bootstrapper!) sometime around the time you would said it would be
available.

Joel

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday, June 06, 2008 9:56 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

To provide a bit more detail on what Bob said, the biggest difference
between the planned WiX bootstrapper and the other bootstrappers
discussed here is to create something with built in layers so that you
can use only the functionality that you want.  Additionally, the hope is
to make the binary very tiny (definitely  500K, and I personally want
to come in  120K) with very few dependencies.  No earth shattering
patentable functionality just very tight C/C++ code.

Also, Bob pointed out that this is the same struggle I had when we
forked WiX v3 off of WiX v2.  There was feature creep affecting the WiX
v2 schedule so we just had to cut the new stuff free.  Thus WiX v3 was
born.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Friday, June 06, 2008 09:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.

Evans, Jim wrote:
 This is sorely disappointing to me personally. Quite frankly, I need
the
 bootstrapper. I hate that I'll be waiting for WiX v4 to get it.

It's unlikely to change the date when the bootstrapper becomes
available. Working on it in the v4 branch gives us the flexibility to
ship it in stages and not be forced to do a more limited release just
to ship v3. Also note that there's nothing that ties the bootstrapper to
a particular build of WiX; you can easily use v3 to build your setups
and v4 for the bootstrapper.

 In an
 earlier email, Rob, you mentioned that your team had the design pretty
 well nailed down, though the code has a long way to go. Is there any
 chance that the community could get a peek at that design?


What aspects of the design are you interested in? The biggest piece is
all internal: e.g., how the worker thread handles installations and
communicates progress with the UX thread.

--
sig://boB
http://joyofsetup.com/




-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.

2008-06-06 Thread Jason
I like the new plan, let's get it done! :D

On Fri, Jun 6, 2008 at 3:34 AM, Rob Mensching
[EMAIL PROTECTED] wrote:
 http://robmensching.com/blog/archive/2008/06/06/Proposed-adjustments-the-WiX-v2-and-WiX-v3-roadmap.aspx

 Based on the feedback left by those of you here and elsewhere, I've posted 
 some proposed adjustments to our current roadmap.  I am curious what people 
 think about trimming the next releases of WiX v2 and WiX v3 to get done 
 sooner.  Feedback here or as comments on my blog is appreciated.


 -
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users