Transitioning the source to VS 2012 and Windows 8

Topics: ASP.NET MVC, ASP.NET Web API, ASP.NET Web Pages, General
Sep 5, 2012 at 11:42 PM
Edited Sep 5, 2012 at 11:43 PM

Part of moving our sources over for v.Next includes dependencies on Visual Studio 2012 and Windows 8 (or Windows Server 2012). We took the first step today (porting our FxCop rules to VS 2012), and soon we will require Windows 8 (or Server 2012) so that we will be regularly building our Windows 8 version of System.Net.Http.Formatting.

Pulling the source today, you may find that you are unable to do command line builds with only VS 2010 installed, especially if you are using a version of VS 2010 that includes FxCop. The solution is to install VS 2012 on the machine in question. If you need to continue to build using only VS 2010, you can disable FxCop by passing parameters to the command line build:

build UnitTest /p:CodeAnalysis=false

Also, you may need to re-run "build restorepackages" to get the new v11 version of our custom FxCop rules.

Sep 7, 2012 at 7:21 AM

Can we consider adding a nice command-line switch to allow you to continue to use VS 2012 on a Win7 box?

Sep 8, 2012 at 1:20 AM

From Visual Studio, you will get an "unsupported project" warning for the Win8 project. From the command line, though, there's no way to do that without keeping multiple solutions, which we really don't want to do.

Sep 15, 2012 at 8:46 PM

That's too bad. I don't want to install Windows 8. I can't stand that Metro start screen.