News

Visual Studio 2015 Approaching Single Sign-On Nirvana

It's not quite there yet, but Visual Studio 2015 has improved the authentication process so that developers aren't forced to sign into it more than twice a day.

Visual Studio 2015 has seen lots of productivity and efficiency improvements over the last few months, and authentication is one of the areas that the team has been tackling lately -- with favorable results. As Microsoft's John Montgomery explains in a blog post, as a result of some recent work based on a popular user request, developers will see fewer productivity-stifling prompts upon start up, particularly when developing against an Azure account.

"We're excited to share that we completed the deployment of some improvements that allow users to safely stay signed in and eliminate the forced sign-in every 12 hours," noted Montgomery, in the blog. He said that the forced sign-in every 12 hours, which is common for those using one of Microsoft's @outlook.com, @hotmail.com, and @live.com accounts while connecting VS projects to Azure, was one of the more notorious issues on the UserVoice feedback site.

"The next time you're prompted to sign-in, Visual Studio will follow the new authentication flow that lets you stay signed into the IDE without reentering your credentials every 12 hours," he explained. "This server-side fix is compatible with all Visual Studio versions that support Azure development back to VS 2012 though the improvements and bug fixes described above will give you the best results on the latest version."

The streamlined sign-on builds upon earlier work with a much improved keychain that was introduced with the latest VS release. "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," wrote Montgomery. "In the last few updates, we've made changes to core services like licensing and roaming, which allow you to refresh your license or roam your settings for up to a year or more without a prompt for credentials."

About the Author

Michael Domingo is a long-time software publishing veteran, having started up and managed several developer publications for the Clipper compiler, Microsoft Access, and Visual Basic. He's also managed IT pubs for 1105 Media, including Microsoft Certified Professional Magazine and Virtualization Review before landing his current gig as Visual Studio Magazine Editor in Chief. Besides his publishing life, he's a professional photographer, whose work can be found by Googling domingophoto.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube