Is it possible at this time (end of February, 2019) to deploy a .net core v3 beta backend to azure? I'd like to update some of my play stuff to .net core v3, but I only use it via azure I'm specifically looking at an azure web app that is currently running windows.
TIA.
You can install the runtime as an App Service extension. Look for "ASP.NET Core 3.0 (x86/x64) Runtime"
Related
When deploying a .net core 3.1 app by using the Deployment Center (in App Service), I got the following
failed error:
"error NETSDK1045: The current .NET SDK does not support targeting .NET Core 3.1. Either target .NET Core 2.2 or lower, or use a version of the .NET SDK that supports .NET Core 3.1"
It was fine for me to deploy .net core 2.1 app in the environment. What should I do to resolve the issue?
I found an answer to my question. The SDK (.net core 3.1) is not deployed in App Service yet.
According to the following post, it should be there soon.
https://github.com/Azure/app-service-announcements-discussions/issues/129#issuecomment-569997549
Problem
After upgrading a .Net Core 2.2 Linux Web App to .Net Core 3.1 in Azure, the application is down with a Specified framework 'Microsoft.AspNetCore.App', version '3.1.0' was not found error. I even went as far to create a new Linux Web App with .Net Core 3.1, and after the bash command prompt is still outputting dotnet --list-runtimes as 2.2.7.
Details
Website Down
Logstream
reporting application is down because it can't find .net core 3.1.
Created new .net core web app
3.1 linux webapp in North Central, same problem
Ensured it was running in North Central US
According to https://aspnetcoreon.azurewebsites.net/, should have full .netCore 3.1 support
Still .net core 2.2.7
opt/dotnet/runtimes lists 3, 3.0 and 3.0.0, but no 3.1`
Environment variables
My environment variables in Azure list FRAMEWORK_VERSION = lts, instead of 3.1
Publishing
This was published from an azure devops ci pipeline using an Azure AppService Deploy task. 3.1 wasn't available here, so I chose LTS
Update 1
It seems the culprit is 3.1 missing from the framework stack in Azure Devops Web App / Web Service tasks.
Whenever I publish from CI, the web app framework is updated to whatever is selected in this dropdown. If I manually go change the framework to 3.1 on the Azure Web App, the site comes up. But then the next publish it goes back down because it reverts the framework back to the settings in the ci.
New Question
How can I get the Azure Devops Release pipeline to publish a .net core 3.1 task?
Update 2
Related Azure Devops forum post
Currently being investigated as of 2/23/2020
.Net Core 3.1 deploy pipeline to Linux App Service
Suggested Workarounds
Use YML for release pipeline and manually change the version from 3.0 to 3.1, noted by answer and this thread
Upgrade from a framework dependent release to a self contained. Reference
Downgrade to .NetCore 3.0
I've run into the same situation, using the information you provided I've been able to fix the issue by setting the value manually in the Devops Pipelines Build .yml file. It seems like they are just missing the value from RunTime Stack drop down. If you manually update the build processes .yml file as seen here:
This will select the proper framework version. Hopefully this will fix your issue with the Azure Devops CI Pipeline deployment.
An easier solution is to type DOTNETCORE|3.1 into the Runtime Stack dropdown in devops. (Thanks rdavisau!)
With the release of .NET Core 3.0, the latest version of visual studio offers the gRPC Service template to create this type of service.
Does anyone have idea what are my choice to host this kind of service (written in .Net Core 3.0) on the web?
Does Azure have a solution to this?
You can create a kubernetes cluster on Azure and deploy your application on it. Azure App Services doesn't support gRPC. If you want to learn how you can create your first service in gRPC follow this article:
gRPC service in .Net Core
i have an asp.net core app who works correctly on my computer but not on azure app service:
In one of my api, i return a dynamic type.
from the api runed on my computer i got (with .net core version : 1.0.1):
{"id":2,"color":"#3da1e8 ","logo":"","name":"...","companySecurities":[]}
from the api runed on azure app service i got (with .net core version : 1.1.0-preview1-001100-00):
{"id":2,"color":"#3da1e8 ","logo":"","name":"...","companySecurities":[]
You can see the the last bracket disapear on azure app service.
I want to know if there is a way to change the .net core version of azure app service to 1.0.1 .
I am not sure if I download Azure SDK 2.7 will it let me target .NET 4.5.2? Currently I have Azure SDK 4.5 and it does not let me publish when I have a worker role targeting 4.5.2.
Thanks
Worker roles currently do not support .NET 4.5.2 without manual installation.
You can either set up VM access to install .NET 4.5.2 onto the worker role's underlying VM or look at usin a powershell script to install it when your application starts up.
See proof in release notes for SDK 2.6 and instructions to how install .NET on cloud services here.
Azure SDK's currently only allow you to target 4.5.1 in PaaS services. Azure SDK v2.5 and on is able to to target 4.5.2 but only if it is a VM instance
https://msdn.microsoft.com/en-us/library/azure/dn873976.aspx