Microsoft discloses Visual Studio 2013 pricing, rollout plans

Microsoft discloses Visual Studio 2013 pricing, rollout plans

Summary: Microsoft will be rolling out its latest Visual Studio development-tool suite starting in mid-October. Pricing will remain in line with that of the current VS 2012 suite.


Microsoft plans to hold the line with pricing for the latest version of Visual Studio, officials disclosed this week.


Visual Studio 2013 prices are unchanged from the corresponding Visual Studio 2012 products, according to Microsoft execs. Those who get access to Visual Studio via their MSDN subscriptions won't have to pay anything to move to the latest version when it becomes generally available on October 18, officials added. (The "vast majority" of Visual Studio customers get their VS releases through their MSDN subscriptions, company officials say.)

There will be one change in the SKU line-up between Visual Studio 2012 and 2013. Microsoft will be reintroducing a Visual Studio Professional 2013 Upgrade SKU for customers running Visual Studio 2012 Professional. For a limited time (November 1, 2013 through January 31, 2014), those interested in the VS Professional 2013 Upgrade SKU can get it for $99 from the Microsoft Online Store. After that time, the price will be $299.

Current Visual Studio 2012 prices include:

  • Visual Studio 2012 Professional: $499
  • Visual Studio 2012 Professional with MSDN: $799
  • Visual Studio 2012 Premium with MSDN: $2,569
  • Visual Studio 2012 Ultimate with MSDN: $4,249

Update (November 14): As a few readers have noted, the prices above are the “renewal” prices only, and not the full prices for new customers who are buying Visual Studio for the first time. Those prices are higher. Here are the prices for first-time VS purchasers.

Microsoft made the Visual Studio 2013 release candidate available for download in September. The Visual Studio 2013 launch event is November 13, but MSDN subscribers will get access to the Visual Studio 2013 RTM bits on October 18, which is Windows 8.1's general availability date. Visual Studio 2013 with MSDN will be available through volume licensing on November 1, and from retail resellers "soon after," according to Microsoft's VS 2013 pricing page.

Visual Studio 2013 -- and Net 4.5.1 -- add support for asynchronous debugging (when using VS 2013 on Windows 8.1, not older Windows releases) for C#, VB, JavaScript and C++ developers, among other features. The latest VS release also adds improvements for those using XAML, HTML and JavaScript to build Windows Store/Metro-Style apps. Microsoft made an initial public preview of Visual Studio 2013 available in late June of this year.

Topics: Software Development, Microsoft, Windows 8


Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Buying from "On-line" store

    If you purchase something from the Online store, are you able to re-download it at a later time?
    A Gray
    • re:

      If you have MSDN, you can download and install the things your subscription level has access to as long as your subscription is valid.
      Sir Name
    • ...good question

      ...and I wonder if you can actually burn it to disk for future installs. $99 sounds too good to miss!
      • most are ISO's

        Most of the MSDN downloads are ISO's so you can burn them to a disk. In fact, unless you use a program to mount ISO's as virtual disks you *need* to burn them.
        • Other Options

          You can use 7-zip or similar to unzip the contents.

          Another option in Windows 8 you can just mount the ISO and install from the virtual drive.
  • I have been spoiled

    Never actually paid for a Visual Studio license since every company I have worked for uses enterprise licensing. I tried a few of the "Free" open source dev tools over the years and I keep coming back to Visual Studio. It is one of the best development tools to learn and use. The Team Foundation System integration makes working with source code in a team very easy. I think Visual Studio, much like Microsoft Office, is a flagship product.
    Sean Foley
    • visual studio was always nice

      but the world outside of windows-only technologies is sooo much more interesting. Hey if that's what you do - .NET, etc, then that's what you need.
      • Interesting?

        The world outside of Windows only technologies is in a word HORRIFIC. The tools suck, the platforms suck, the pace of innovation sucks. One only has to look at how antiquated the bucket of puke known as Java is to know how bad things are. Seriously, they're not even trying anymore.
        • Sounds like the only thing you have looked at is Java.

          I think DrWong was talking about more than just Windows tools.
          But hey, its your choice to bury your head in MS ..., er, I mean sand.

          But then again, let's look at MS: The tools suck, the platform sucks, the pace of innovation sucks. One only has to look at how antiquated the bucket of puke known as Win8. Seriously, they're not even trying anymore.
          • So...

            What platform IDE is better? Seriously?

            Have you even ever developed in VS?

            It's easy to bash something, but if you really are trying prove a point give an alternative instead of usual BS anti-MS rhetoric.
          • What are you comparing it to?

            So, what exactly are you comparing Microsoft to when you say everything sucks? Have you ever actually used the Microsoft development ecosystem? Or are you just an ideologue?

            VS is actually amazing to use. Unless you can actually explain what you think is better about something else, then I'll assume you've never used it.
        • And JackBond predicted Silverlight was never get axed... ;)

          Small world Jack. VS 2012 UI is horrible, when the Win8 team saw what the VS team did they were in shock. VS 2012 Ultimate frequently just stops working for me (I do Silverlight and .NET WCF and Windows forms development) ... or it will go produce error messages that aren't real or valid where it requires me to shutdown VS and restart and viola, error message magically disappears.

          Or how about when VS decides there is a problem with some XAML an goes into "slow motion typing mode at 1 letter per 4 seconds" usually in my APP.XAML because VS gets "confused" (a parser problem that has been around since VS 2010 in which is a verified bug but MS will not fix because the code is too complex).

          Or how about the lovely "Unknown" error VS 2012 return on a Web Service call ... so incredibly helpful!! Which actually could mean anything, but in my case I was able to track it down to a value that was defined in an enum.

          Or how about parts of VS 2012 that only work if you are running Win8 ... for those of us that have ZERO interest in building/deploying anything for Win8 (and why should we when Win8 has only gained 7% market over a year later) and work on Win7?

          And why exactly did Microsoft kill Silverlight in favor of HTML5? Does Microsoft honestly think they can just change technologies every 3 months and developers will immediately migrate to the next "new" technology that will soon fail and be dropped again?

          Come on Jack, explain your very bizarre love for Microsoft's development tools? Do you even have an ADC account with Apple? Have you ever code for anything other than Microsoft? So why is your nose so firmly up Microsoft's bung hole? Do they employ you to make false statements about VS?
          Rob Ainscough
          • Why do you need that

            ADC for Apple? Most every single corporation I work for uses Microsoft for their infrastructure support.
          • Unknown error on a web service

            If it's your web service your error handing is no good.

            "And why exactly did Microsoft kill Silverlight in favor of HTML5"

            It kills me that anti-ms people love to rave about this. Microsoft is abandoning a proprietary technology for an open one. Isn't that what you wanted from MS?
        • Agreed

          An MSDN subscription is the best thing in the world for developers. Not only do you get Visual Studio; you also get all the server and workstation operating systems, SQL Server and a whole lot more. I'd be screwed without it: it's about the only thing I renew religiously every year. Say what you like about free, open-source stuff, but ultimately you get what you pay for. And Microsoft's development environment is, as has been pointed out by various posts here, years ahead of anything else.
      • Of course

        This is why that interesting world is trying to copy stuff from Microsoft.
        • Care to name some copied MS stuff?

          I would be happy to correct you with true origins of whatever you name.
          • Oh I don't know...

            1.) LINQ
            2.) Entity Framework
            3.) C# Auto-Properties
            4.) Unified single-root type system
            5.) Auto-boxing (yes, Java has it now too, but YEARS after C#)
            6.) IEnumerables/yield-return/delayed execution
            7.) C# await
            8.) C# dynamic typing
            9.) C# unsafe code for performance sensitive loops
            10.) Deterministic disposal with using keyword (yes, Java has it now too, but it is much more clunky)

            1.) Table-Valued Parameters
            2.) Merge statement
            Cody Yancey
      • I do mostly fortran

        and C hpc development and I almost exclusively use visual studio (except final runs that are currently done on a Red Hat machine). I used eclipse first, but moved on to visual studio (2012 now), and haven't look bad. Foe me theres just no IDE that even compares to visual studio.
        Sam Wagner
        • Too expensive BTW

          Very nice endeed but you have to pay to much royalties for technologies that work only in a MS environment like, etc. So in a open world, buying VS doesn't make sense.