Sorry, I haven't been following Burn enough.  I thought it was using WPF, my 
mistake.
 
I don't remember the last time I wrote an installer for a non-managed 
application so I'm not sure what that type of longevity buys me.
 
Chris


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

--- On Wed, 1/5/11, Rob Mensching <r...@robmensching.com> wrote:


From: Rob Mensching <r...@robmensching.com>
Subject: Re: [WiX-users] Creating Virtual Directories in c:\inetpub\wwwroot in 
WiX
To: chr...@deploymentengineering.com, "General discussion for Windows Installer 
XML toolset." <wix-users@lists.sourceforge.net>
Date: Wednesday, January 5, 2011, 1:58 AM


1. Burn doesn't require NETFX. A bootstrapper application for Burn may require 
NETFX (for example, I wrote the WiX Bootstrapper Application against NETFX4 to 
show how it could be done) but it doesn't have to. A pure native solution 
(wixstdba.dll) is provided that runs on WinXP SP2 straight up. It probably even 
works on WinXP RTM, but I haven't been able to find an XP RTM CD yet to verify.

2. The nasty thing about NETFX is that it is a side-by-side platform, not 
innately backwards compatible platform. That means if you shipped code compiled 
against NETFX 2.0 you have to run on the NETFX 2.0 or change your .config file 
to say it's okay to run against NETFX 4.0.  We've done that in WiX v3.5 for 
managed DTF custom actions but what happens when NETFX 5.0 comes out? 
Everything probably breaks again... unless you install the version of NETFX you 
need first or you reship your custom actions with updated .config files 
(assuming NETFX still support backwards compatible to whatever version of the 
runtime your code was compiled against).  Note: if you use WiX v3.0, you've 
probably already seen this problem with NETFX 2.0 custom action code running on 
NETFX 4.0 only machines.

I really need to sit down and write the blog entry about the perils of 
side-by-side. I've see this misconception a few times now and it's dangerous in 
setup.

Anyway, that's why we don't write custom actions in managed code as part of the 
WiX toolset. We expect the code to live for a long time... longer than the 
NETFX backwards compatibility guarantees.



On Tue, Jan 4, 2011 at 9:13 AM, Christopher Painter 
<chr...@deploymentengineering.com> wrote:

I'd contribute it, if I could do it using DTF. :-)

Actually an interesting question in my mind... with Burn requiring .NET and 
older operating systems being retired and newer operating systems coming with 
at least .NET 2.0,  at what point (if ever) will the WiX toolset have built in 
custom actions based on managed code?

Chris


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


--- On Tue, 1/4/11, Rob Mensching <r...@robmensching.com> wrote:

> From: Rob Mensching <r...@robmensching.com>
> Subject: Re: [WiX-users] Creating Virtual Directories in c:\inetpub\wwwroot 
> in WiX
> To: "General discussion for Windows Installer XML toolset." 
> <wix-users@lists.sourceforge.net>
> Date: Tuesday, January 4, 2011, 10:44 AM



>  There isn't a custom action in the
> WiX toolset that does this today. It'd
> be cool if someone wanted to contribute it.
>
>
> > I did spend some time over the last week experimenting
> with the WiX 3.5 IIS
> > configuration feature.  It looks promising but I
> could NOT figure out how
> > to
> > get it to set an MSI property that indicated where a
> physical directory for
> > a WebDirectoryor VirtualWebDirectorywas located. 
> So I backed out those
> > changes.  But if someone has figured this out,
> please share!
> >
> > --
> > View this message in context:
> > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-Virtual-Directories-in-c-inetpub-wwwroot-in-WiX-tp688976p5887358.html
> >   Sent from the wix-users mailing list
> archive at Nabble.com.
> >



> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node
> allows customers
> to consolidate database storage, standardize their database
> environment, and,
> should the need arise, upgrade to a full multi-node Oracle
> RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>




------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC



      
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to