by Rob
15. September 2012 11:16
I've been slowly migrating to using VS2012 as my primary development environment and I love the fact that it can open projects created in 2010 with no conversion required. It is however, not flawless as I found when trying to build a project with code contracts and code analysis enabled. The build fails with warnings from code analysis like so;
The problem is that VS2010 puts an absolute path into the project file for the code analysis rule files (bug?) and this causes 2012 to attempt to load the 2010 versions and subsequently fail.
This appears to be reasonably well documented on the internet and a post on this problem with a fix is available here. The author claims the fix will last as long as you don't add any new configurations but in my experience I've seen the issue magically come back after the customer subsequently worked on the project with VS2010 and added no new configurations.