I try to attach a debugger to a deployed Azure App Service app and it gives me an error. Why is this?
I enabled the remote debugging from my app dashboard in Azure Portal, but selected VS 2015, because there is not an option for 2017..
I found the post by this guy while doing the research:
link
Related
I'm using Application Insights as part of my .Net Framework WebAPI project. When running the code locally (in debug mode), I can see all the events that would be sent to AI locally in Visual Studio by clicking the Application Insights button in the toolbar.
I've also got a Angular web App which works in tandem with the .Net backend. I've got the web version of Application Insights setup on it which sends telemetry to an Azure AI instance. Is it possible to have the Angular web app send its telemetry to the local AI instance in Visual Studio when I'm running it locally?
I'm using v2.5.10 of the #microsoft/applicationinsights-web library and Visual Studio Professional 2019 if that makes a difference.
Actually, there is no local AI instance. By default, the data you see in visual studio -> Application Insights Search window is from the current debug session, the screenshot is as below:
Another thing is that if you specify a valid InstrumentationKey, the data are always sending to application insights in azure portal(unless you setup firewall rule to block them).
For Angular web App, there is no way to just show the data in visual studio, but not sending to AI instance in azure.
Here are some suggestions just for your reference, but they cannot totally meet your requirement:
Solution 1: Sending data from Angular web App to AI instance in azure, then you can fetch these data from azure to visual studio locally. To do that, in the visual studio -> Application Insights Search window, change the Debug session telemetry to the AI instance in azure. Like below:
Solution 2: If you just don't want to send the data to Azure, you can use an invalid InstrumentationKey, and then open tools like fiddler to see these telemetry data.
I am following a series of instructions to deploy a mobile backend using Azure Mobile Services.
As part of that workflow I get to download a personalized backend app which downloads as Visual studio solution.
It builds fine and the next step is to publish it to Azure.
Instead of seeing the choice below (Microsoft Azure App Service) I am seeing 2 different choices
Microsoft Azure Web Apps, or
Microsoft Azure API Apps (Preview).
So, I chose the closest option (Web Apps) provided and it logs me into Azure and in a box which reports existing web apps I see none.
Yet I've deployed a mobile app in the Azure portal earlier.
In some of what I've been reading online it mentions a Publisher profile. I am just a bit stumped by not getting the "Microsoft Azure App Service" choice when I go to publish my backend to the cloud.
Here is the tutorial/guide which I am following (January 2016).
Perhaps the VS/Azure integration has changed since then or maybe I've more configuration steps missing.
Azure .NET mobile backend using Azure Mobile Services
Any guidance would be hugely welcome.
At this stage I am stuck as far as what I need to do to get my mobile backend published to Azure.
You have got an older version of the Azure SDK installed. The latest version of the Azure SDK provides the Azure App Service publish dialog.
I think I've solved this for now.
I was able to download a publish profile from the Azure Console which I could import within the "publish" dialog in VS2015.
I now have the mobile app up and running in Azure.
I'm simply trying to add my Azure Enterprise subscription to Visual Studio 2015 Enterprise. I go into Cloud Explorer, Add an Account, input my corporate email address and the box simply goes away.
Here's a quick screencast: http://www.screencast.com/t/DcKWQjIqn
Can anyone assist?
maybe try to download your publish profile from below link
https://manage.windowsazure.com/publishsettings
when you want to publish your app to Azure, instead of login. import the profile file
Back in March 2015, Microsoft announced that "Azure Mobile Apps" are replacing "Azure Mobile Services." A few days ago, I spotted the documentation explaining how to create an Azure Mobile App. I followed the doc and successfully got my "TestDroid" mobile app service running locally. However, I cannot publish the app to Azure from Visual Studio 2015 Community Edition.
To publish my "TestDroid" app, I right-clicked on the project and selected "publish."
This dialogue is already the "first sign of trouble." Technically my Mobile App service does not match any of the categories shown in the above dialogue. Still, because Web Apps and Mobile Services have been merged into one, the best choice is "Microsoft Azure Web Apps." So that is the choice I made...
Unfortunately, Visual Studio 2015 CE does not show my already-provisioned "TestDroid" app as an option:
However, I know that it exists because I created it a day earlier, per the instructions, and it does appear in a resource group blade on the Azure portal:
Also, in the Visual Studio "Server Explorer" I can see the "TestDroid" service:
The Server Explorer entry for "Mobile Services" is empty, but in this case I expect it to be empty because, as already stated, creating a "Mobile Service" is now considered the old way, and creating a "Mobile App" is the new way.
I'm guessing this is merely a glitch in preview material, but I would like to know how to resolve this.
I got this working. In the end I simply visited the Azure blade for my "TestDroid" mobile app, and selected "get publish profile". I used the "import" option on the VS 2015 publish dialogue to import the publish profile.
The original MS instructions did not mention that this slightly-round-about approach was necessary, so I did not assume at first to try it.
All is well that ends well. :)
I have a number of web apps hosted in Azure. These can be navigated to by their URL and are live and running correctly. If I use the server browser in Visual Studio 2015 I can see the correct web apps... AND previously deleted web apps.
However in the new Azure portal one of my web apps is missing. What do I need to do to get the new portal to recognise all of my web apps and should I be worried about visual studio displaying old deleted ones?
This is a sync issue that happens occasionally, and that we can fix for you. In order to do this, please share the name of any site in your subscription. You can create a temporary dummy site for that purpose if you like.