We just upgraded to 8.1 of asp.net zero and have some trouble to host asp.net zero on a linux app service with .net core 3.1. Currently Microsoft dont allow support for .net core 3.1 on their app service hosted on windows. Only linux based app service support .net core 3.1 at the moment.
We have a couple of asp.net zero applications running on windows app services in aure, is there anything different you need to do or think of when deploying to a linux app service in azure? Other build settings etc?
5 Answer(s)
-
0
Hi @webking
Have you solved this problem ? We didn't know about this problem until a few days ago. Did you solve this problem ? I have followed the discussion on https://github.com/Azure/app-service-announcements-discussions/issues/129 but couldn't understand what is the latest situation.
-
0
Hello @ismcagdas! Yeah, we managed to solve the issue after a while. We had to set the following arguments when publishing the build pipeline in azure to "-r win-x64 --self-contained true". And after the asp.net zero can run as a self contained application built on .net core 3.1 on a windows app service.
-
0
Great to hear that :).
-
0
I am currently running it all on an Azure App Service Linux setup with .Net Core 3.1
The only issue I've encountered so far is where images are uploaded (profile picture). The current code uses system.drawing.common and this depends on libgdiplus.
I cannot actually get libgdiplus to work even after installing into the host through SSH (for testing purposes). In prod version in my startup I detect if I'm running on Linux and run a custom install.sh script which installs a bunch of apt-get packages needed for other third party libraries I'm using. They all work fine. libgdiplus will not.
Also based on this link https://www.hanselman.com/blog/HowDoYouUseSystemDrawingInNETCore.aspx
I suspect ASP Zero should probably move away from using system.drawing.common if they can :)
So you should really have no problems running this on the Linux App Service.
Cheers
-
0
@rickfrankel thanks, I will check that and create an issue on AspNet Zero repository.
