Microsoft’s new .Net environment is the new domain that software-oriented companies are looking towards courtesy, the end of VB6 support. In fact, with the unpredictable nature of the present market in mind, several companies are jostling hard to slash costs and restructure their application development procedures. Research shows that various tactics, strategies and methods have been employed by some companies to accomplish the even course of migration from old to new.
Following are some helpful tips regarding the strategy of the migration:
While making transition of projects from any previous version of Visual Basic, the course for analysis and design ensures the best results. A bit different from the rest who suggest you to convert your current apps to .NET and fix the changed code in .NET, here, you need to start by studying the present application and trying to spot code blocks, which possibly require some changes.
Even if your developers are experienced for six months in handling the .NET, it can be well surmised that they might have spent more development time on your current applications. They would probably be more at ease making alterations in your present application than the migrated version. However, you can make changes in your current applications and push them to a point, which we term as “Migration Ready”.
Below are the steps, which you can follow for migrating applications:
If more alterations are required, make them accordingly using Migration tool (Repeat the second and third steps as and when necessary)
The implementation of initial proof-of-concept marks the beginning of the migration path. This will help you estimate the resources, the time and the cost as well to migrate the project. You will do well to extract at least a single complex working procedure of the application and construct it into a small working solution. Eventually the process of migration follows.
