Making such a change increases the likelihood of a project failing, even if necessary. I would say if it is not broken, do not correct it. Although itβs good to work with the latest tools, changing the tool to change the tool in the current size project is usually too risky. It would be better to wait until you reach the delivery line, release the product, and then devote a development cycle, possibly short, to update the tool.
With that said, as a rule, VS2010 for VS2012 is much smoother than VS2008 before VS2010. The only problems that I encountered were to cut out some links that were not correctly ported to some projects and difficulties associated with the old version of the TFS server (the transition to a newer server was fixed by this).
I had VS2010 and VS2012 on several systems (along with VS2005 and VS2008 in some cases) without problems.
source share