The official source of product insight from the Visual Studio Engineering Team
Visual Studio 2013 is now available for download! We hope you are as delighted with this release as we are to bring it to you. You can learn more about what's new in Visual Studio 2013 on the Visual Studio website. Also mark your calendars to join us for the Visual Studio 2013 virtual launch event on November 13th!
If you haven’t tried out Visual Studio 2013 Preview or RC, when you first launch Visual Studio 2013 you’ll be invited to sign in to Visual Studio with a Microsoft Account.
When you sign in with your Microsoft account, Visual Studio will remember your top settings and automatically synchronize them across devices ensuring Visual Studio is set up to exactly how you like it! You can learn more about this feature from our previous Synchronized Settings blog post or from MSDN.
Signing in has other advantages in addition to synchronizing your settings across devices. As an MSDN subscriber, signing in will automatically unlock the IDE without needing to enter a product key. Signing in to Visual Studio Professional, Premium and Ultimate can extend a trial, and Visual Studio Express users can sign in once to fully unlock their IDE. In addition, when you sign in, Team Explorer can now prepopulate all your Team Foundation Service accounts automatically in the Connect to Team Foundation Server dialog and connect to them without re-prompting for credentials. Check out Signing in to Visual Studio to learn more about the capabilities that get lit up when you sign into Visual Studio.
Please note that you can still unlock Visual Studio Professional, Premium and Ultimate with a product key. However, features that need a signed in user, like Synchronized Settings won’t be available.
For information on Windows 8.1, which was released today the general public, please check out Blogging Windows. MSDN subscribers can also download both Visual Studio 2013 and Windows 8.1 from the Subscribers Download page.
Download Visual Studio 2013 to try out the new features. To help get started, check out system requirements and platform compatibility as well as the Productivity Tips on MSDN. Finally, to gain more insight into Visual Studio 2013, read additional posts in the Developer Tools blog network from the people who contributed to this release.
Thank you for all the feedback thus far that has helped shape Visual Studio 2013. We look forward to hearing from your feedback / ideas so please add your suggestions to UserVoice or vote up an existing suggestion. Use Connect to log bugs, and Forums for Q&A. You can also contact Product Support for any issues in production.
The Visual Studio Team
We’ve listened to the feedback from the community, and released an updated installer to get Visual Studio 2013 on machines with older versions of IE. Visual Studio 2013 still works best with IE10 or higher, and you still need IE10 or higher for some scenarios (details here - go.microsoft.com/fwlink). If you’re having issues installing Visual Studio 2013 due to IE, run the updated web installer from our download page (http://aka.ms/getvs) or from MSDN subscriber downloads (msdn.microsoft.com/.../downloads).
Trial license? I've just downloaded and installed Visual Studio 2013 from my MSDN account. Shame there is no product key, so I've been forced to go the route of registering using my MDSN account BUT Visual Studio says it is running using a trial license. Is this normal? Fortunately I'm only at the evaluation stage, but I'd be reluctant to use it in place of Visual Studio 2012 if it keeps thinking it is running under a trial license. Am I missing something?
The change in license keys is causing significant grief for all partners that obtain licenses through the MPN competencies. The problems are that MPN does not allow us to register all of our developer Live IDs (Microsoft Accounts) with MPN. The new 'feature' of activating based on Live ID is causing grief. How can MPN partners obtain static license keys for their legally licensed users?
I agree with Shane. Our company has one MSDN Subscription and 6 developers. In the past we were able to install Visual Studio on all the developer machines using the same product key. So now, you're saying this is not possible? Every one of our developers needs to have a MSDN Subscription in order to use Visual Studio 2013?!?! That's outrageous! What can I do? I don't want all of our developers signing into Visual Studio with my own Microsoft ID.
Found out that you need to go into the Microsoft Partner (MPN) website and add the developers to the list of Associated People and then assign one of our 10 MSDN Subscriptions to each of them. Once I did that, they can sign into Visual Studio 2013 and it will automatically register it for them.
"Our company has one MSDN Subscription and 6 developers. In the past we were able to install Visual Studio on all the developer machines using the same product key. So now, you're saying this is not possible? "
I'm sure if you give them your company name and email address, someone from the Microsoft legal department will be in touch with you very shortly. :)
You do know that you're violating the MSDN license agreement by doing this, right? MSDN is a per-user license. You can install VS on an many machines as you want, but you need to have a separate MSDN license for every user that uses it.
Does VS 2013 support Windows Mobile CE 6.5.3 development ?
I am very Intrigued... So Excited to educate myself further into coding..I am ready for a smoother experience. Thank You ...Visual Studios..
what is the key code?
1) I got a new computer.
2) Downloaded VS2013 premium from MSDN account (which is also linked to my visual studio online account)
3) Installed VS2013
4) Entered my Microsoft account
5) got the message "License Expired", and now it's impossible to open the "help" menu to register through a license key
6) went on msdn forums, found nothing interesting about that... only people reinstalling all over again and entering keys
7) Stuck here, I think I there is problems with your licensing stuff through the msdn account is simply NOT working
just my feedback for now