All geek questions in one place

What is the best approach when porting legacy projects to visual studio versions?

I was thinking about the number of projects that we have in the house that are still being developed using visual studio 6 and how best to port them to Visual Studio 2008. Projects vary depending on C / C ++ and VB.

Is it better to let VS2008 transform workspaces into solutions, fix any compilation errors and be on your fun journey? Or is it better to start with a clean solution and transfer the code to the project by project, discarding dead code along the way?

+4
source share
2 answers

The Microsoft p & p team has recommended some strategies that respond to this. Basically they recommend something like a project project for the project you mention. Of course, they accept a neatly encrypted application that has no unpleasant dark corners, of which late coding nights and a plentiful amount of spring coffee are off.

It doesn’t hurt VS2008 to convert the project for you and see how much effort is required to fix the errors.

+3
source

When I had to convert a VB6 application to VS2003 a few years ago, I started the converter and it created something that basically compiled, but was not very good at all. I had to change a large piece of the code that it generated.

I would start with a clean solution, then run the converter in the project and copy only the code that you need. One of the big differences that I noticed between the VB6 project and the converted VB.NET project (WinForm) was with built-in controls. The converter will try to keep the type of controls you use, even if they were old and obsolete. That way, you might be better off creating new forms using modern controls (text boxes, tab controls, etc.), and then copy the code you need.

+2
source

Source: https://habr.com/ru/post/1276639/

More articles:


All Articles