Extension is incompatible with .NET Core 3.x on New AppService

[robertmclaws]

So, I've been having problems getting this extension working on and off for the last few months. I haven't been able to figure out what the problem is, only that I've occasionally had to delete my whole Azure AppService and rebuild it.

Well, today I figured out the problem. If you have a brand new AppService, that does not have an app deployed yet, install the .NET Core 3.1 Extension, and then this extension, and try to run this extension to configure the service, the extension will fail. Specifically, you will get a "Task has been cancelled" error without any further details, and will have to turn on Application logging if you want any more info.

It turns out, because .NET Core takes over the web.config in the root, the Static File Handler will be turned off, and it won't be able to serve up the file from the .well-known folder. Once I uninstalled the .NET Core extension, everything worked fine.

The instructions either need to be updated to tell users not to install .NET Core first, OR the extension needs to be updated to detect if .NET Core is installed, and install a different runtime.

[sjkp]

thanks for the heads up. I'm probably not going to rewrite the extension to use .net core, as it seems Microsofts intentions are to replace it with built-in functionality. I will see if I can come up with a warning instead.

[audacity76]

Just upgraded a running .NET Core 2.2 web app to version 3.1. Installed the .NET Core 3.1 extension (x86) and ran the the extension (Version 1.0.4) - no problem, I was getting a new certificate.

[YetAnotherDev]

I also just installed the extension for the first time on a new .net core 3.1 site. no issues get the first cert.

[YetAnotherDev]

I also just installed the extension for the first time on a new .net core 3.1 site. no issues get the first cert.

it didnt auto renew, but i was able to go into the extension and renew it manually.