Using 2.0 in 1.1
-
hey folks, is it possible to use a 2.0 dll in a 1.1 project? i just created a vs 2003 project and tryed to add a reference to a .Net2.0 dll...unsuccessful is there a way to realize my intention anyway? thanks, bernd
-
such a crap! and also no way to create something like a wrapper in 2.0 for 1.1? or something like a .tlb? thx
Nope.
Dave Kreskowiak Microsoft MVP - Visual Basic
-
hey folks, is it possible to use a 2.0 dll in a 1.1 project? i just created a vs 2003 project and tryed to add a reference to a .Net2.0 dll...unsuccessful is there a way to realize my intention anyway? thanks, bernd
Can you put your 2.0 dll behind a web service?
Logifusion[^] If not entertaining, write your Congressman.
-
Can you put your 2.0 dll behind a web service?
Logifusion[^] If not entertaining, write your Congressman.
-
Nope.
Dave Kreskowiak Microsoft MVP - Visual Basic
Hi, haven't tried it but are you sure it isn't possible to enable COM registration in the 2.0 dll and then use it from 1.1 via COM interop? Robert
-
Hi, haven't tried it but are you sure it isn't possible to enable COM registration in the 2.0 dll and then use it from 1.1 via COM interop? Robert
I haven't done it myself either, but I think this is correct... His app will start and load the 1.1 framework, if available(!), or under the latest version installed. When his component is finally created, no matter what interface is used to call it, it'll try to load under the version of the framework that is already running. If the component isn't compatible with it, it'll fail. You can't load two different versions of the framework into the same process. His component will have to run as a remote component in its own process since you can run two versions side-by-side, but in different processes. This, of course, will also come with a performance hit because of the cross-process marshaling.
Dave Kreskowiak Microsoft MVP - Visual Basic
-
I haven't done it myself either, but I think this is correct... His app will start and load the 1.1 framework, if available(!), or under the latest version installed. When his component is finally created, no matter what interface is used to call it, it'll try to load under the version of the framework that is already running. If the component isn't compatible with it, it'll fail. You can't load two different versions of the framework into the same process. His component will have to run as a remote component in its own process since you can run two versions side-by-side, but in different processes. This, of course, will also come with a performance hit because of the cross-process marshaling.
Dave Kreskowiak Microsoft MVP - Visual Basic
You are right. I didn't think of the restriction of only having one framework version within the same process.
-
You are right. I didn't think of the restriction of only having one framework version within the same process.
I compiled my project against .NET1.1 and run it currently on .NET2.0, so i thought i can load some 2.0-dll's dynamicly...still in testing state... -- modified at 18:05 Saturday 5th August, 2006 ok, that does the job. i'm sure there are sometimes some compatibility isues in running my 1.1-App under 2.0 but this price i have to pay. thanks guys