Hello!
I thought I had strategy clear to me that if I want to use .NET in an
VC6/MFC I must use compile in VC8 with the CLR switch.
But now I get another answer it says. I asked this question.
If I want to use the .NET framework for an VC6/MFC application I must
compile the VC6/MFC to VC8 using the /CLR switch after removing all
the errors?
I received this answer
If you wan to use .NET 2.0, yes. You can do it with VC 7.1 (2003) for .NET
1.1, but you won't have the new managed C++ syntax.
If I can't use the new managed C++ syntax what consequences will that have
and is there other limitation that will exist on my updated VC6/MFC if I use
VC7.1 instead of VS 2005(VC8)?
For example is it still possible to use .NET framework classes from
anywhere, including adding new code to old classes?
I assume that if I use VC7.1 it's not so easy to use different .NET language
as it is if I use VS2005(VC8).
So my question is when is it sufficient to use VC 7.1 and when should I use
VC8?
//Tony
Carl Daniel [VC++ MVP] - 28 Oct 2005 00:33 GMT
> Hello!
>
[quoted text clipped - 22 lines]
> So my question is when is it sufficient to use VC 7.1 and when should
> I use VC8?
Only you can answer that for sure.
VC8 has new facilities in MFC to make it _easy_ to use maanged code in your
MFC app. VC7.1 has no such facilities, so you'd have to "roll your own".
VC8 has the new C++/CLI which makes it _easy_ to write managed code. VC7.1
supports only the older managed extensions for C++ syntax, which is
considerably harder to write and doesn't expose as much .NET functionality.
For a project that you haven't even started the porting effort, I'd say
going to VC7.1 would be the wrong choice, since VC8 will be officially
released in just over a week.
-cd