Apps built on 3.0 running on 2.0

Hi All,
Trying to build a case for company wide transition to 3.0. If we have apps
built on 3.0 not using any of the WinFx libaries, any possible issues about
deploying it on clients who are still running 2.0 ?

Thanks in advance.

The framework only loads libraries if the compiler requires it's code -
therefore it's quite possible to build an application and have none of the
referenced libraries loaded.... ever.

..NET 3.0 is really just additional components such as WCF, WWF, CardSpace
etc, which are contained within their own assemblies etc. Much of the .NET
3.0 code base is original .NET 2.0 - except slight tweaks to some of the
language features.

With this in mind it's entirely possible for you to write a .NET application
and deploy it onto a platform that may/may not have .NET 3.0 - the only
criteria would be that you ensure refererences to non .NET 3.0 specfic
features - i.e. .NET 2.0

Finally, remember that .NET frameworks can co-exist on the same platform and
the application will always try and pick up the version it was compiled
against - presume the use of the GAC, or assemblies in the appbase dir, probe
paths.


"MMA" wrote:

> Hi All,
> Trying to build a case for company wide transition to 3.0. If we have apps
> built on 3.0 not using any of the WinFx libaries, any possible issues about
> deploying it on clients who are still running 2.0 ?
>
> Thanks in advance.