Good morning,
I am trying to connect my Visual Studio with my Github account.
But for me some strange behaviour is happening.
I click on the plus and then Github.
[1
After that I am in my Browser where I must log in, which I do and accept the authorization. After that the Microsoft-Website says everything went well and that I can go back to VS.
But in VS nothing happened.
When I go into my Github account into the setting, Applications, Authorized OAuth Apps Visual Studio is listed. But still nothing in VS itself
Does anyone know what I have to do, or did I make a mistake?
Use the latest VSCode. Install gitlens extension to manage GIT from vscode. You will see an icon (accounts) at the sidebar like the one below (above the settings icon)
If you tap on it, it will ask you to log in with your GitHub account.
OR
Check whether "git" is enabled in your vscode settings.
To check that,
Files>preferences>settings
Type "git: enabled" in the search bar
There will be an option "git", it needs to be enabled if it's not already.
Please find the attached screenshot
Related
I have just upgraded from Visual Studio 2019 to Visual Studio 2022 and I have encountered a strange problem. When going to File -> Account Settings..., under "All Accounts" I used to have both my Microsoft account (which is also my Personalization Account) and my GitHub account. In VS 2019, there was no issue adding the GitHub account, but I have not been successful in VS 2022. When I select +Add▾ then GitHub/GitHub Account, the Connect to GitHub dialog pops up asing me to Sign In to either GitHub or GitHub Enterprise. Since my account is GitHub and not GitHub Enterprise, the only sign in option listed is "Sign in with your browser".
When I select Sign in with your browser, I get redirected to https://visualstudio.microsoft.com/vs/github-signed-in/ and I get the message "Success! Your authorization was successful. You can now return to Visual Studio."
The expected result at that point would be to see my GitHub account listed under All Accounts, but I do not. The other expected result would be to see Visual Studio listed in my GitHub account under Authorized OAuth Apps, and I do see it there, so it does look like the authorization was successful. As well, I can access repositories without issue, so it looks like the problem is inside Visual Studio 2022.
Has anyone else experienced this issue? Is this a known issue that Microsoft is working on?
EDIT: I found this on the Microsoft Docs, which lays out the steps I was following. Under Adding public GitHub Accounts, I get to Step 3 ok, but then at Step 4, I do not get the expected result.
I've also found out this is preventing me from creating a new repository from VS, or opening a repository directly from VS. I can still work with local repositories cloned via GitHub Desktop, but that's about it.
Very annoying.
This worked for me:
Open ‘Account options’(Click ‘Account options’ in account settings page or navigate to tools > Options > Environment > Accounts) and check ‘Include GitHub Enterprise Server accounts’ checkbox, then click on “Re-enter your credentials” again and check if you still unable to sign in to GitHub enterprise account?
https://developercommunity.visualstudio.com/t/unable-to-sign-in-to-github-enterprise-account-in/1460790#T-N1465373
I had a suspicion that this was related to some type of settings cache or potentially some type of previous Git setting. After wiping out all of my Visual Studio settings and re-setting to factory defaults (which is another annoyance) using the following commands, it started working for me:
devenv.exe /ResetSettings
devenv.exe /ResetUserData
When I clicked Manage Connections, the GitHub option wasn't available in the usual spot. Only the Microsoft Sign on. I found another spot to connect to GitHub;
Open the Team Explorer (View -> Team Explorer).
Click the Connect | Offline drop down from the top of the explorer.
Projects -> New Repository
Under Create a new GitHub repository select Add an account under the account field to open up the sign on page for GitHub.
I have projects that I have controlled be Azure DevOps. Every time when I open some of these solutions in the Visual Studio I get following error in the team explorer:
So when I re-enter my credentials I get the same error again. But when I restart Visual Studio my project is suddenly properly connected to Azure DevOps.
Could you tell me why I have this issue and how to solve it?
You may try the following items:
Go to Control Panel > Credential Manager, and remove all Windows Credentials related to TFS.
Close all Visual Studio instances, and delete the %LOCALAPPDATA%\.IdentityService folder if it exists.
Clear TFS caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache
As #4c74356b41 mentioned, repair VS.
As stated above, try doing only this step and see if it fixes the problem. It did for me.
Close all Visual Studio instances, delete %LOCALAPPDATA%.IdentityService if it exists.
It saves doing all the other steps.
The same issue is still occurring in 2021.
I had tried the sign out/sign in method, I had tried the local app data deletion method.
No luck with either.
What worked for me were the following steps.
Click on your name in the top right corner of Visual Studio and select Account Settings
Now rather than signing out, look below this to the All Accounts section. On some it will say "We need to refresh the credentials for this account"
Re-enter your credentials here.
This fixed the issue for me. I hope this helps someone else with this annoying issue.
Much easier solution to this. Close any open visual studio instances, restart visual studio as an administrator and connect to your ADO instance, i got this issue on cloning a repo personally, when i re-tried cloning again via web ADO the next time VS opened it worked just fine.
I've just had this same error as part of a wider issue with not being able to clone my DevOps projects, getting "connection reset" messages in Chrome and general weird behaviour for anything that tried to use my Microsoft login.
After a lot of hunting around, the cause of the issue turned out to be the Intel Killer wifi service. I opened the Killer Control Center app and turned off everything and all the issues disappeared:
Once I'd found the cause, a bit of googling turned up this post that suggests the Killer Prioritization Engine may be the root cause:
Bruno Nepomuceno 🎮 [MSFT] ··· I had the same issue and after a long
time I found out what was going on. My network card has a feature
called "Killer (I know, ironic) Prioritization Engine" and that was
on. Somehow it was interfering with the connection with Azure DevOps.
When I turned it off (and you can do it using the Killer Control
Center app), it started working.
I've been using VS for a while and have always pushed my code to github from within VS. I've just started a new project and want to do the same thing but in the Team Explorer github no longer appears. The options are either Team Services or Publish to a remote repository created outside of VS (which I understand in theory could be github but usually there is a github option within Team Explorer).
I've just created a new project called Test and github doesn't appear in this project either.
Anyone encountered this problem? And where can I check to see if the github extension is still installed?
Cheers,
Jerome
I noticed the same thing so I checked my Extensions and Updates and it looked like the Github extension uninstalled itself.
Searching the "online" pane for "github" allowed me to reinstall and now it's working again. Hope this helps.
You can access your Extensions and Updates by clicking on the Tools menu and it's about 3/4 of the way down the menu.
Latest Comment
I believe my problem occurs when using Nuget, however, if you are reading because of the TF30063 error. Have a look at the answer I provided and accepted.
Original Post
I am getting this error message when I try to check out. This happens randomly and can occur even if minutes ago the same instance of visual studio allowed me to check something else out for edit.
The current workaround is to reopen VS2010.
Using W7x64, vs2010 ultimate with TF2010 and sql2008 on my local dev machine. I am not part of a domain. I am the administrator of this computer.
Additional 2011-08-09
When the problem occurrs, I "close solution" under file. And then reopen the solution. I then get a uid/pwd box. I put my admin uid/pwd into it and then get a further error message. Again, closing vs2010 and reopening solves the issue.
Additional: 2011-08-30
I believe this has to do with nuget. I have provided an answer and so far after many months I have not had a TFS error. Where I should have had an error given the types of operations I have been performing which were identical to the scenarios making it fail.
I noticed that the problem occurred mostly after i installed a nuget package. After adding a nuget package i found that I could not check out. Restarting Visual Studio helped.
Based on this discussion:
http://nuget.codeplex.com/discussions/254328
i used this solution which appears to be working:
(I have copied the solution here if ever the webpage disappears)
Control Panel / Internet Options / Security Tab
Select "Local Intranet"
Click Sites button
Click Advanced Button
Add your TFS server http address to the list. e.g. http://tfs
Restart Visual Studio
Source: http://blog.rthand.com/post/2011/08/26/Fixing-combination-of-NuGet-and-Team-Foundation-in-workgroup-configuration-401-Unauthorized.aspx (Go straight down to The Solution half way down).
Don't let the Internet Options part fool you. I do not use Internet Explorer and this solved my issue.
I found this issue and the accepted solution didn't work for me. For me the problem occurred when trying to add a NuGet package to my project (through either the console or the GUI) and it would show the login prompt but not accept my user/password. It would try around 4 times and then fail and roll back the installation.
It turns out for me the issue was that I had Fiddler open and as soon as I closed it (to undo the proxy settings) I was then able to install the package without any issue. I didn't even have to restart Visual Studio to get it working.
Just thought I'd share this for the next person who comes across this issue.
I want to add a solution for people who are using VisualStudio online. My problem was that I was logged into VS2013 with the wrong Microsoft Account.
I would like to point that the accepted solution didn't work for me - probably it is for IE users.
My fix was to "clear the package cache"
Open VS
Go to Tools-> Options
Open "NuGet Package Manager" and select General
Click in the button: "clear the package cache"
When I had this problem I checked Event Viewer on my TFS machine and it showed a bunch of insufficient permissions Windows Sharepoint Service errors. I ended up just disabling the Sharepoint aspects of TFS since I wasn't using them anyways.
Got the error TF30063: You are not authorized to access Collection when comparing or merging the solutions in tfs 2012.
I found that enabling and disabling the windows authentication in IIS did randomly fix the error but found the disk space issue,
Once i cleared it, and enabled the windows authentication for TFS in IIS, it was a fix for me.!
-Pasha
This answer got me far enough to solve:
Control Panel / Internet Options / Security Tab Select "Local
Intranet" Click Sites button Click Advanced Button Add your TFS server
http address to the list. e.g. http://tfs Restart Visual Studio
On our internal network, for some reason, our computers don't always recognize other computers as being part of the domain - resulting in connections being sporadic/intermittent. My user had a restricted list set by domain policy, so I couldn't edit it. However, I could change the connection from just the computer name to the computer's fully qualified domain name and that appears to have solved the problem.
Our TFS server has some temporary connectivity issues right now, and as such VS has gone unresponsive, leaving 50+ developers unable to work!
Is it possible to switch TFS into an offline mode in the event of such an issue?
See this reference for information on how to bind/unbind your solution or project from source control. NOTE: this doesn't apply if you are using GIT and may not apply to versions later than VS2008.
Quoting from the reference:
To disconnect a solution or project
from source control
In Visual Studio, open Solution
Explorer and select the item(s) to
disconnect.
On the File menu, click Source
Control, then Change Source Control.
In the Change Source Control dialog
box, click Disconnect.
Click OK.
The 'Go Offline' extension adds a button to the Source Control menu.
https://visualstudiogallery.msdn.microsoft.com/6e54271c-2c4e-4911-a1b4-a65a588ae138
plundberg: The "disconnect" button is only available for the TFS provider starting in VS 2008. Even then, I'm not sure if it's officially supported. The recommended way to use the Go Offline feature is to [re]open the solution.
Martin Pritchard: if you get stuck mid-operation, you can force VS to timeout by pulling the network plug (literally) or running ipconfig /release.
Once you're marked offline, here's a step by step guide to working in that mode: http://teamfoundation.blogspot.com/2007/12/offline-and-back-again-in-vs2008.html
More detailed info on tweaking the behind-the-scenes behavior:
http://blogs.msdn.com/benryan/archive/2007/12/12/when-and-how-does-my-solution-go-offline.aspx
http://blogs.msdn.com/benryan/archive/2007/12/12/how-to-make-tfs-offline-strictly-solution-based.aspx
There are couple of little visual studio extensions for this purpose:
For VS2010 & TFS 2010, try this
For VS2012 & TFS 2010, use this
In case of TFS 2012, looks like there is no need for 'Go offline' extensions. I read something about a new feature called local workspace for the similar purpose.
Alternatively I had good success with Git-TF. All the goodness of git and when you are ready, you can push it to TFS.
Depending on which tool windows you have open, VS may or may not try to hit the team server automatically when it starts up.
For best results try this:
Close all instances of visual studio
Open an empty visual studio (no project/solution)
See which windows are opened by default, if source control explorer or team explorer or any other windows that use team are opened (and activated) by default, close them or switch them to a background tab.
Close visual studio
You should notice now that you can start visual studio without it trying to hit the TFS server.
I know its just an aside to your problem, but I hope you find this helpful!
If you have a solution open, and TFS is down, you might have trouble going into offline mode. If you close and reopen your solution, a nice little dialog will appear asking you if you want to Go Offline.
Alternatively if you don't want to close/reopen the solution, (as suggested by Bernie) you can install the TFS Go-Offline plugin, then click:
TEAM -> Go Offline
Simply, change the root folder name for your solution in your local machine, it will disconnect automatically.
I just wanted to include a link to a resolution to an issue I was having with VS2008 and TFS08.
I accidently opened my solution without being connected to my network and was not able to get it "back the way it was" and had to rebind every time I openned.
I found the solution here;
http://www.fkollmann.de/v2/post/Visual-Studio-2008-refuses-to-bind-to-TFS-or-to-open-solution-source-controlled.aspx
Basically, you need to open the "Connect to Team Foundation Server" and then "Servers..." once there, Delete/Remove your server and re-add it. This fixed my issue.
If the code has already been checked out by the user that if offline and they have the latest version on their local hd, then they just need to browse to the solution location and open the solution by double clicking sln file. The solution will open in disconnected mode.