Using .Net 1.1 assemblies from a .Net 2.0 App

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

CuriousGeorge - 09 Mar 2006 00:18 GMT

Can anyone point me at some references that discuss the issues involved in
referencing .Net 1.1 assemblies from a .Net 2.0 application?

We are migrating our application to .Net 2.0 and have a number of 3rd party
assemblies that we leverage. Some of them do not yet have support for .Net
2.0. So I'm wondering what kind of problems I might be in for if I try to
combine the two. Obviously I'll need to have both versions of the framework
installed on the machine. Beyond that am I asking for trouble or should
this work seamlessly?

-Brett-

Reply to this Message

"Peter Huang" [MSFT] - 09 Mar 2006 03:31 GMT

Hi Brett,

So there is no such a list about running 1.1 code on .NET 2.0.
Here are the links you may take a look.
http://dotnetdebug.blogspot.com/2006/01/running-net-20-and-11-side-by-side.h
tml
http://blogs.msdn.com/junfeng/archive/2004/07/22/190813.aspx

Commonly we suggest use app.config to force the .NET 1.1 code on .NET 1.1
runtime.
But so far we can not host two runtime in one process, so if we are going
to reference .NET 1.1 as a library in .NET 2.0, we can not run both .NET
1.1 and 2.0 runtime.
If so, I think we need to recompile the .NET 1.1. code on .NET 2.0 if there
is any error.
Or we can write another .NET 1.1 App to host the class library and
interactive with .NET 2.0 with remoting or other IPC(e.g. Web Service).
But commonly the .NET 1.1 code will run fine on .NET 2.0 this is the last
approach we may try.

Best regards,

Peter Huang
Microsoft Online Partner Support

Signature

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

CuriousGeorge - 10 Mar 2006 01:32 GMT

So as I understand it since my app is built on.Net 2.0 any assemblies I
reference will also use .Net 2.0 (even if they were built on .Net 1.1 and
.Net 1.1 is installed on the pc). This will all work as long as none of
those .Net 1.1 assemblies have compatibility issues with .Net 2.0. Correct?

This is good news as it gives my app a good chance of working without
waiting for my 3rd party libs to update to .Net 2.0. Obviously I'l have to
do some thorough testing but I'm optimistic.

-Brett-

> Hi Brett,
>
[quoted text clipped - 25 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

Reply to this Message

"Peter Huang" [MSFT] - 10 Mar 2006 03:39 GMT

Hi Brett,

Yes, you are right.
In a process, there will be only one runtime, .NET 1.1 or .NET 2.0, but not
both.

Best regards,

Peter Huang
Microsoft Online Partner Support

Signature

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Jeroen Vandezande - 09 Mar 2006 16:02 GMT

> Can anyone point me at some references that discuss the issues involved in
> referencing .Net 1.1 assemblies from a .Net 2.0 application?
[quoted text clipped - 5 lines]
> the framework installed on the machine. Beyond that am I asking for
> trouble or should this work seamlessly?

Hi,

I am in the same situation... I use .net 2.0 as dev platform, but I have
some 1.1 DLL's from a third party.
I just added those DLL's to the References of my project and they work
perfectly...
I had no problem at all...

Best Regards,

Jeroen Vandezande

Reply to this Message

CuriousGeorge - 10 Mar 2006 01:33 GMT

Great, that confirms what I understand. I just need to verify that all of
the 3rd party dlls built on .Net 1.1 are compatible with .Net 2.0.

Thanks...

-Brett-

>> Can anyone point me at some references that discuss the issues involved
>> in referencing .Net 1.1 assemblies from a .Net 2.0 application?
[quoted text clipped - 17 lines]
>
> Jeroen Vandezande

Reply to this Message

Using .Net 1.1 assemblies from a .Net 2.0 App

Free Magazines