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# / August 2006

Tip: Looking for answers? Try searching our database.

Using VS2005 dll's in 2003 projects

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
DaTurk - 31 Aug 2006 16:24 GMT
Hi,
I'm converting our code base into VS2005 and we have alot of Managed
c++.  Problem is, is that for some reason some of our code will
compile, but doesn't run correctly in VS2005.  So, as we can continue
moving forward we decided to keep the managed c++ stuff in VS2003 and
just compile them seperatley.

My problem is that when I tried to reference one of our VS2005 dll's is
gave me an error, so I tried to reference several different 2005
generated dll's and had the same problem.  SO I referenced the same dll
in but genereated in 2003 and it was fine.  Is there a problem with
this?  BEcause I really do need to reference these libraries that I'm
geneerating in 2005, in the MCPP in 2003.
Thanks in advance for the help.
WhiteWizard - 31 Aug 2006 16:35 GMT
I'm pretty sure you are NOT going to be able to do that.  Think about it.  
Your application is using version 1.1 of the framework, and the dll's will be
trying to use 2.0 version of the framework.

WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT

> Hi,
> I'm converting our code base into VS2005 and we have alot of Managed
[quoted text clipped - 10 lines]
> geneerating in 2005, in the MCPP in 2003.
> Thanks in advance for the help.
DaTurk - 31 Aug 2006 16:44 GMT
I know, I figured as much, but I was just hoping there was some strange
hack to get around it.
Nicholas Paldino [.NET/C# MVP] - 31 Aug 2006 16:57 GMT
That's great thinking, because using unsupported hacks always
contributes to the stability of a system =)

   My suggestion is to figure out why its not working in 2005 and fix it.
You will be thankful that you did.

Signature

         - Nicholas Paldino [.NET/C# MVP]
         - mvp@spam.guard.caspershouse.com

>I know, I figured as much, but I was just hoping there was some strange
> hack to get around it.
Stoitcho Goutsev (100) - 31 Aug 2006 22:08 GMT
You cannot do that. .NET 2.0 introduces new types, new type members, etc not
to speak of new things like generics, anonymous methods and so. It is pretty
obvious that .NET2.0 code cannot run in 1.x environment. Because of this MS
made 2.0 images not loadable by 1.x runtime. As soon as you try to do this a
"bad image" exception so thrown.

Signature

Stoitcho Goutsev (100)

> Hi,
> I'm converting our code base into VS2005 and we have alot of Managed
[quoted text clipped - 10 lines]
> geneerating in 2005, in the MCPP in 2003.
> Thanks in advance for the help.

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.