After nearly two years using VB.NET, I'm now working for a company
that has a very large commercial ASP/COM+ application (1 million+
lines of VB6 code, 350+ objects in the COM+ catalog, 2300+ classes).
The corporate decision has been made to "port" this monster over to
..NET (C#/VB.NET). My inquiry is to discover some of the major issues
that might be raised in the course of this endeavor (I've reviewed
most of the Microsoft documentation on projects of this type).
I've convinced some (but not all) managers that it is not just a
question of what percentage of code "can" be translated successfully
to .NET, but how much code "should" be translated. In other words,
given the major benefits that the .NET model offers, new code should
be written to take advantage of these benefits -- even if this means a
major (or complete) rewrite.
Any tips/experiences/advice from senior programmers who have worked on
very large projects like this will be welcome. Please, no company or
product names.
AllenL