[NaCl SDK] Update Visual Studio Addin docs to reflect VS2012 support.

native_client_sdk/src/doc/devguide/devcycle/vs-addin.rst

 .. _devcycle-vs-addin:
 
 ############################
 Debugging with Visual Studio
 ############################
 
 
 .. contents:: Table Of Contents
   :local:
   :backlinks: none
   :depth: 2
 
 Whether you're porting an existing project or starting from scratch, the Native
 Client Visual Studio add-in makes it easier to set up, build, run and debug
 your Native Client app by integrating the Native Client SDK development tools
 into the Visual Studio environment.
 
 .. Note::
   :class: note
 
-  The Native Client add-in requires Visual Studio 2010 with Service Pack 1. No
-  other versions of Visual Studio are currently supported. Visual Studio
-  Express is also not supported.
+  The Native Client add-in requires Visual Studio 2012 or Visual Studio 2010
+  with Service Pack 1. No other versions of Visual Studio are currently
+  supported. Visual Studio Express is also not supported.
 
 Introduction
 ============
 
 The Native Client add-in for Visual Studio helps you develop your application
 more efficiently in many ways:
 
 * Organize and maintain your code as a Visual Studio project.
 * Iteratively write and test your application more easily. Visual Studio
   handles the details of launching a web server to serve your module and run
@@ skipping 112 matching lines @@
 
   Note: The PNaCl platform currently supports the newlib toolchain only.
 
 Installing the add-in
 =====================
 
 In order to use the Native Client Visual Studio add-in, your development
 environment should include:
 
 * A 64-bit version of Windows Vista or Windows 7.
-* Visual Studio 2010 with Service Pack 1.
+* Visual Studio 2012 or Visual Service 2010 with Service Pack 1.
 * `Chrome <https://www.google.com/intl/en/chrome/browser/>`_ version 23 or
   greater. You can choose to develop using the latest `canary
   <https://www.google.com/intl/en/chrome/browser/canary.html>`_ build of
   Chrome, running the canary version side-by-side with (and separately from)
   your regular version of Chrome.
 * :doc:`The Native Client SDK <../../sdk/download>` with the ``pepper_23``
   bundle or greater. The version of Chrome that you use must be equal or
   greater than the version of the SDK bundle.
 
 Set environment variables
@@ skipping 56 matching lines @@
 You can usually run the installer successfully with no arguments. The new
 platforms are installed in ``C:\Program Files
 (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms``.
 
 In some cases system resources may not be in their default locations. You might
 need to use these command line arguments when you run ``install.bat``:
 
 * The MSBuild folder is assumed to be at ``C:\Program Files (x86)\MSBuild``.
   You can specify an alternate path with the flag ``--ms-build-path=<path>``.
   The installer assumes Visual Studio has created a user folder at
-* ``%USERPROFILE%\My Documents\Visual Studio 2010``. You can specify an
-  alternate path with the flag ``--vsuser-path=path``.
+* The addin itself is normally installed in ``%USERPROFILE%\My Documents\Visual
+  Studio 2012`` (or 2010 for Visual Studio 2010). You can specify alternate
+  paths with the ``--vsuser-path=<path>`` flag.
 
 From time to time an update to the Visual Studio add-in may become available.
 Updates are performed just like an installation. Download the new add-in using
 naclsdk update and run ``install.bat`` as administrator.
 
 To uninstall the add-in, run ``install.bat`` as administrator and add the
 ``--uninstall`` flag. You'll need to run the Command Prompt program as
 administrator in order to add the flag. Go the to the Windows start menu,
 search for "Command Prompt," right click on the program and run it as
 administrator.
@@ skipping 353 matching lines @@
   functional code that is running is the same as STEP5.
 
 NaCl64 Platform
 ^^^^^^^^^^^^^^^
 
 Run the Native Client Module in the NaCl64 platform
   You are still running the STEP6 code, but as a Native Client module rather
   than a Pepper plugin.
 
 .. TODO(sbc): port reference section?