You’ve told us that Visual Studio makes you sign in WAY too often. Over the last year, we’ve released several improvements to help address your feedback. The keychain we released with Visual Studio 2015 made it possible to manage multiple identities in VS and gave you single sign-on across the IDE.
In Visual Studio 2015 we have made radical changes to sign in experiences and connecting to your online resources. You can now chose to use a single account across many developer services, or use multiple accounts across Visual Studio. All of this is possible because of the new Visual Studio Account Manager.
Visual Studio 2015 was released yesterday. Throughout the prereleases, you’ve seen some major announcements, from the new VS 2015 product lineup introducing Visual Studio Enterprise and Visual Studio Code, to the release of a free Visual Studio Community Edition with support for VS extensions.
Anyone who has built an application in Visual Studio that uses several services (e.g. roaming Visual Studio settings, accessing Azure services in Server Explorer, or using Windows Store) has probably experienced what we’ve come to call “sign-in Whack-A-Mole,” with prompts popping up when you least expect them to.
Applications today are leveraging the cloud to deliver personalized experiences and offer new capabilities. So it’s no surprise the tool used to build those applications is also putting the connected developer at the center of the IDE.
In Visual Studio 2012,