Thread: Per app framework version.

Brought to you by: wrowe

mod-aspdotnet-devel

Per app framework version.

From: Todd H. <ele...@ho...> - 2010-05-03 19:22:48

Has anyone given a thought to the possibility of setting AspNetVersion per
mounted application?
Maybe as an optional parameter to the AspNetMount directive, with the
default being the global AspNetVersion.

Re: Per app framework version.

From: William A. R. Jr. <wr...@ro...> - 2010-05-03 20:35:50

On 5/3/2010 2:22 PM, Todd Hicks wrote:
> Has anyone given a thought to the possibility of setting AspNetVersion per
> mounted application?
> Maybe as an optional parameter to the AspNetMount directive, with the
> default being the global AspNetVersion.

It would be very unwise; better to use mod_proxy to front several different
servers running different asp.net levels.  And it's likely not possible unless
the CorBindToRuntimeEx permits multiple .NET engines to coexist in the same
process space.

RE: Per app framework version.

From: Todd H. <ele...@ho...> - 2010-05-03 21:59:03

Just reading up on CorBindToRuntimeEx, and it's been deprecated in the 4.0
framework. But I see what you mean.
I seem to recall on one of my installations in the past that httpd had
multiple processes running (using process explorer or task manager). I don't
know if this was by design or by some config option. Could that be leveraged
somehow?

-----Original Message-----
From: William A. Rowe Jr. [mailto:wr...@ro...] 
Sent: Monday, May 03, 2010 4:09 PM
To: mod...@li...
Subject: Re: Per app framework version.

On 5/3/2010 2:22 PM, Todd Hicks wrote:
> Has anyone given a thought to the possibility of setting AspNetVersion per
> mounted application?
> Maybe as an optional parameter to the AspNetMount directive, with the
> default being the global AspNetVersion.

It would be very unwise; better to use mod_proxy to front several different
servers running different asp.net levels.  And it's likely not possible
unless
the CorBindToRuntimeEx permits multiple .NET engines to coexist in the same
process space.

----------------------------------------------------------------------------
--
_______________________________________________
mod-aspdotnet-devel mailing list
mod...@li...
https://lists.sourceforge.net/lists/listinfo/mod-aspdotnet-devel

RE: Per app framework version.

From: Todd H. <ele...@ho...> - 2010-05-03 22:09:45

This from MSDN:
The .NET Framework version 4 consolidates many of the version 2.0 hosting
APIs. In addition, .NET Framework 4 supports in-process side-by-side runtime
host activation...

-----Original Message-----
From: Todd Hicks [mailto:ele...@ho...] 
Sent: Monday, May 03, 2010 5:59 PM
To: mod...@li...
Subject: RE: Per app framework version.

Just reading up on CorBindToRuntimeEx, and it's been deprecated in the 4.0
framework. But I see what you mean.
I seem to recall on one of my installations in the past that httpd had
multiple processes running (using process explorer or task manager). I don't
know if this was by design or by some config option. Could that be leveraged
somehow?

-----Original Message-----
From: William A. Rowe Jr. [mailto:wr...@ro...] 
Sent: Monday, May 03, 2010 4:09 PM
To: mod...@li...
Subject: Re: Per app framework version.

On 5/3/2010 2:22 PM, Todd Hicks wrote:
> Has anyone given a thought to the possibility of setting AspNetVersion per
> mounted application?
> Maybe as an optional parameter to the AspNetMount directive, with the
> default being the global AspNetVersion.

It would be very unwise; better to use mod_proxy to front several different
servers running different asp.net levels.  And it's likely not possible
unless
the CorBindToRuntimeEx permits multiple .NET engines to coexist in the same
process space.

----------------------------------------------------------------------------
--
_______________________________________________
mod-aspdotnet-devel mailing list
mod...@li...
https://lists.sourceforge.net/lists/listinfo/mod-aspdotnet-devel

----------------------------------------------------------------------------
--
_______________________________________________
mod-aspdotnet-devel mailing list
mod...@li...
https://lists.sourceforge.net/lists/listinfo/mod-aspdotnet-devel

Re: Per app framework version.

From: William A. R. Jr. <wr...@ro...> - 2010-05-03 23:20:58

On 5/3/2010 5:09 PM, Todd Hicks wrote:
> This from MSDN:
> The .NET Framework version 4 consolidates many of the version 2.0 hosting
> APIs. In addition, .NET Framework 4 supports in-process side-by-side runtime
> host activation...

Good to know.  It's awfully heavy-weight, but if it's not impossible, I'd
certainly entertain a patch.

RE: Per app framework version.

From: Todd H. <ele...@ho...> - 2010-05-04 02:15:44

This article: 
http://msdn.microsoft.com/en-us/magazine/ee819091.aspx 
indicates that 1.1 and 2.0 can't be loaded in the same process. Figure 2 on
that page is an in-process compatibility matrix. Personally I'm not deving
1.1 apps but being able to host 2.0 and 4.0 side by side is useful. 
I should be able to account for this by failing if 1.1 && 2.0 are specified.

-----Original Message-----
From: William A. Rowe Jr. [mailto:wr...@ro...] 
Sent: Monday, May 03, 2010 6:54 PM
To: mod...@li...
Subject: Re: Per app framework version.

On 5/3/2010 5:09 PM, Todd Hicks wrote:
> This from MSDN:
> The .NET Framework version 4 consolidates many of the version 2.0 hosting
> APIs. In addition, .NET Framework 4 supports in-process side-by-side
runtime
> host activation...

Good to know.  It's awfully heavy-weight, but if it's not impossible, I'd
certainly entertain a patch.

----------------------------------------------------------------------------
--
_______________________________________________
mod-aspdotnet-devel mailing list
mod...@li...
https://lists.sourceforge.net/lists/listinfo/mod-aspdotnet-devel