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

native_client_sdk/doc_generated/devguide/devcycle/vs-addin.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="debugging-with-visual-studio">
 <span id="devcycle-vs-addin"></span><h1 id="debugging-with-visual-studio"><span id="devcycle-vs-addin"></span>Debugging with Visual Studio</h1>
 <div class="contents local" id="table-of-contents" style="display: none">
 <p class="topic-title first">Table Of Contents</p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#introduction" id="id1">Introduction</a></li>
 <li><p class="first"><a class="reference internal" href="#platforms" id="id2">Platforms</a></p>
 <ul class="small-gap">
@@ skipping 30 matching lines @@
 <li><a class="reference internal" href="#porting-windows-applications-to-native-client-in-visual-studio" id="id24">Porting Windows applications to Native Client in Visual Studio</a></li>
 </ul>
 </li>
 </ul>
 
 </div><p>Whether you&#8217;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.</p>
 <aside 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.
 </aside>
 <h2 id="introduction">Introduction</h2>
 <p>The Native Client add-in for Visual Studio helps you develop your application
 more efficiently in many ways:</p>
 <ul class="small-gap">
 <li>Organize and maintain your code as a Visual Studio project.</li>
 <li>Iteratively write and test your application more easily. Visual Studio
 handles the details of launching a web server to serve your module and run
 the module in Chrome with a debugger attached.</li>
 <li>Compile your module into a dynamically-linked library (DLL) using Visual
@@ skipping 80 matching lines @@
 Native Client SDK to transform the .pexe file into a NaCl64 .nexe file and runs
 it as if you were working with a NaCl64 platform.</p>
 <aside class="note">
 Note: The PNaCl platform currently supports the newlib toolchain only.
 </aside>
 <h2 id="installing-the-add-in">Installing the add-in</h2>
 <p>In order to use the Native Client Visual Studio add-in, your development
 environment should include:</p>
 <ul class="small-gap">
 <li>A 64-bit version of Windows Vista or Windows 7.</li>
-<li>Visual Studio 2010 with Service Pack 1.</li>
+<li>Visual Studio 2012 or Visual Service 2010 with Service Pack 1.</li>
 <li><a class="reference external" href="https://www.google.com/intl/en/chrome/browser/">Chrome</a> version 23 or
 greater. You can choose to develop using the latest <a class="reference external" href="https://www.google.com/intl/en/chrome/browser/canary.html">canary</a> build of
 Chrome, running the canary version side-by-side with (and separately from)
 your regular version of Chrome.</li>
 <li><a class="reference internal" href="/native-client/sdk/download.html"><em>The Native Client SDK</em></a> with the <code>pepper_23</code>
 bundle or greater. The version of Chrome that you use must be equal or
 greater than the version of the SDK bundle.</li>
 </ul>
 <h3 id="set-environment-variables">Set environment variables</h3>
 <p>Before you run the installer you must define two Windows environment variables.
@@ skipping 47 matching lines @@
 the installer again later to add the PPAPI platform.</p>
 <p>You can usually run the installer successfully with no arguments. The new
 platforms are installed in <code>C:\Program Files
 (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms</code>.</p>
 <p>In some cases system resources may not be in their default locations. You might
 need to use these command line arguments when you run <code>install.bat</code>:</p>
 <ul class="small-gap">
 <li>The MSBuild folder is assumed to be at <code>C:\Program Files (x86)\MSBuild</code>.
 You can specify an alternate path with the flag <code>--ms-build-path=&lt;path&gt;</code>.
 The installer assumes Visual Studio has created a user folder at</li>
-<li><code>%USERPROFILE%\My Documents\Visual Studio 2010</code>. You can specify an
-alternate path with the flag <code>--vsuser-path=path</code>.</li>
+<li>The addin itself is normally installed in <code>%USERPROFILE%\My Documents\Visual
+Studio 2012</code> (or 2010 for Visual Studio 2010). You can specify alternate
+paths with the <code>--vsuser-path=&lt;path&gt;</code> flag.</li>
 </ul>
 <p>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 <code>install.bat</code> as administrator.</p>
 <p>To uninstall the add-in, run <code>install.bat</code> as administrator and add the
 <code>--uninstall</code> flag. You&#8217;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 &#8220;Command Prompt,&#8221; right click on the program and run it as
 administrator.</p>
 <p>You can verify that the add-in has been installed and determine its version by
@@ skipping 273 matching lines @@
 </dl>
 <h4 id="nacl64-platform">NaCl64 Platform</h4>
 <dl class="docutils">
 <dt>Run the Native Client Module in the NaCl64 platform</dt>
 <dd>You are still running the STEP6 code, but as a Native Client module rather
 than a Pepper plugin.</dd>
 </dl>
 </section>
 
 {{/partials.standard_nacl_article}}