Azure PremiumV2 app service plans lose the ability to attach remote debuggers over Standard app service plans:
Remote debugging: When you scale your app to PremiumV2, you will no longer be able to use remote debugging for your apps. If you scale your App Service plan to a lower tier, you will be able to use remote debug again.
https://azure.github.io/AppService/2020/03/23/PremiumV2-support-for-older-deployments.html
I've looked at the documentation for the new PremiumV3 app service tier, and can find no reference one way or another to remote debugging.
https://learn.microsoft.com/en-us/azure/app-service/overview-hosting-plans
https://learn.microsoft.com/en-us/azure/app-service/app-service-configure-premium-tier
Do PremiumV3 allow for the attachment of remote debuggers, and is there any indication of the long term strategy around this feature?
I span up a .NET 6 minimal API project, uploaded to a app service, changed the app service plan level, and where possible, attached a remote debugger from Visual Studio 2022 to observe a GET request.
I've tested each tier, and have the following results:
Tier
Remote Debugger Support
F1
YES
D1
YES
B1
YES
S1
YES
P1
YES
P1V2
NO
P1V3
NO
I have created an App service with V3 plan.
Deployed WebApp to the App service.
Tried to Attach debugger from Visual Studio,It changed the settings of Remote Debugging to On but unable to hit the break point.
Even there is an option of Remote Debugging in Azure Portal,the debugger is not attached to it.
Related
I am intending to enable logging in my Azure app. I am following the instructions by Microsoft on here, where they state to go to my app and select App service logs, but I see no such option for my app. This resource has the same instruction but I don't have that option. I am running on the Basic configuration for the app (the cheapest option), could that be the issue?
This is all I have under Monitoring (see image below)
What am I missing?
Which region are you running your app service on?
I just tried with Basic(B1) app service and I was able to configure app service logs
Seems like I had to upgrade to a minimum of Standard tier configuration to get the option to set up App Service Logs. It is Unfortunately about triple the cost of the Basic tier.
I just need to deploy a aspnet core app into a Linux Service Plan.
I tried pre-creating the Linux service plan (into it's own Resource Group) from portal, and then starting the publish profile creating process in VS, but it does not show the linux Resource Group or Service Plan.
I can only find references to doing this from a Linux machine using Git-integration.
Thanks in advance,
Jose Parra
Unfortunately, for now we cannot deploy web app to Azure linux service plan through VS. It's by design that we can only see windows service plan in VS publish process.
However there are alternatives for us to choose.
FTP-- Upload pre-compiled files(under ~/bin/Debug(Release) folder) to website. Here's the reference.
Local Git--You may have read this tutorial. Note that Git bash can also be used in Windows.
GitHub--Follow this reference to connect VS with your GitHub, then config Deployment option in portal. After that your code will be deployed automatically once pushed to GitHub.
There are some other deployment ways like CI/CD aka Continuous Delivery in portal and another source control tool BitBucket. I recommend you to use GitHub as it's simple to operate in VS after configuration.
I'm trying to automatically deploy from Team Services (was Visual Studio Online) after a successful build a C# program to an azure app service without success.
I can only do it to a cloud service (classic) rather app service.
I've seen that I could plug Team Services directly to the app service with "deployment source" (I did tried so far because both tenant, Team Services & Azure one are different and requires some effort)
but wouldn't it break the normal release / test process from Team Services?
I can only find little information over internet regarding these topics ...
Any help would be appreciated.
You can also add a FTP Upload task in your build definition to publish the output to Azure App Service via FTP Method.
To publish to an Azure App Service, you need to use either of the following Agent tasks:
Here is a walkthrough: https://www.visualstudio.com/en-us/docs/build/apps/aspnet/aspnet4-to-azure
When making a new build definition, it is easiest to choose the Deployment -> Azure WebApp option.
I can't find what is causing CPU increase to 100% daily at some periodical time. Is there any way like if you have VM, task manager in Azure dashboard?
I have telemetries:
You can remote debug your Azure app with Visual Studio :
When you enable remote debugging on an Azure virtual machine, Azure installs the remote debugging extension on the virtual machine. Then, you can attach to processes on the virtual machine and debug as you normally would.
https://azure.microsoft.com/en-us/documentation/articles/vs-azure-tools-debug-cloud-services-virtual-machines/#debugging-azure-virtual-machines
Also to try to understand what happened in the past: if you have activated Azure Diagnostics, you get the output logs in a Azure Storage that you configured for diagnostics. You can have a look at there to try to find what caused the problem.
You can integrate app logs to azure logs to get more accurate or specific info.
https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-dotnet-diagnostics/
You can also use 3rd party logs like log4net, ... (see appropriate extension or nuget packages).
I have a WorkerRole running as a Cloud Service. I want to debug it because when I call the service on Azure the calling application hangs.
I tried attaching the debugger to the remote service but it times out after 90 minutes of doing nothing. So, my next step is to run the service locally with the emulator, which I am now doing.
I have the emulator running but I have no idea how to connect to this local service and what the endpoint is. Can someone help?
To be able to debug your Azure cloud service (running in the cloud), you first need to make sure it is built with the Debug configuration and that the remote debugger feature is enabled, then you'll be able to attach to the role from Visual Studio as if you were running it locally.
To do the debugging locally, with the Azure Emulator, all you need to do is to run your cloud service project (F5 (if it is the default project) or right click -> Debug -> Start new instance).
You can follow these steps to enable the debugger and attach to the service (both locally and in the cloud): https://msdn.microsoft.com/en-us/library/azure/ff683670.aspx