microsoft.public.dotnet.framework

Jon Skeet

2/19/2008 11:51:00 PM

Christopher <Christopher@discussions.microsoft.com> wrote:
> Hello, I have a shipped version of a DLL built on .NET 2.0 for ASP.NET.
> Customers have programmed against it on .NET 2.0. I'm upgrading this DLL to
> .NET 3.5. I don't want to make customers recompile against my new DLL and my
> new DLL contains new namespaces and only new classes.
>
> I'm wanting to redirect the implementations only of the methods within the
> 2.0-based DLL so that they call into the .NET 3.5 DLL instead.
>
> Is calling into a .NET 3.5 DLL from a .NET 2.0 DLL alright in general? Has
> anyone seen any performance, compilation, or other quickiness issues with
> doing this? Thanks!

Assuming they have .NET 3.5 installed, it should be fine. There's
really no such thing as a ".NET 3.5 DLL" - there's just a DLL which
refers to types or assemblies which are part of .NET 3.5.

--
Jon Skeet - <skeet@pobox.com>
http://www.pobox.... Blog: http://www.msmvps.com...
World class .NET training in the UK: http://iterativetrai...