When configuring an Azure App Service backend you can choose between either a managed NodeJs project that works with EasyAuth and EasyTables or a full .NET based backend project that you can download and work with.
This project is based on an ASP.NET MVC template using .NET Framework 4.6.
When you want to integrate the Azure NotificationHub, you need to add nuget package references to Microsoft.Azure.NotificationHubs which target dotnetstandard2.0.
How can I either integrate the NotificationHub into my existing .NET backend project or migrate my .NET Framework 4.6 based backend project to dotnetstandard?
d'oh.
As stated on Microsofts compatibility page, dotnetstandard2.0 requires .NET Framework 4.6.1. The template, an Azure App Service .NET Backend is based upon targets .NET Framework 4.6. So migrating this to 4.6.1 solved my problem.
Related
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!
I recently upgraded my ASP .Net Core 2.2 Web API to .Net Core 3.0.
Now, when I publish to Azure App Service from within Visual Studio 2019 Community (latest updates installed) I get this message:
There was a problem starting PropWorx.API on propworx-api-san.
Your application requires the .NET Core 3.0.0 runtime, but Microsoft Azure App Service only supports the following versions: 2.1.12, 2.1.13, 2.2.6, 2.2.7 and 3.0.0.
Yet, the API appears to work just fine once deployed. Is this something I should be concerned about?
Don't worry much about it as its just a warning, You can keep track on the latest releases on the ASP.NET Core on App Service Dashboard
I have MVC web application developed on dotnet framework 4.5.2 . This application has database in MS SQL server. I want to move DB from SQL server to GCP. Does .Net framework 4.5.2 support GCP? Or i will have to rewrite application in dotnet core with MVC .
I have gone through several blogs many of them has contradictory conclusion but all of these blogs specify that dotnet core supports GCP and hence I am not able to reach on conclusion whether dotnet framework 4.5.2 supports GCP or not. Does anyone has idea about this or any reference.
There are some diferentes ways to deploy an app in GCP. You can take a look in the following official documentation Compute Engine with .NET, App Engine with .NET, Kubernetes with .NET and APIs and .NET.
Regarding the switch from the Katana / Web API project template to ASP.NET Core for Service Fabric in Visual Studio 2017 that happened around April Vaclav Turecek made this comment on a post...
Katana was largely a prototype for what would become ASP.NET Core. Most, if not all, new feature work is going into ASP.NET Core, not Katana, and ASP.NET Core is officially supported by Microsoft.
Does this mean that the previous project template that used Katana / Owin is not officially supported by Microsoft?
How critical is it to migrate any Azure Service Fabric services we wrote using that old template to the new ASP.NET Core template?
Are the old Katana based services acceptable for production?
If we continue to use these old services should we expect any issues? For example, what about automated deployments with Team Services? ASP.NET Core doesn't require XML transforms for it's configurations during deployment but the older Service Fabric template uses web.config so it does. Can we expect this to cause headaches that migrating to ASP.NET would cure?
How do I add .NET Core class library reference in Service Fabric App.
While I'm adding Class Library reference (.NET Core) in WebAPI app, showing Compatibility issues. Please find below What I did, using Visual Studio 2017.
File >> New Project >> Cloud >> Service Fabric Application
Name - FirstServiceFabricApp
Select a Template >> Stateless ASP.NET Core
Name - FirstStatelessAPI
Build and Run the Project. It works.
Although API Project Framework version is .NET Framework 4.5.2.
Added Class Library Project [builds on .NET Core 1.1] as reference into Stateless WebAPI Project. Showing compatibility issues-
Building the solution x64 platform.
My concerns are:
How do I take .NET Core Library reference in Stateless WebAPI Project [Service Fabric]
Should I go/develop with .NET Framework for Class Library which is compatible with Stateless WebAPI project.
I did Azure AD Authentication/Microsoft Graph in Azure APP Service, but never did for Service Fabric App. Whether Azure AD and Microsoft Graph implementation is same in this Stateless WebAPI App. Kindly provide some references on this.
You need to make your class library target a compatible framework e.g. net452 (or netstandard2.0 when it's supported like 2017 Q3)
The below link talks about converting a .net core to azure service fabric application.
It talks about statefulservice. Statelessservice is more or less similar to it.
http://dotnetextensions.blogspot.in/2018/04/convert-dot-net-core-application-to.html?m=1
When it comes to azure ad, i won't have much impact. You can continue to use the same thing