I created a Visual Studio 2013 MVC project in Visual Studio 2013 Ultimate using Visual Studio Team Services through visualstudio.com. I have since reinstalled Windows and Visual Studio 2013 and have reopened the solution and receive error:
The solution you have loaded is bound to the source control server at https://{myaccount}.visualstudio.com/defaultcollection, but no workspace on that server could be located. If you do have a workspace on this server, and you want this solution to be opened under source control,
connect to that server using Team Explorer and then re-open the solution.
I am having difficulty locating how to setup and manage workspaces on my local machine and Team Services.
If you open visual studio and connect to your team project you should then be able to open the solution explorer. Once open you should see your project grated or as It is not maped locally.
Right click on your desired mapping folder level and map it to your local disk.
Note: You will need to map it to another location and pull across any uncommitted changes.
Related
I am sometimes encountering "TF30063" errors in Visual Studio 2019 when connecting to an Azure DevOps (TFVC) repository.
I am using Visual Studio 2019 (v16.1.4 at the moment) on a Windows 10 Pro (version 1809) workstation. This workstation previously had Visual Studio 2017.
We have a department repository at dev.azure.com, configured as a TFVC repository (not Git). This repository was originally created when Azure DevOps was VSTS, but we weren't using it for anything until recently, after it had been converted to Azure DevOps.
When opening a project that has its source managed in Azure DevOps in Visual Studio 2019, I have been encountering an error like this at times:
TF30063: You are not authorized to access dev.azure.com/[ORG-NAME]
Sometimes the error occurred when opening the project, and at other times when attempting to get the latest version of files or checking files in or out from the Azure DevOps repository.
I have been searching for this issue online for a few weeks, and have tried various suggested solutions, such as clearing the ".IdentityService" folder, or clearing out some specific AppData local/temp folders, or logging out of and back into Azure DevOps, etc. Some of these seemed to resolve the issue temporarily, but the issue always returned.
However, I now believe I know how to reliably cause this issue (and how to resolve it in the short term).
I have discovered that I can reliably cause this TF30063 error in either of two ways:
If I have Visual Studio open with a project connected to our on-premises TFS server, and then I open another instance of Visual Studio with a project that is connected to Azure DevOps.
If I don’t have any other projects open, but the last time that I had Visual Studio open, I left the "Team Explorer" tab selected (for example, because I had just checked in some files), and I open a project connected to Azure DevOps.
In either of the above cases, I will encounter the TF30063 error when I open a project connected to Azure DevOps (either when I first open the project, or when I attempt to perform any source control operations). In either case, the solution is relatively simple, as follows:
If Visual Studio is showing the "Team Explorer" tab/panel, select the "Solution Explorer" tab/panel.
If Visual Studio had already been showing the "Solution Explorer" tab, select the "Team Explorer" tab and then select the "Solution Explorer" tab again.
Make sure that the "Solution Explorer" tab is currently selected, and close this instance of Visual Studio (if I have other Visual Studio instances open that are connected to the on-premises TFS server, I can leave those open).
Re-open the same project (connected to Azure DevOps) in Visual Studio, and now everything seems to be fine.
Does anyone else have any additional information on this TF30063 error with Azure DevOps repositories, or any additional suggestions for resolving or working around the issue?
Please try below and see if it helps.
Close all instances of VS
Delete %localappdata%.IdentityService
Restart VS
another approach:
Close all VS instances.
delete your VS appdata folder and then open VS
Though this will reset all your setting. Hope it helps.
If you still face the same issue , please raise a request in below link.
https://developercommunity.visualstudio.com/content/problem/post.html?space=8
you can do it from here too:
I am working on an Angular 2+ project in Visual Studio 2017 but without a Visual Studio solution or csproj. We're just using the Angular CLI to generate the project serving the app using "ng serve". We are opening the folder in VS by going to File->Open->Folder, which is working well. But we are using TFVC (Team Foundation Version Control - 2015 on premise) as our source contorl and it seems as if when you open a Folder in Visual Studio 2017 it expects you to be using GIT. When I go to the Team Explorer window I only get GIT options.
I've tried:
Creating a folder apart form Angular
Checking the folder into TFS first before opening in Visual Studio
Reconnecting to the TFS server
NOTE: once the Folder is closed I have access to TFS again. I feel like I'm missing something obvious.
Check comments in this article:
https://blogs.msdn.microsoft.com/visualstudio/2016/04/12/open-any-folder-with-visual-studio-15-preview/
I have managed to corrupt my local Visual Studio Team Foundation Server workspace mappings. Visual Studio can successfully connect to TFS and I can manage the TFS Server connections. However, I cannot open Source Control Explorer or the Workspaces/Manage Workspaces dialogue. Both windows fail with the following message: "Error Unexpected end of file.". From my local machine I also cannot get any information about my workspaces from the tf.exe command line which fails with the same error message "Unexpected end of file."
I would like to note that TFS/database still has my workspaces mapped correctly since I can successfully retrieve information about them from a different machine.
I would like to repair or remove whatever local file Visual Studio is using to map the workspaces. Does anyone know where this information is stored?
I've fixed my issue where Visual Studio was unable to open Source Control Explorer and Workspaces/Manage Workspaces dialogue by deleting the cache folder located here at:
%localappdata%\Microsoft\Team Foundation\5.0\Cache
Once this folder was deleted reopening Visual Studio was able to connect to Source Control Explorer and I can once again manage my workspaces from the IDE. (Visual Studio created a new cache folder in the same location after starting)
I am workign with a central Team Foundation Server (2010) and I connect to it from my workstation. On my workstation I use both Visual Studio 2010 and 2012. I have installed both have the Team Explorer 2010 and 2012 and the latest patches and hotfixes.
I need to use both Visual Studio 2010 and 2012 because I am developing both .NET 4.5 code and SQL Server Reporting Server reports for SQL Server 2012.
I can configure both instances of Visual Studio to connect to TFS, I mapped my workspace in Visual Studio 2012 and I can interact with Source Control. I tried configuring Visual Studio 2010 to use the same working folder, I can connect to TFS, I can see the source control folder, but when I try to map it to the same local folder I get the following error message:
Map
The working folder "C:\TFS\Example" is already in use by the workspace JohnDoesPC; Doe, John on computer JohnDoesPC
I tried configuring the workspace mapping through the dropdown in the Source Control Explorer:
Team Explorer>project>Source Control>Map Window>(Set Local Folder)
And I tried it through the Source control menu under the File menu:
Go File>SourceControl>Manage Workspaces>(Highlight my showing workspace)>Edit>Try to add existing folder.
What am I missing? Do I need to map my solution folder to two different local folders? That would be very confusing and inconvenient!
The simplest way to put this is that I want two versions of TFS to point to the same local location. Is that possible? Or should I be creating a new project up just for my SSRS reports?
EDIT: See pic for more detail:
Make sure that in both Visual Studio 2010 and Visual Studio 2012 the same work space name is selected. If you cannot see the workspace of 2012 in Visual Studio 2010, check the advanced workspace settings of the workspace in 2012. Ensure that the workspace type is set to server.
When both Visual Studio versions are using the same workspace name, they should be able to see and use each others file mappings as well.
This is what the settings in 2012 should look like:
And that workspace should be visible in 2010 as well:
Make sure you select the same workspace name in both versions of Visual Studio:
I am currently developing on Visual Studio 2012 RC using TFS Preview for source control. I would like to create an SSIS Integration project, which requires me to use Visual Studio 2010. However, when I connect to TFS from VS 2010, it automatically creates a new workspace and does not list the VS 2012 workspace.
If I issue the tf workspaces command from the VS 2010 command prompt, I see only the VS 2010 workspace, and if I issue the command from the VS 2012 command prompt, I see only the VS 2012 workspace (both indicate the same colleciton is being used).
Is there some way I can get VS 2010 to see the VS 2012 workspace? I would prefer not to have to have two copies of source code just to be able to use VS 2010 for the SSIS project.
TFS 2012 introduces a new concept called local workspaces, which differ subtly from the behavior of workspaces in previous versions of TFS (the old default behavior is now called a server workspace.) Local workspaces do not require read-only files and instead allow files to be edited without checking out from the server, and they are intended to be more suitable for small to medium sized workspaces. For this reason, local workspaces are the default in TFS 2012.
Local workspaces, however, are not compatible with TFS 2010 and TFS 2010 clients will not be able to use a new local workspace.
You can convert the workspace that you created with your VS 2012 client to a server workspace. In the Edit Workspace dialog, select Advanced, and you can change the type from a Local to a Server workspace.
At that point, you should be able to connect with VS 2010 and choose that TFS workspace.
(Note that it's not sufficient to use tf workspaces as that will return a cached copy of your workspace list - you will need to connect to the server either with Visual Studio 2010 or with a tf.exe command that talks to the server.)
In addition to the Location="Server" property mentioned in other answers/comments, the File Time property must be "Current", as shown below.
Workspaces created in Visual Studio 2012/2013 with either Location="Local" or File Time="Checkin" are not visible/usable in Visual Studio 2010.