In our company, we are developing and selling the VB6 application, and we think that the time for its transfer to .Net.
Main reasons:
- We expect VB6 runtime support to end at some point in time, and we don’t want to start the migration just then, as it is likely to be a lengthy process.
- Only 1 1/2 of the VB6 developers are left. First half of me.
- More and more customers are requesting features such as support for cloud and mobile devices.
I know that rewriting an application from scratch is the least recommended way to migrate to .Net. I totally agree with that! Emissions over a decade of code seem simply wrong and will be such a waste of money that it’s hard for me to recommend and justify it in relation to our management.
But right now I see no other way to do this.
Let me tell you a little about the application:
As I said, it's been over a decade. Many developers worked on it, most of which were rather inexperienced at that time. We have one developer left over from the initial team. This app was his first and largest software project, and now he realizes that many of the architectural decisions made over the past 15 years were terribly wrong, others were right at the time, but were not reorganized to fit the changes made to other parts of the application and therefore became erroneous at a certain point in time. This app is a demo of a code gene.
150 KSLOC, . 15 DLL, - ActiveX, - .Net.
- , .Net. , . , , , . , .
, , /, , Artinsoft/Microsoft/WhoEver, , .Net.
:
- , . , . , , .
- .Net : , . , , - .
- , , - , . , , . , , , .Net , , , , , .
. , , , , .
? ?