Visual Studio 2013 Update 3 RTM Available

Visual Studio 2013 Update 3 RTM Available

Rate This
  • Comments 21

Today we released Update 3 for Visual Studio 2013 (you can read more on Brian Harry’s blog and Soma’s blog). To upgrade you can either download the update or install a full version of Visual Studio 2013 with Update 3 already installed from these links:

In addition to new features, this update also offers reliability fixes and bug fixes, including:

  • CodeLens. CodeLens is an editor productivity feature available in Visual Studio Ultimate; with this update, CodeLens can show authors and changes to files that are in Git repositories. If you use Git for source control and TFS for work item tracking, CodeLens work item indicators now provide information about work items associated with a method or class.
  • Code Map. Code maps help you avoid getting lost in large code bases, unfamiliar code, or legacy code by visualizing relationships among multiple pieces of code. This update adds colors to links on code maps to make it easier for you to navigate. You can also drag and drop binaries from File Explorer into a directed graph in Visual Studio to immediately start exploring the code. Check out MSDN for how to map dependencies in specific code using code maps in Visual Studio.


Managed Memory dump analysis

  • CPU and Memory Usage tool. The CPU Usage tool in the Performance and Diagnostics hub now enables you to navigate from a function name in the Call Tree to the definition of that function in the editor so that you can easily see the code that is using CPU in your application. We have also made improvements to the Memory Usage tool such as support for Win32 and WPF applications (.NET 4.0 and up on Windows 8.1) and the ability to force garbage collections in managed apps.

CPU Usage Tool

  • Notification Hub. When we release a Visual Studio Update for you to download, the Notifications badge will turn yellow (in the upper right hand corner of the IDE). The badge also now acts as a toggle so you can easily use one click to open the hub and one click to close the hub.
  • ALL CAPS. The change in our menus to use all capital letters was one of the areas about which we received a lot of feedback so a while ago we added a registry key that disabled the ALL CAPS menus in VS 2012. To make the setting more discoverable and to enable it to remain set as you upgrade across Visual Studio versions, we have now added a Tools Options setting under the General Environment settings that lets you set your preferred menu bar styling. We also roam this setting so it’s available on all your devices
  • Testing. This update includes many updates to test capabilities in Visual Studio. Top features include the ability to customize test plans and test suites, ability to use work item history to track changes made to test suits and the owner of the changes, enhanced security for test suites, and cloud based load testing capabilities with application insights for monitoring performance.
  • Release Management. To better manage the release of your applications you can now deploy your app to an on-premises environment or a Windows Azure environment without having to set up a Microsoft Deployment Agent on each machine. You can use Windows PowerShell, or Windows PowerShell Desired State Configuration (DSC). You can also deploy to servers that are not running a Windows operating system when you use Chef. For more information, see Manage your release.
  • Visual Studio Graphics Analyzer. Diagnosing DirectX rendering and performance issues is tricky and the Visual Studio Graphics Diagnostics tools help. In Update 3, we have enhanced the Graphics Analyzer to analyze graphics frames and to view the impact of shader code changes without re-running the app. You can easily configure capture options in Tools Options under Graphics Diagnostics.
  • WebJobs Tooling. We have added support for Microsoft’s Azure WebJobs in Update 3. You can now create standard Console Projects in Visual Studio solutions that can be published to Azure Websites as either continuous, triggered, or scheduled WebJobs. We have also added support for two-factor authentication in One ASP.NET templates for MVC, Web Forms support, and enabled creation of ASP.Net projects using WAAD when signing in with Live Id. Checkout this Channel 9 video to learn more.
  • Application Insights. Application Insights, Microsoft’s service for monitoring production web sites and Windows Store apps, is included in this update. We have improved the account setup experience so accounts can be setup in Azure without requiring a Visual Studio Online account.

You can learn more about the full list of new Update 3 features in the release notes and bug fixes in the KB article.

Other important releases

I also want to highlight some related releases announced recently that provide additional features and functionality for Update 3 users. These releases are all compatible with Update 3 and in some cases are required for Update 3.

  • Multi-Device Hybrid Apps. You can use the Multi-Device Hybrid Apps CTP 2.0 release to build mobile apps using JavaScript or Typescript for iOS, Android, Windows Store, and Windows Phone using Update 3’s version of tooling for Apache Cordova. To learn more check out Multi-Device Hybrid apps. Visual Studio 2013 Update 3 is not compatible with CTP 1.0 & 1.1 for Multi-Device Hybrid apps. (Minimum edition required: Professional).
  • Azure SDK 2.4 RTM. The recent Azure SDK 2.4 RTM release includes tools to manage virtual machine configuration and set up remote debugging for 32-bit virtual machines, and tools to provision Geo-Redundant Storage. You can download Windows Azure SDK for 2013, Windows Azure SDK for 2012, and Windows Azure SDK for .NET.
  • IntelliTrace Stand-alone Collector. The standalone IntelliTrace collector provides a more practical alternative to remote debugging an application in production. You can use the collector to record the execution of your application on a remote machine by saving it into an .itrace file and playing it back on your local development machine with Visual Studio. For more information about the collector, see this MSDN article.
  • Windows Phone 8.1 Update Emulators. Windows Phone 8.1 Update was released this morning and is ready to download. This release provides additional emulator images to Visual Studio 2013 Update 2 or later that can be used to create and test apps that will run on devices that have Windows Phone 8.1 Update.
  • Visual Studio Tools for Unity. As we mentioned earlier this week, the Visual Studio Tools for Unity (formerly UnityVS) are available for download, free for Visual Studio Professional and higher.

Many of the features and bug fixes in this release come from your feedback. Thank you for sharing these suggestions with us on our UserVoice site and through the thousands of Send-a-Smile and Send-a-Frown actions you sent us from inside the IDE. If you find a bug please send it to us the Visual Studio Connect site.


John Montgomery, Director of Program Management, Visual Studio Platform

John has been at Microsoft for 15 years, working in developer technologies the whole time. Most recently before working on the Visual Studio core development environment, he was working on the tools for Windows 8 development

Leave a Comment
  • Please add 3 and 6 and type the answer here:
  • Post
  • The "Install Now" download link is broken:

    It wants to download "VS2013.2.exe", which doesn't look like update 3 to me!

  • @Richard Deeming

    You're right -- we're fixing that. You can go to the download center and use that directly in the meantime:


  • fix first then output notice of release


  • Still confused/ing with both .2 and .3 in the same section

    •On this page, choose the Download button.

    •Select the .exe option and then choose the Next button.

    •Choose the Save button.

    •Once the download is complete, open a command prompt, navigate to the download location, and run VS2013.2.exe /layout.  <----------- .2

    •Specify where to download the files and click the Download button.

    •Once downloaded, you can run VS2013.3.exe from the download location to install the update.

  • The rtools (at least the x86 which I just did, and DL'ed again just now) shows its as update 2 in the install dialog, and as you can see the filesizes are still the same.  What's the story on this one?

    Directory of E:\downloads_E\vs2013_upd3_rtools

    2014.08.04  15:45        61,029,000 rtools_setup_x86.exe

    2014.08.04  15:46        25,607,032 rtools_setup_arm.exe

    2014.08.04  15:46        86,118,760 rtools_setup_x64.exe

    2014.08.04  16:31        61,029,000 xrtools_setup_x86.exe just now

                  4 File(s)    233,783,792 bytes

                  2 Dir(s)  377,091,477,504 bytes free

    Directory of E:\downloads_E\vs2013_upd2_rtools

    2014.05.13  05:04        25,607,032 rtools_setup_arm.exe

    2014.05.13  05:06        61,029,000 rtools_setup_x86.exe

    2014.05.13  05:06        86,118,760 rtools_setup_x64.exe

  • @idea man *

    Looks like a link propagation problem. Try the link on the Download Center:


  • When is the proper XNA support coming?

    Thank you.

  • @John Montgomery,

    Please add SSH, SCP and SFTP support in Windows via PowerShell/CommandPrompt. This means no disrespect to Microsoft's remoting solutions but in full honesty those protocols are far more famous in the world.

    You guys can implement those protocols and win hearts of millions worldwide using Windows and dealing with Linux servers in their day jobs.

    Installing Cygwin, WinSCP, Putty or Mingw etc. is far more annoying solution for those simple straight-forward protocols. Built-in support for those three protocols will "ONLY" reflect goodness and shows that Microsoft cares for all sorts of consumer scenarios.

    As a treat, you can also add support for those and FTP in File Explorer, so we can hook and use our remote storage via Add Network Drive.

    Thank you in advance for reconsidering this decades old stubborn decision and doing the right thing finally.

    - P. Finney

  • VS guys please read this:

    This is "THE" example of VS issue, which needs immediate attention and VS team should work with all the project system teams and unify them to abide by some mandatory interface.

    Ignoring this will eventually fend away people from VS. Improving those aspects of VS extensibility interfaces will bring more useful stuff to VS world.

    Please do right by automation guys and we will deliver must better solutions to your world than what your competitors have to offer. We are getting better in discovering stuff (since there is no documentation). We have done a lot the hard-way. Would be a treat, if only this time you guys also care to do some documentation and help material on universal new interface for automation and extensions.



          _ ___.--'''`--''// ,-_ `-.

      \`"' ' |  \  \ \\/ / // / ,-  `,_

     /'`  \   |  Y  | \|/ / // / -.,__ `-.

    /<"\    \ \  |  | ||/ // | \/    |`-._`-._

    /  _.-.  .-\,___|  _-| / \ \/|_/  |    `-._

    `-'  f/ |       / __/ \__  / |__/ |

        `-'       |  -| -|\__ \  |-' |

               __/   /__,-'    ),'  |'

              ((__.-'((____..-' \__,'

  • @Peterous

    What does SSH, SFTP and SCP command line support in the Windows OS have to do with Visual Studio?

  • Sorry I am not a developer so I don't know. I better stfu then?

    On second thought, how about: VS > File > Open > Website  and tadah! we gotta SFTP right there out-of-the-box!

    So basically having this little sftp.exe (with helpers: scp.exe and ssh.exe) in Windows will benefit: VS, DotNet, PS, CMD, FileExplorer, vagrant, git and hundred other third-party apps for DEVELOPERS!!!

    Question: Is VS related to various kind of heterogeneous development scenarios?

    Answer: Yes!

    Question: Does it makes sense that VS team build those three utilities (for fallback purposes: Win7,8) and also give it away to Windows team so they can add to Windows vNext (perhaps 9) ?

    Answer: Yes!

    Question: Should I take back my previous comment?

    Answer: Yes!

    Apologies for the nonsense nuisance.

  • The release notes incorrectly claim the new C++ compiler switch for enabling rich debug information for optimized builds is /Z0 (zero) when it is in fact /Zo (lowercase o).

  • another so what release poorly done,

    check this out if you even give a crap , anymore

  • After install the Update 3, my mvc3 project razor view @model not longer strongly typed any more. It's too bad!

  • vs2013 update3  stop...

    in windows8.1 x64

Page 1 of 2 (21 items) 12