You definitely have some work cut out for you, but here is a strategy to consider before doing ANY .NET work.
Extract as much of the base FORM code as possible into the class: one class file for each form at the beginning. In fact, form event handlers should do nothing but proxy method calls in an instance of the base class; it is obvious that all user methods can be transferred to the class file.
After reading the best practice guide (etc.) from Microsoft and others to help you get ready for the .NET port, you are mostly tuned to small pieces of hell that you will have to transcode / refactor: annoyances such as error handling, event ordering, late related objects / options, collections, etc.
Word for error-processed code: it is especially difficult to duplicate spaghetti errors, especially because the average Visual Basic encoder had poor ability to use it as a flow control logic. It is almost worth breaking each On Error block into separate subroutines if there are more than two .
After clearing the code, you can also consider refactoring Visual Basic code into reasonable abstractions (e.g., one data adapter class and connection, etc.), but you will be the best judge of this.
You may not like this approach, so definitely check out one form of water.
hythlodayr
source share