I just installed the Azure SDK for Visual Studio 2013 from this link http://go.microsoft.com/fwlink/?LinkID=324322. When I restart Visual Studio, and go to Server Explorer, I see the Azure node. I right click, and go to Manage and Filter Azure Subscriptions. I click 'Add an account...' and nothing happens.
I'm using Visual Studio Ultimate 2013, Update 5
PS. I thought maybe it was the account I had logged into Visual Studio with, so in the top right, I did Sign Out, and now I can't sign back in. I get this:
The component 'Microsoft.VisualStudio.Services.Client.Controls.BrowserWindow' does not have a resource identified by the URI '/Microsoft.VisualStudio.Services.Client;component/controls/browserwindow.xaml'.
I have the same issue but I believe I have found a workaround.
I went to the folder: "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Windows Azure Tools\Common\KeychainDlls"
I renamed Microsoft.VisualStudio.Services.Client.dll to something else (e.g. __Microsoft.VisualStudio.Services.Client.dll)
I then restarted VS2013 and I was able to sign in.
Then finally I renamed it back.
I hope this helps
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:
For some reason I cannot check in my code to our Visual Studio Online account. Other developers can, but not me. This is the error I am getting:
"Could not find dataspace with category VersionControl and identifier [some guid]"
Searching for any help on the above error is not returning anything meaningful.
This started to happen after I installed Visual Studio 2015 Enterprise. I launched it for the first time after creating a new web application with Visual Studio 2013. I then opened that new solution in 2015 and all was fine. Things began to go awry once I tried to put it in our Visual Studio Online account. When I went to Team Explorer in VS 2015 I selected "Projects and My Teams / New Team Project". This then bounced me over to our Visual Studio Online account in the browser for me to fill out that simple form to create a new team project. I filled the form out and submitted. I then got an error that the project was not successfully created. Unfortunately Visual Studio still thinks it was created and it shows up in the list of projects ONLY WITHIN Visual Studio -- it does not show up online. Eventually I just became frustrated and deleted everything related to all that I just tried but then learned that I cannot check anything in now on my old projects! I had other developers test and they still can so the problem evidently is on my machine. I then uninstalled VS 2013 and VS 2015 then reinstalled VS 2013 and am still having the problem.
I am hoping someone can point me to some cached junk that needs to be cleared on my system. :-)
This is a bit shot in the dark, few things you can try:
Delete the local cache under:
%localappdata%\Microsoft\Team Foundation
%localappdata%\Microsoft\VisualStudio\14.0\SyncSettings
Open cmd. Type:
"%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\Common7\Tools\vsvars32.bat"
Verify connections: tf settings connections
Run Visual Studio in safe mode (devenv.exe /SafeMode)
Run Visual Studio with activity log (devenv.exe /log) and check for errors.
After opening Visual Studio 2013 successfully, I switch to the Team Explorer tab and consistently get a popup error dialog saying that, "Microsoft Visual Studio 2013 has stopped working" and "Windows is checking for a solution to the problem".
This seems to be directly related to TFS (2013 Update 4) since other tools that access TFS (like Source Control Explorer > Workspaces...) also cause the crash.
Edit: I have already tried a VS 2013 Repair. This took all morning with no different results.
This is frustrating because I cannot use TFS outside of the command-line tools. Any help would be greatly appreciated. Thank you.
Credit to Tuğrul Emre Atalay for the post: Visual Studio Crashing When Checking In.
His issue was checking in changes and having Visual Studio crash. In my case, just using the TFS tools was consistently causing a crash.
The fix for me was to only clear out the local cache and not both the server and local caches.
Clean the Cache folder on client computer. The folder path is: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache.
I cleared this folder and I was able to use all of the TFS tools without any further issues.
I then realized that this happened since migrating to a new user name. I had copied many of my settings over from my old account folder and it must have corrupted the cache area.
I had the same issue with Visual Studio 2015 Enterprises. When i open it, VS wasn't able to connect to TFS and it crashed when i clicked on "manage connections"
The issue was not about the cache (I cleared the cache, made a repair of VS and nothing changed) but about the fact that we are currently migrating our projects from perforce to Git with Team Foundation Server.
When Visual Studio starts, it seems VS is trying to connect to TFS with linked Git repositories, but since the plugin currently used is perforce, it causes an exception somehow.
The solution is to set your source control plugin to Microsoft Git Provider (or Visual Studio Team Foundation Server if you are using it)
Here's two screen shots I took. Right after I selected the Microsoft Git Provider, the Team Explorer tab automatically refreshed and I am now able to connect to my projects.
Go to Tools -> Extensions and Updates Look for Github Extension for Visual Studio and Uninstall it
Never Mind as you can still work with Github
Now Restart Visual Studio.
Enjoy working on Team Explorer.
Few days ago i had to reinstall VS. So after uninstallation, I downloaded VS2010 Ultimate from MSDNAA and installed it. Everything went without any trouble, but when i run VS I found, that there wasn't a Team Explorer.
So i downloaded TE from Team Explorer link. But after installation TE, Visual Studio still doesn't see TE. There is nothing in Menu -> View and Menu -> Tools -> Options -> Source Control.
What should I do now?
Are you able to see Team Explorer which is tabbed along with the solution explorer (At the bottom of the solution explorer window)? If not click view->Team Explorer (Ctrl+M). From there you should be able to connect to your TFS instance.
When you install the Visual Studio, then Team Explorer comes by default with VS.
You can check Team Explorer in View->TeamExplorer
If you do not found Team Viewer in your View then you can download it from below link
https://blogs.msdn.microsoft.com/devops/2017/04/05/reintroducing-the-team-explorer-standalone-installer/
or you can download it from vs installer.
For future readers:
I was missing some menus from the Team Explorer side panel.
what fixed it was resetting user settings by manually running devenv.com /resetuserdata from the visual studio folder.
To me it was:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.com /resetuserdata
Notice: this will reset your settings, so make sure you import / export it first (if you require anything specific) .
I'm assuming your using TFS. Have you connected to a TFS instance using the menu Team -> Connect to team foundation server?
You need to download Microsoft Visual Studio Team Explorer 2010 from here:
https://www.microsoft.com/en-us/download/details.aspx?id=329
After several deployments, I receive the following error when trying to re-deploy a solution:
Error occurred in deployment step
‘Recycle IIS Application Pool’: The
communication object,
System.ServiceModel.InstanceContext,
cannot be used for communication
because it has been Aborted.
The only solution I have found (not ideal) is to restart Visual Studio.
Anyone know a better way?
I have seen this a couple of times as well and the only resolution I found was to restart Visual Studio as well.
How come restarting Visual Studio will fix anything :)
You need to run Visual Studio as Administrator (by right clicking on its icon)
If still persists, restart the server.
If still persists, add the administrator account under which you are running Visual Studio to Sharepoint Central Administration for that sharepoint web portal.