VC 6.0 <-> .NET compatibility

[Peter Gliwa]

Hi .NET experts,

I've been using VC 6.0 for a couple of years now.
Before buying a .NET license, I would like to estimate the effort necessary to port my existing projects to the new development platform.

I have searched this Site for FAQs/articles, but found entries handling quite specific topics only.

The projects to speak of make extensive use of the MFC and use third party DLLs, if this information is of any help for the effort estimation.

Thanx in advance & have a nice day,
Peter

[TheCPUWizard]

If you are going to continue programming in UNMANAGED C++, then there should be very few porting issues.

Onthe other hand moving from un-managed to managed application development is a paradigm shift [often perfromed without the use of a clutch :eek: ] that is equal to the shift from "C" to "C++".

[KevinHall]

No kidding! Some things about managed C++ are great. But others are quite annoying -- like the complete lack of generic forms of common programming data structures (generic linked lists, generic vectors, generic maps, etc...). Supposedly Whidbey will include STL.NET, but that will still be template code (and thus not as portable outside managed C++ as generics). <sigh>