When we deploy an ASP.CORE 3.0 on Azure we have this error:
The current .NET SDK does not support targeting .NET Core 3.0
Okay... but do you know when ASP.CORE 3.0 will be available in Azure App Service ?
Thank you
As of now its not deployed and no estimates are provided
But you should be able to do it your self
Install the preview site extension
From the Azure Portal, navigate to the App Service.
Select the web app.
Type "ex" in the search box to filter for "Extensions" or scroll down the list of management tools.
Select Extensions.
Select Add.
Select the ASP.NET Core {X.Y} ({x64|x86}) Runtime extension from the list, where {X.Y} is the ASP.NET Core preview version and {x64|x86} specifies the platform.
Select OK to accept the legal terms.
Select OK to install the extension.
The channel to get the best information about Azure Updates is:
https://github.com/Azure/app-service-announcements
But until now nothing has been posted there.
The MS Dev-Blog https://devblogs.microsoft.com/dotnet/announcing-net-core-3-0/ is saying that
Azure App Service deployment of .NET Core 3.0 is currently ongoing.
So I suggest you set up a watch on the github repo above to get notified once the work is done.
Work is in progress and will be available in some time. But No ETA at this point.
Related
As part of the build applications with Azure DevOps learning path, I have to deploy a .NET 5.0 app to the Azure WebApp Service. When setting up the instance, I no longer have .NET 5.0 available as an option, only .NET 6.0.
I have no experience and only basic programming skills, so I naively tried to build it on .NET 6.0 with no success. I reported the error to MS Learning, but the available channels to communicate with them are one way and I have no feedback on whether a fix will be implemented at any of the ends.
What are my options?
Is it viable to refactor to .NET 6.0?
Any leads to MS Learning on the issue?
Is there a way I'm not seeing to select .NET 5.0 like via az CLI or any other?
Thank you in advance for the help, and since these are my first questions I'm sorry if I skipped a guideline or etiquette. I will appreciate any tips.
Is there a way I'm not seeing to select .NET 5.0 like via az CLI or
any other?
One of the workaround to use ASP.NET 5 ,Once you have created App service you can download the extension .
GO TO APPSERVICE> EXTENSION> ADD> search ASP.NET5(32/64bit based on requirement) > Agree the policy> OK.
Then you will be see ASP.NET CORE 5 is there by navigating to ADVANCE TOOLS(KUDU CONSOLE)
BELOW ARE THE SCREENSHOT FOR REFERENCE:-
Click the "+" mark and go ahead and install the runtime in the app service. Then restart the site.
To create ASP.NET CORE 6 Application and deploy to AZURE Please refer this MICROSFT DOCUMENTATION
For more information please refer the below links:-
Blog Post|To run .net5 in Azure
SO THREAD|ASP NET Core 5.0 not supported in Azure
I spent many hours trying to find some way to create a new .NET Core 3.1 web app under Windows subscription. I found that if you pick up the Runtime stack as .Net Core 3.1 (LTS) the only option is to create an app under the Linux. I tried to play with different regions and Sku and sizes as well but for all cases, it's just the same. There is no option to configure App Insight during the creation time either when using the Linux.
The interesting thing is that when I created the Web App under .net core 3.0 marked as current I was able to deploy .net core 3.1 web app and it all worked including the app insights stuff.
My question: is it just a bug in the Azure UI that you cannot create .net core 3.1 web app under Windows or there is some specific reason behind it?
This option is going to be available once the deployment of .NET Core 3.1 has been rolled out to all AppServices worldwide. So far, this is only been completed for Linux.
https://github.com/Azure/app-service-announcements/issues/217
https://github.com/Azure/app-service-announcements-discussions/issues/129#issuecomment-565620039
Windows hosted App Service option will be enabled once world wide rollout of 3.1 SDK to App Service backend is complete.
Since Windows AppServices have all required runtimes installed, you can select 3.0 and try to deploy your app regardles of what the portal says. I was able to host a WebApi in west Europe this week with .NET Core 3.1, but from what I read that might just have been luck.
Deploying a self contained version is probably also possible from what I read in the linked Github issue.
edit2:Note that the accouncement talks about the SDK. As of the writing of this post, most of the app services have the 3.1 runtime installed, while the SDK will take a while longer.
edit:
You can also check manually if your AppService has the runtimes installed already:
Go to Kudu (https://myappservicename.scm.azurewebsites.net/)
Open the Debug console (e.g. CMD)
type in dotnet --list-runtimes
I had the same problem. I could not get windows selected in Azure.
What I did was let Visual Studio create the App in my App Services. (Note the app insights!)
When this profile finished creating I went into the created App in the Azure portal. Settings - Configuration and changed the stack from 4.7 to .Net Core (Sorry this is in dutch, I hope you can manage...)
And now I also had the standard documents available which I did not have creating it in Azure portal! I changed it to only have index as landing page :
After I did this the homepage of my website showed up. Hope this helps someone!
When using the latest version of the Application Insights(AI) SDK (at time of writing: 2.4.1) in code via NuGet, is the AI extension also needed on the web app extension list in Azure ?
You may either install the Application Insights SDK via NuGet, aka build time, or enable the Application Insights site extension through the Azure Portal, aka run time.
If you do both, the Application Insights site extension will not work even though it is turned on.
You can refer to the Azure Monitor documentation on Application Insights for more information.
No. The extension gives similar features as the SDK.
It is an option to use App Insights in an app without installing the SDK.
I wanted to install Azure 2.5 SDK for VS 2013 and that required updating VS 2013 to Update 3 or later. Update 4 was the recommended one so I installed it. Azure 2.5 SDK installation still broke at the same spot. When I checked about dialog in VS 2013 it said that my current version is 12.0.31101.00 Update 4 but my Extensions and Updates feature still offers me Update 4. When I select this update,Extensions and Updates window says that my current version is 12.0.21005.1 and new version will be the one mentioned above, 12.0.31101.00. Anyone had this kind of issue? Should I install some other version of Azure SDK?
Azure SDK 2.5.1 was released in March 2015. Along with support for Visual Studio 2015 Update 4 this release also updated the SDK for recent changes in the Azure Platform:
Azure Websites was renamed to Azure App Service.
Azure API Apps (Preview) support has been added.
The Websites node in Server Explorer has been deprecated.
Azure Mobile Apps (Preview) support has been added
Add > Azure API App Client gesture now supports local Swagger JSON files
Web App and API App publishing dialogs have been enhanced
Azure API App Server Explorer nodes provide links to the API Apps
There are a few known issues, so make sure you read those before you jump in.
I want to develop an application using appfabric composite application/model but i was unable to find any latest updates on it. Also very little help related to it is present on web thus creating a confusion that whether this feature is continued after June CTP 2011 or not ?
Is there any update going to be available in future release?
Also I have installed windows azure toolkit 1.7 and after that azure appfabric sdk1.5 but in visual studio project templates I cannot find any template for appfabric as shown in some videos.
What additional installables will I require ?
In Windows Azure, word "App Fabric" is not longer used, instead all the services which were part of "Windows Azure App Fabric *" are named completely different (Service bus, ACS, Cache * etc) specific to their objective. That why you do not see any latest documentation specific to "App Fabric" in Windows Azure. Now when App Fabric term is used specific to Windows Server specific service model.
That's another reason when you installed Windows Azure SDK 1.7 you did not see any thing specific to App Fabric at all.
I am not sure how much it will apply but you sure can take a look at "Building Hybrid Applications in the Cloud on Windows Azure - eBook" and see if that will help you.