Juan
Mon Apr 21 11:56:09 CDT 2008
re:
!> as long as I haven't made reference to anything beyond 2.0's framework,
!> or changed the property on MY IIS (or the server's) to reference dotnet
!> framework beyond 2.0 - things on the website in my test (local) environment
!> and the production environment - should function as before.
!> Right?
Right.
Juan T. Llibre, asp.net MVP
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
======================================
"Blasting Cap" <goober@christian.net> wrote in message news:OkfxX88oIHA.3976@TK2MSFTNGP03.phx.gbl...
> Ok -
>
> I think I understand.
>
> I guess I didn't ask the question I really wanted the answer to very well. But from what I understand about your
> response, it shouldn't affect it.
>
> What I have is a system with VS 2005, and framework 2.0 on it, that I develop from. Also in the mix is a server
> (Server 2003) running framework 2.0 as well.
>
> If I were to install Framework 3.5 on my machine (XP, VS 2005) and work on the app that resides on the server
> (Server2003), as long as I don't change the .net property in IIS, that property should stay the same. Meaning, when I
> code & test on my machine, where I have IIS and that website installed, make changes, etc - when I deploy it (or copy
> code to) the server with framework 2.0 installed, as long as I haven't made reference to anything beyond 2.0's
> framework, or changed the property on MY IIS (or the server's) to reference dotnet framework beyond 2.0 - things on
> the website in my test (local) environment and the production environment - should function as before.
>
> Right?
>
> ;-)
>
> BC
>
> Andy wrote:
>> From what I understand...
>>
>> To run mixed .NET assemblies on a computer, first install each .NET
>> framework the assemblies call.
>>
>> A single Windows process can only load and run one .NET framework.
>> This means that a process can only run assemblies targeted for
>> the .NET framework that was first loaded by that process. This will
>> be the .NET framework used by the first assembly that the process
>> loads.
>>
>> The major impact this restriction has appears in IIS where each
>> application pool runs as a single process with one framework. This is
>> why you can't mix .NET frameworks in a web application or webservice
>> running on IIS.
>>
>> In a similar way, Visual Studio .NET also runs as a single process.
>> As Visual Studio .NET is itself written in .NET, the framework that
>> gets loaded is the framework the VS IDE was written in. This means
>> you won't be able to link assemblies targeted for a different version
>> of .NET into projects you developed with that version of Visual
>> Studio.
>>
>> If the mixed assemblies run under different process so that each .NET
>> framework can run, and you have a mechanisim in place to communicate
>> between the processes (ie messaging), then you can have a mix of .NET
>> Framework targeted assemblies for the same application.
>>