Using VS2005 dll's in 2003 projects

[DaTurk]

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]

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
"DaTurk" wrote:

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.

[DaTurk]

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]]

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.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"DaTurk" <mm******@hotmail.comwrote in message
news:11*********************@m79g2000cwm.googlegro ups.com...

>I know, I figured as much, but I was just hoping there was some strange
hack to get around it.

[Stoitcho Goutsev \(100\)]

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.

--
Stoitcho Goutsev (100)

"DaTurk" <mm******@hotmail.comwrote in message
news:11*********************@i42g2000cwa.googlegro ups.com...

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.