I have been using Visual Studio 2012 with Microsoft Team Foundation Server for a while.
I noticed today, when I am in Team Explorer and I click on "Web Access", it throws an error that says "Class not registered". Everything else seems to work.
Any idea why I would be seeing this error?
If you go to Add/Remove Programs and run a repair for Team Foundation Server, that should fix the issue.
Also, you should consider installing the latest quarterly update available for TFS.
http://www.microsoft.com/en-us/download/details.aspx?id=30658
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
When I try to connect to TFS 2015 from within Visual Studio 2017, I get the message "No repositories available". The tfs server is listed, but I cannot connect.
No problems in Visual Studio 2015.
Do you have an idea, what I could do?
Thank you
This is a new UI design changed by Visual Studio 2017.
In Visual Studio 2017, we changed the behavior of the Connect page. We
now populate the Connect Page list with only the items you’ve
selected.
If you select a project and click "Connect", you will see only the project node in the Connect page. To get your repositories to appear
on the Connect page you need to select the repository node in the
Connect dialog and hit Connect.
This change was made in response to feedback from folks who had large
numbers of repositories in their team projects and wanted to not have
them all added whenever they connected to anything in said project.
More details please refer the visual studio team's comment in this similar question: Team Explorer does not show the repositories within a multi repository project
I had similar issue ,for me TFS is using Kerberos authentication. I changed the authentication to NTLM by running command from Developer tools under TFS server.
TFSConfig Authentication [/provider:NTLM|Negotiate] [/viewAll] [/siteType:ApplicationTier|Proxy]
Reference - https://learn.microsoft.com/en-us/azure/devops/server/command-line/tfsconfig-cmd?view=azure-devops#authentication
We also did IISRESET after this.
After this i am able to view the Repos under visual studio.
We have upgraded TFS2008 to 2013 on a new server and source control/workitem tracking is okay - we can use all that from within VS2013 Pro.
We have also upgraded Sharepoint (containing all the project documentation) to a new database server and using the TFS 2013 Adminisration Console we can see the Team Projects listed there.
However although from the VS2013 Team Exlorer we can add the team projects and open the 'web portal' for each team project, we cannot see any of the documents nor can we (seemingly) view in a browser the portal that in VS2008 shows the document libraries.
Are we missing something in the unfamiliar interface, or can anyone advise what the cause might be and how to fix it?
You need to "wire up" the Team Projects to the Sharepoint sites. It sounds like they have been detached through the order of the upgrade.
Sharepoint needs to be upgraded and available during the upgrade process or this happens
You can however easily wire them back up. In the Team Project in Visual Studio go to the Team Explorer and do "Settings|Portal".
You should have a dialog for wiring up The existing Sharepoint to the Team Project.
If you don't you may have Tbeen disconnected at the collection level. In which case you can open the TFS Administration Console and follow: http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/
I have created a repo using TFS (cloud) on www.visualstudio.com
I created my repo as on something as myproject.visualstudio.com and when trying to run or click on following link:
Open new instance of Visual Studio it throws an error as
Cannot open file vstfs:///Framework/TeamProject/..... Verify that the
file still exists and then try again
I searched here on SOV and also on MSDN and found a thread on MSDN forum but it was about some services pack and updates.
Has anybody ever used this service?
Thanks.
I assume that you already created project on yourAccountName.visualstudio.com
Then, if you are using VS2010, install recommended update SP1 VS2010 SP1
After that (it might take a while as long as 30 min), just start VS2010, on start page just click Connect To Team Foundation Server, then on "Select a team Foundation Server" click on "Servers", then "Add", and in "Name or URL of Team Foundation Server" just paste URL of your AccountName such as: "https://yourAccountName.visualstudio.com" (withouth quotes). then you jsut click OK and that's it. Your VS2010 should be now connected with your account at visualstudio.com
This is a bit of a manual method but it works :)
You can find more about it in this MSDN blog Team Foundation Service Preview – Connect Visual Studio 2010 to Your TFS Preview Account
there is a solution I just found which walks me through IDE.
Run VS2012 Under "Start" in VS 2012 click on "Connect to Team Foundation Server ..."
It will popup a dialog so then in bottom of dialog/form there is link as "Sign In", click on it
Enter your user-name and password Now, you are connected to the server and can view
all your Repositories
P.S. don't forget to add your server URL on the list TFS in your IDE provides.
I have a tfs server installed, and it allow me to connect, but when try to create a team project, it shows this message.
TF30172: You do not have permission to create a new team project.
All my permission are currently set, or at at least I think so.
What else can I check?
This is a know issue with Visual Studio 2010 and Team Foundation Server 2012.
From Buck Hodges' blog:
You must use the Visual Studio Team Explorer 2012 (included in all Visual Studio editions or may be separately downloaded) to create a team project on a TFS 2012 server. If you use VS 2010, you will get an error about not having permission. The error message is very misleading, because it’s not a problem with your permissions.
You should to install this hotfix to resolve this issue.
You Should have the right in Team Project Collection administrator . you have to add yourself in this group.
and after that may be it is also required to add yourself in Contributor group.
kindly check that you have give the rights in Team Project Collection Setting .
not in Team Project Setting.
Having tried a plethora of solutions including many reinstalls, service pack reapplication, hotfixes and the two answers provided by Mak and DaveShaw.
The workaround I used was to create the new team project using Visual Studio 2013. Once I did that I was able to add my solutions to source control. I guess VS 2012 could be used too.