Not directly programming, but related:
I'm using team explorer 2010 to connect to a 2010 TFS server (On a 2008R2 box), however when I try and connect, I get a red X on the project node and cannot expand it. There are not error messages or anything. Here is an image of what I am getting . I have the same exact setup on another system (except Windows 7), using the same credentials and it works fine. Anyone ever run into this before?
Run devenv.exe /ResetSettings
If this won't help, you'll have to do a clean install of VS 2010 Ultimate (preferably Ultimate)
I get this every once in a while.
To resolve this, I delete the cache folders in the %APPDATA%..\Local\Microsoft\Team Foundation\3.0\Cache folder.
Go the steps from here.
Related
After my recent upgrade to Visual Studio 2019 (?) on Mac, I am unable to connect to my TFS server using the TFS Source Control extension.
My current setup:
Visual Studio for Mac, version 8.0.3.14
Source Control Extension:
Team Foundation Version Control for TFS and Azure DevOps Version
0.4.4.5
Steps: In Team Explorer, now I see two options:
1) Add Account
2) Add Server
When I try Add Account, a dialog pops up asking for my MS credentials - I enter them as usual, and then nothing further happens, no feedback whatsoever. Is this because it thinks this account is already "added"?
When I try Add Server, I enter my azure dev ops server name, then for user name/password I enter my MS account email and password. I leave domain empty. I get a message:
"Server already exists."
Here is what I expect to see (screenshot from VS 2017 on Windows):
Instead, nothing gets populated the way it normally does in Team Explorer: Pending changes, work items, settings - the entire panel is empty:
I do switch between Windows and Mac a lot, but if I remember correctly, everything worked fine from both workspaces before, so it probably happened when I upgraded to Visual Studio 8.0.3.14 on my Mac. Any ideas on how to fix this?
I wondered the same thing but without the update process in my back pocket... meaning I haven't written any C# in a while but I'm coming back to it. I set up a project with TFS in Azure Dev Ops on my pc, then went to check it out on my Mac and couldn't find any reference anywhere to TFS. Subversion and Git are in there, but no TFS. It took a little while to find it, but here's what I found. The short answer is they want you to use Git, not TFS as TFS is not supported in VS 2019 for Mac. The article does list work-arounds.
https://learn.microsoft.com/en-us/visualstudio/mac/tf-version-control?view=vsmac-2019
I am trying to set up an integration with MS Project 2013 with TFS 2017 I have not tried this before. so i am not sure if there is a problem with my pc setup or the addin configuration.This is the error i get when trying to open saved query:
Error Converting Value "System.Security.Principal.WindowsIdentity;xxx" to type 'Microsoft.VisualStudio.Identity.Services.IdentityDiscriptor'.Path 'authenticatedUser.descriptor'. line 1 postion 168
I am able to load it from Visual Studio 2015 in the workitems load the Query and then click "Open in Microsoft Office" then choose MS Project. this loads successfully. but i do get errors that I can't publish changes. It asked to restart Project and try again
I cannot reproduce this issue with project 2013 and TFS 2017.
Check Addins’ key in registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\MS Project\Addins), change newest addin (e.g. TFCOfficeShim.Connect.5) LoadBehavior to 3 and others to 0, then try to open saved query in Project 2013 and check the result.
If still don’t work, try to repair your project product.
I have uninstalled Office 365 and Project 2013. Restarted my PC and installed Project 2013 and this fixed this issue.
The issue came back and did some more google searches. I found the answer as part of a bug kb
https://support.microsoft.com/en-us/help/3181963/excel-or-project-cannot-connect-to-tfs-2010-or-tfs-2012-servers
After installing this update and rebooting it works.
After I install Visual Studio 2013 update 2, I notice that right click on any kind of project file (aspx, cshtml) causes about 45 seconds of hang in Visual Studio. It eventually opens context menu, but every single time this happens.
If I right click on Solution Explorer, Class View etc.. there is no issue at all, just in files editor.
I am using intel i7 processor and 16gb ram (hardware is not an issue) and Windows 8.1 Pro.
I also cannot connect tfs online for last 2 days so I am using my solution with disconnect from tfs. This causes hangs on start up because it tries to connect remote server. But I am not sure it will cause issue on right click of the files.
What I did up to this moment;
1- Installed last update again
2- Restarted Visual Studio several times
3- Restarted PC
4- Cleared TFS cache files
Is there any idea what is causing this issue?
Update: I created an empty MVC project without TFS binding and there is not issue. Looks like it is totally related to TFS dis-connectivity, I will investigate more and will post answer if find out.
ReSharper can cause this problem. You can suspend it (temporarily) to see if the problem is solved. If it is indeed solved, you should clear ReSharper's cache before you enable it again. Go to %LOCALAPPDATA%\JetBrains\ReSharper and delete the SolutionCaches folder for whatever version of ReSharper you are using.
I just had the same issue and in my case wasn't Resharper the culprit. What worked for me was, inside VS, right clicking the SOLUTION, open Nuget Package Manager and at the top was a message telling "There are missing packages". I clicked to restore them and immediately after that the problem was solved.
Just sharing as I had a different cause, so this may help some one else. My visual studio (2015) was locking up for 10-20 seconds on the right click context menu on the solution.
It turned out to be a faulty extension. Go to 'tools' > 'Extensions and updates', and try disabling all your extensions. If that solves it, try enabling a few at a time, until you narrow it down to a particular extension.
In my case, it happened to be the 'ImageOptimizer' extension, that comes part of Madz 'web extention pack': Github issue on 'ImageOptimizer'
Recently had this issue in Visual Studio 2015
For me it was because I had silently been disconnected from the TFS server
When you right click in a source-controlled file, part of the context menu consists of TFS commands (check out for edit, history, annotate). I presume that VS was spinning waiting for a TFS connection that would never come.
Getting reconnected to TFS solved the issue.
I'm trying to set up the siren of shame build monitor, but for some reason can't connect to my TFS.
TFS itself is running on port 8080, and TFSBuild on 9192 - but putting http://build-server:8080 or trying other ports does not work...
(Update 1) I've downloaded the source, and also looked using Wireshark into what is happening when it tries to authenticate. I'm confused, as the code is using standard .net Libraries for TFS - Microsoft.TeamFoundation.dll (v2.0.50727). It seems to be looking for web services that do not exist if I look in IIS on the server - namely POST /TeamFoundation/Administration/v3.0/LocationService.asmx
Is it the case that this is not compatible with TFS 2008 at all, and only TFS 2010 will work?
I downloaded the "Siren of Shame" to have a look.
To connect you need to enter the URL for TFS in the following format
http://tfs-Application-Server:8080/tfs
Note that it attaches to the TFS server not the build server (or build controller).
However having connected to TFS it looks like a pain to configure. It correctly detected all of the Team Project Collections that I have in TFS but when I selected one of the collections it wasn't showing any running builds. So I tried selecting a single Team Project, once again no builds were displayed. Finally I selected a build that I knew was running, only then did it show up in Siren of Shame.
I have thousands of builds and I don't want to have to select each one individually to be able to monitor it. At the very least I want to be able to select a team project and monitor all of the builds in that project with one click
There are a number of alternatives out there. But none of them are great
http://teambuildscreen.codeplex.com/
http://buildmonitor.codeplex.com/
http://tfsbuildinspector.codeplex.com/
I have successfully installed TFS 2012 and migrated my TFS 2008 databases into TFS 2012. From within Visual Studio I am able to connect to the new TFS server through my source control plugin and can see all of the projects that were imported from TFS 2008. The problem is that when I click 'Connect' I am getting an exception that an HTTP 500 error has occurred. On the server I am getting a warning in the Event Viewer because of this URL:
http://[servername]:8080/tfs/tfs2008projectcollection/services/v3.0/locationservice.asmx/TeamFoundation/Administration/v3.0/LocationService.asmx
If I manually go to the above URL minus '/TeamFoundation/Administration/v3.0/LocationService.asmx' the page loads fine. Additionally if I remove '/tfs2008projectcollection/services/v3.0/locationservice.asmx' and navigate to http://[servername]:8080/tfs/TeamFoundation/Administration/v3.0/LocationService.asmx the page loads fine.
Thing is this only happens with the project collection that I imported from 2008. I created a new project collection directly in TFS 2012 and I can connect to that project just fine within VS 2012. Has anyone ran into this issue and, if so, what is the best way to correct it?
It is unclear what caused / is causing this problem but after a TFS server reboot the issue is no longer manifesting itself.
I'm am also having this issue. I have Update 4 and this is a fresh machine. I see the issue here, have tried the fix and no luck. I've also tried a reboot with no luck. I see the issue here and it appears that Microsoft's only suggestion is to 2013. Unfortunately they do not supply a migration path directly between 2008 and 2013, so I have to cross my fingers and hope that upgrading the machine after importing from 2008 even with the error will solve the issue.
Can anyone confirm the issue is actually resolved in 2013?