Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / C# / May 2007

Tip: Looking for answers? Try searching our database.

Using .Net 2.0 components in .Net 1.1?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ethan Strauss - 10 May 2007 21:40 GMT
Hi,
   I need to convert a big .Net 1.1 solution to .Net 2.0. There is a LOT of
code here and I do not want to do the conversion all in one go. I would like
to be able convert individual projects from the solution to 2.0 and then
reference them from the 1.1 solution, but when I try to add a 2.0 .dll into
a 1.1 project, I get an error
       "A reference to ... could not be added. This is not a valid assembly
or COM component....."
I can reference this same component in other 2.0 projects, so I think it is
valid for 2.0, but not 1.1. Is there a way to convince .Net 1.1 to read a
.Net 2.0 dll?
Thanks!
Ethan

Ethan Strauss Ph.D.
Bioinformatics Scientist
Promega Corporation
2800 Woods Hollow Rd.
Madison, WI 53711
608-274-4330
800-356-9526
ethan.strauss@promega.com
Jon Skeet [C# MVP] - 10 May 2007 21:47 GMT
> Hi,
>     I need to convert a big .Net 1.1 solution to .Net 2.0. There is a LOT of
[quoted text clipped - 7 lines]
> valid for 2.0, but not 1.1. Is there a way to convince .Net 1.1 to read a
> .Net 2.0 dll?

No - go the other way round instead; start off with the top-level
project, and make that refer to 1.1 DLLs. That will work fine.
Gradually work down the dependency tree.

Signature

Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet   Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

Ethan Strauss - 11 May 2007 15:07 GMT
OK. Thanks to all. I was afraid I would have to do that. I could have
started with smaller chunks the other way 'round...
I'll start today!
Ethan

>> Hi,
>>     I need to convert a big .Net 1.1 solution to .Net 2.0. There is a LOT
[quoted text clipped - 16 lines]
> project, and make that refer to 1.1 DLLs. That will work fine.
> Gradually work down the dependency tree.
Tom Porterfield - 10 May 2007 21:50 GMT
> Hi,
>     I need to convert a big .Net 1.1 solution to .Net 2.0. There is a LOT of
[quoted text clipped - 7 lines]
> valid for 2.0, but not 1.1. Is there a way to convince .Net 1.1 to read a
> .Net 2.0 dll?

Not directly, no.  You could set up a remoting scheme of some sort to go
from the 1.1 to 2.0 dll indirectly, but you cannot directly reference a
2.0 assembly from a 1.1 assembly.  Nor you can load a 2.0 assembly under
the 1.1 framework.
Signature

Tom Porterfield

Andy - 10 May 2007 21:52 GMT
On May 10, 4:40 pm, "Ethan Strauss" <ethan dot strauss at Promega dot
com> wrote:
> Hi,
>     I need to convert a big .Net 1.1 solution to .Net 2.0. There is a LOT of
[quoted text clipped - 7 lines]
> valid for 2.0, but not 1.1. Is there a way to convince .Net 1.1 to read a
> .Net 2.0 dll?

Try the other way.  For example, convert your application project
first, and it can use assemblies from .Net 1.1 without recompiling.
There's no way to get 1.1 to use 2.0 assemblies.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.