I'll make a few quick comments on some of your questions --
This is something to look at on a project-by-project basis. I'd suggest looking at converting C++ projects to Managed C++ rather than going to C#. If you convert them to Managed C++, then you can link the pieces with C# going forward. (see yourQuote:
Originally Posted by John E
The executables and DLLs created within .NET are actually composed of Intermediate Language code (IL/MSIL). This code is completely compatible and thus, you can mix classes from VB with those of C# or Managed C++. You can even go as far as inheriting classes from one language using another.Quote:
Originally Posted by John E
There are definitely tools to convert VB 6 to VB.NET or C#. There are also tools to convert from C# to VB.NET and back. I've not seen tools to go from C++ to C# or VB.NET, but then I've not looked.Quote:
Originally Posted by John E
Brad!