I have VB6 project with about 150,000 code lines that controls sophisticated automatic/manual calibration system. The system hardware was recently updated and some of the hardware drivers does not support any more VB6 32 bit applications.
The whole calibration software package include 22 applications including 3 data acquisition programs, data bases applications and data reduction and analysis applications. I designed the system and wrote all the code.
I consider now to rewrite the one problematic data acquisition calibration program in VB.net 2022 to solve the 32 bit issue.
This program has about 80,000 lines of code and use about 100 routines located in the project main library. These routines are also used in the other applications. Obviously, each library routine include several related procedures (subs and functions).
As I understand, in VB.net solution, to keep this structure, each library routine, saved in the library folder, must be "project" since other approach merge the classes and/or modules to the "master" project folder. So, I have to convert the 100 library routines to 100 projects. Am I right?
Where can I find some explanations and recommendation how to approach to this project. Some detailed template how to call routines and variables between tens of projects in one solution will be very helpful as well.
Thanks.