For cloud service deployment , when I hit publish, visual studio goes unresponsive. No error and if you try to click on visual studio it says visual studio is busy.
Fix that worked for me- Go to server explorer, Go to Azure node and right click and connect to a Microsoft Azure subscription. Reenter your credentials and connect and try to publish again.
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:
Suddenly (at least I have no idea that were changes) I'm getting the following error during web deploy from Visual Studio 2017 to Azure classic Cloud service.
I re-checked the setting on Azure Portal:
and server itself:
Do you see some problem? What else can I check to fix the problem?
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
I want to publish a Lightswitch HTML client application to a Azure web app. The problem is after clicking "Publish" visual studio 2013 freeze.
The problem is that I use multiple azure subscriptions in Visual Studio and the Lightswitch Publish dialog is not able to handle multiple azure subscriptions.
Solution:
Go to Visual Studio -> Server Explorer
Right-click to Azure -> Manage subscriptions
Select only the required azure subscription
Publish
I had the same problem with multiple subscriptions. When the problem could not be fixed by managing subscriptions I ended up closing Visual Studio and deleting the Windows Azure Subscription.XLM file found at C:\Users*xxxx*\Documents\Visual Studio 2013\Settings on my computer. The next time you publish you will need to re-enter your subscription credentials. Hope this helps.
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.