CodePudding user response:
I come now, everyone use VS2008 in a project to do then, later, I changed, you can use VS2017 code generation, this should see yourself how to deal withCodePudding user response:
Vs can be backward compatibility, not meet high version can't open the low version of the situationCodePudding user response:
If use the third-party components, upgrade vs very troublesome, have a problem to solve a problem, in,CodePudding user response:
High version automatically transformation projectsCodePudding user response:
There are too many people in project maintenance upgrade version must be highCodePudding user response:
C + + project may trouble points, the.net project is not matter,CodePudding user response:
New company, according to my new sex, cannot upgrade to the latest is rubbish, otherwise, mathematics and code how to progress, is abandoned directly, write again!CodePudding user response:
Don't blindly upgrade production code, especially if you don't know the code also, prefer to find a computer to install a vs2008 make do withCodePudding user response:
In fact high version VS all normal can open the low version of the solution is no problem.You normally open the SLNS. Detected it will prompt you to upgrade what so-called upgrade does not change the version number of the config... Other unscathed...
If you be afraid influence directly open the project csploj file will do...
CodePudding user response:
Can't endure, must be at least 2010CodePudding user response:
Visual Studio 2010 applicable highlight plug-inCodePudding user response:
Low versus high version, and then install version of the compiler will do ah, as long as the project file don't upgrade, do not have what problem, but still suggest to discuss unification upgrade, lower version of VS really bad to use, after use habits high version don't understand why anyone has been willing to stay on the lower version of VSCodePudding user response:
Use the git or SVN version management tools, such asThen generate new csproj and SLNS files detected, do not cover the original project files,
CodePudding user response:
In general, I met the old version of the project, is to write directlyCodePudding user response:
1. Build git or SVN warehouse, make the regret medicine, copy to assemble a.2. With high version vs, according to the prompt to upgrade.
3. Check the update report, if there is any mistake, modify them one by one, are usually better change.
CodePudding user response:
Had the meeting this morning the director said in time on the new business in upgrade now do writeAny old programmer to recommend some VS2008 optimization plugin resharper found a compatible version of the 08