Shulou(Shulou.com)06/02 Report--

This article will explain in detail how to use the Visual Studio project conversion function. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

The previous version was developed using VS2003, but now it can no longer meet our needs, so we decided to upgrade to VS2008 in the new version.

These are the main reasons for our upgrade:

VS2003 does not support directly viewing elements in various STL data containers when debugging (in fact, you can view the value of an element through a pointer, but not all elements at once); it does not support parallel construction, with more than 200,000 lines of code, and it takes nearly half an hour to build at a time.

Need to support Vista/Win7 operating system, VS2003 does not support UAC, and can not directly add manifest files

Some other optimizations of VS2008 compared to VS2003

The upgrade process is mainly done by VS2008's conversion wizard. Step by step according to the instructions, you can get the converted solution and engineering documents. Open the new sln and build, change the problem, recompile the old lib and dll files using VS2008, and the built software will run normally and look normal.

But after a while, testers found that the overall performance of the Release version declined significantly, almost 1/2 to 2/3 of the original. As our products are positioned for massive data analysis, performance is crucial. I worked with another developer to analyze the cause of the problem, all the project properties were correct, and I looked at the svn submission record, and everything seemed to be all right. Later, we found that the compiler option of the current project is "* speed / O2" for optimization, but the performance has been improved after changing to "global optimization / Og". Looking at the original vcproj file, it is found that although the "* speed / O2" is set, there is no "/ O2" option on the compiler's command line. Change the compiler optimization option to something else and then change it back to "* speed / O2". You can see that the "/ O2" option has been added to the compiler command line. Rebuilt, performance returned to normal.

The cause of the problem is that VS2008 lost the optimization option after converting the project file of VS2003, but the default option "* speed / O2" is displayed incorrectly in the project property page.

Therefore, the project conversion function provided by VS is unreliable, and it is recommended to check the converted project files thoroughly and carefully. Or simply do not convert, re-create a set of project files, add the original code, and reset the properties of all projects. It's inefficient, but it's the safest.

This is the end of this article on "how to use the Visual Studio project conversion function". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.