net applications are loaded into an appdomain. only one version of an
assembly can loaded at time. if the appdomain is running 1.1 vm, an
attempt to load a 2.0 assembly will fail, as it has dependencies on
routines n the 2.0 clr.
you have two options.
1) create your httpmodule in 1.1 for it can be hosted by either enviroment.
2) convert all vdirs to 2.0. in most cases 2.0 vdirs can run 1.1
assemblies without a recompile.
-- bruce (sqlwork.com)
> net applications are loaded into an appdomain. only one version of an
> assembly can loaded at time. if the appdomain is running 1.1 vm, an
[quoted text clipped - 48 lines]
>
> - Show quoted text -
Bruce -
Thanks for the response.
I tried solution #2 and it seemed to work.
For solution #1, if I re-create the HttpModule in version 1.1, won't I
have the same issues with my 2.0 applications - since they would be a
"2.0 app domain" and wouldn't be able to see the 1.1 library. Or, do
you mean have 1.1 and 2.0 versions of the HttpModule co-exist in the
GAC. Would I need a different strong name for each version of the
library or not?
Peter Bromberg [C# MVP] - 31 Oct 2007 19:41 GMT
As Bruce indicated, 1.1 assemblies normally load and are executed in the 2.0
App Pool with no issues.
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com
> For solution #1, if I re-create the HttpModule in version 1.1, won't I
> have the same issues with my 2.0 applications - since they would be a
> "2.0 app domain" and wouldn't be able to see the 1.1 library. Or, do
> you mean have 1.1 and 2.0 versions of the HttpModule co-exist in the
> GAC. Would I need a different strong name for each version of the
> library or not?