1.1 and 2.0 .Net framework in same application?

  • Thread starter Thread starter holysmokes99
  • Start date Start date
H

holysmokes99

I suppose this is a somewhat naive question, but here goes anyway. Is
it possible for me to develop a 2.0 framework dll and reference it in
an application built in 1.1 (provided that both 1.1 and 2.0 framworks
are installed on the machine)?

Thx,
Marcus
 
holysmokes99 said:
I suppose this is a somewhat naive question, but here goes anyway. Is
it possible for me to develop a 2.0 framework dll and reference it in
an application built in 1.1 (provided that both 1.1 and 2.0 framworks
are installed on the machine)?

Thx,
Marcus
Click to expand...
It's possible but why not build both projects on the same platform?

Matti
 
We already have a large application built in 1.1, and are not yet ready
to port it over to 2.0 as there will no doubt be upgrading growing
pains that will need to be resolved. However, if we could add 2.0
framework dlls for added functionality, then that would be great. Is
this really possible?

Thanks,
Marcus
 
I don´t think so, and if possible is not advisable to use .NET 2.0 code from
..NET 1.1 code since the .NET 2.0 code can use stuff that is not understood
by the .NET 1.1 run-times.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
 
holysmokes99 said:
We already have a large application built in 1.1, and are not yet ready
to port it over to 2.0 as there will no doubt be upgrading growing
pains that will need to be resolved. However, if we could add 2.0
framework dlls for added functionality, then that would be great. Is
this really possible?
Click to expand...

I think it is, if you make use of COM Interop to get the two to talk to
one another. Of course, if you do that, you'll be limited to what data
COM can marshal.

I think to guarantee it, though, you'd need to make sure the 2.0 stuff
had its own appdomain. To accomplish that I think you'd need to write an
out-of-process COM server (COM EXE), perhaps something in VB6 (just to
make it relatively easy), which in turn called the 2.0-dependent .NET
assembly. You would reference the COM EXE libraries through a reference
in your .NET 1.1 app.

Then again, I've never tried any of this. That much loose linkage is
bound to be less than optimal...

Rob
 
Interesting suggestion, Rob. I'll give it a try when I get back to this
project in a couple of weeks.

Cheers,
Marcus
 
Back
Top