With the imminent arrival of Visual Studio Online Package Manager, which lets us host NuGet (and other) packages on our Visual Studio Online account, it is almost certain that you are going to lose the plot when managing NuGet packages in Visual Studio and keep getting prompted for your account details (especially as the “Remember Credentials” tick box is just there to upset you). So Visual Studio for Mac being used for new code you create new Git repo(s) and still have everything in the same Team Project / backlog. – Sacha K May 18 '17 at 19:15 Yeah, been doing that for a while, but most of the code at my workplace is in a large TFVC mega repo, I've been pushing for git for new stuff.
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 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. We also updated the Windows store publishing features to use the keychain for single sign-on with the rest of the IDE. Still, if you developed against Azure using a Microsoft account (e.g. @outlook.com, @hotmail.com, or @live.com) as many of us with MSDN subscription credits do, Visual Studio prompted you to sign in every 12 hours to access Azure resources from the IDE.
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. This addresses the most commonly reported sign-in issue. 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. 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.
Thank you to all the community members who have shared feedback to improve the identity experience in Visual Studio and, as always, we welcome all your comments. Please report any problems via the Report a Problem control in Visual Studio. If you have a suggestion, please create a post on UserVoice. Keep an eye out for more improvements to come in Visual Studio “15” and beyond.
| John Montgomery, Director of Program Management for Visual Studio @JohnMont John is responsible for product design and customer success for all of Visual Studio, C++, C#, VB, JavaScript, and .NET. John has been at Microsoft for 17 years, working in developer technologies the whole time. |
The only two options I can see are git and subversion. I tried entering the url using the subversion option and it did ask me for credentials but the correct credentials never worked.
Visual Studio For Mac Always Asking For Git Credentials
1 Answer
TFS can use either TFVC (Team Foundation Version Control) or Git for the source control part. You don't have to use an external Git server, it has an internal one - with the data stored in the TFS SQL database. You create your first repo when you create the Team Project, but you can add repos later and you can mix TFVC and Git repos in the same Team Project - since 2015.2 I think.
Microsoft is still in the denial and marketing speak phase but TFVC is basically dead, even Microsoft is using Git for all their new repos. I'm ready to bet Visual Studio Code and Visual Studio for Mac will never connect to TFVC.
Edit: I lost my bet for Visual Studio Code, it can connect to TFVC using the Visual Studio Team Services extension since version 1.116.0 (2017/04/12).
Sacha K
Sacha K