When will .NET Core 8 web apps run on Azure?

Question

When will .NET Core 8 web apps run on Azure?

Aaron Smith 90

I'm testing out .NET Core 8 and trying to deploy to Azure.

I created a new Blazor web app in Visual Studio.

I go to publish the app, creating a new Azure Web App.

Once published, I see "HTTP Error 500.31 - ANCM Failed to Find Native Dependencies" in the browser.

In Azure, I look at the .NET version in 'Stack Settings'. It's set to: ".NET 7 (STS)".

I change it to ".NET 8 (LTS) (Early Access)" as it's the only version higher than 7.

Save, restart app.

Now I get: "HTTP Error 503. The service is unavailable.".

Am I missing something here?

https://blazorapptest20231118153927.azurewebsites.net/

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Anonymous

2023-11-20T02:11:19.94+00:00

Hi @Aaron Smith,

Could you share us the detailed steps about how to create/deploy the project ?
I tried and failed to reproduce the issue, and it should support now.

Ken Kam Hung, Lin has shared you before.
https://azure.github.io/AppService/2023/11/14/dotnet8-ga.html

Best Regards

Jason
Aaron Smith 90 Reputation points

2023-11-20T11:50:38.9033333+00:00

Sure, here's the steps - nothing unusual - just clicking the next button mainly
Humz Singh 0 Reputation points

2023-11-20T12:04:58.3133333+00:00

I am also getting the above issue, just to add if I do another deployment after the above steps it automatically changes the .NET version back to .NET 6 (LTS). Loading the page then gives me an error along the lines of "ANCM Failed to Find Native Dependencies".

I can get the site to deploy and run if I set it to self contained, however once I swap to CI/CD using GitHub actions I end up with the same issue as above again.

Hope this helps find a solution to the problem if the extra information matches.
Anonymous

2023-11-21T08:57:14.23+00:00

Hi @Aaron Smith,

I follow your steps and tried again. Still can't reproduce the issue.

Ok, now the only different is the region I think, I am using East US, could you kindly check and try it again.

Thanks for your trying.

Best Regards

Jason
Aaron Smith 90 Reputation points

2023-11-21T11:11:47.8666667+00:00

Hi Jason

Region seems to be the problem. If I publish to a resource group in East US, it's fine.

If I try and publish to UK South I get this:
Physx 0 Reputation points

2023-11-21T22:07:13.3066667+00:00

I got the same problem. Region: West Europe
David Braverman 0 Reputation points

2023-11-28T16:35:08.1166667+00:00

With a new .NET version coming out every November, and many of us wanting to keep as current as possible, and many of us having 2-week sprints or continuous deployment scenarios, this is very frustrating.

We have some App Services in US East that updated to .NET 8 fine. We have almost identical assets in US Central that are getting 503s. (Fortunately only our dev environments for now.)

How long after each version's mid-November release date should we plan to, you know, use the new bits?
Aaron Smith 90 Reputation points

2023-11-28T17:22:21.31+00:00

I've been told this thread will get updated when things happen: https://learn.microsoft.com/en-us/answers/questions/1434518/when-will-net-core-8-runtime-rollout-to-all-region

Accepted answer

2 additional answers

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Anonymous

2023-11-20T02:11:19.94+00:00

Hi @Aaron Smith,

Could you share us the detailed steps about how to create/deploy the project ?
I tried and failed to reproduce the issue, and it should support now.

Ken Kam Hung, Lin has shared you before.
https://azure.github.io/AppService/2023/11/14/dotnet8-ga.html

Best Regards

Jason
Aaron Smith 90 Reputation points

2023-11-20T11:50:38.9033333+00:00

Sure, here's the steps - nothing unusual - just clicking the next button mainly
Humz Singh 0 Reputation points

2023-11-20T12:04:58.3133333+00:00

I am also getting the above issue, just to add if I do another deployment after the above steps it automatically changes the .NET version back to .NET 6 (LTS). Loading the page then gives me an error along the lines of "ANCM Failed to Find Native Dependencies".

I can get the site to deploy and run if I set it to self contained, however once I swap to CI/CD using GitHub actions I end up with the same issue as above again.

Hope this helps find a solution to the problem if the extra information matches.
Anonymous

2023-11-21T08:57:14.23+00:00

Hi @Aaron Smith,

I follow your steps and tried again. Still can't reproduce the issue.

Ok, now the only different is the region I think, I am using East US, could you kindly check and try it again.

Thanks for your trying.

Best Regards

Jason
Aaron Smith 90 Reputation points

2023-11-21T11:11:47.8666667+00:00

Hi Jason

Region seems to be the problem. If I publish to a resource group in East US, it's fine.

If I try and publish to UK South I get this:
Physx 0 Reputation points

2023-11-21T22:07:13.3066667+00:00

I got the same problem. Region: West Europe
David Braverman 0 Reputation points

2023-11-28T16:35:08.1166667+00:00

With a new .NET version coming out every November, and many of us wanting to keep as current as possible, and many of us having 2-week sprints or continuous deployment scenarios, this is very frustrating.

We have some App Services in US East that updated to .NET 8 fine. We have almost identical assets in US Central that are getting 503s. (Fortunately only our dev environments for now.)

How long after each version's mid-November release date should we plan to, you know, use the new bits?
Aaron Smith 90 Reputation points

2023-11-28T17:22:21.31+00:00

I've been told this thread will get updated when things happen: https://learn.microsoft.com/en-us/answers/questions/1434518/when-will-net-core-8-runtime-rollout-to-all-region

Answer 1

Anonymous

Hi @Aaron Smith,

Glad we found the cause of the problem.

Because now. .NET 8 is still in the Early Access phase, and some regions should be in beta, and when there are no problems when it is stable, it will be deployed in every regions.

So please be patient and wait for the App Service Team update.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best regards,

Jason

Aaron Smith 90 Reputation points

2023-11-22T10:02:44.19+00:00

Hi Jason

Great, thanks for the confirmation. I think moving forward it might be advisable to make it clear that the actual roll-out is regional as I'm clearly not the only person encountering this issue and to my knowledge it isn't documented anywhere. Furthermore, do you know how I might know when my region is ready for .NET 8? I can just keep using the VS publication warning, but is there anywhere this information is published?

Thanks again!
Anonymous

2023-11-22T10:10:26.93+00:00

Hi @Aaron Smith,

It's better to create a new thread with Azure App Service tag without any other tags, like asp.net core.
And app service team will check the thread. You also could create the support ticket and ask for help.

Best Regards

Jason
Aaron Smith 90 Reputation points

2023-11-23T17:19:13.1066667+00:00

I've created a new thread/question:

https://learn.microsoft.com/en-us/answers/questions/1434518/when-will-net-core-8-runtime-rollout-to-all-region

Answer 2

CB 5

I have the same problem for UK regions. I'm amazed that Visual Studio is actively prompting the download and upgrade of .net 8.0, yet most of the Azure application regions cannot handle this yet. I am now having to go through a very painful rollback process on a large application.

It would be hugely helpful to understand when .net 8.0 support is going to be available in the different regions

Aaron Smith 90 Reputation points

2023-11-23T16:03:29.99+00:00

I very much agree! I did my rollback a couple of days ago. Wasted time.
Anonymous

2023-11-30T10:50:18.4133333+00:00

I had the same issue.

For the time being, i've deployed the application as 'self-contained' which will ship the .net 8 runtime along with the app.

It's not the best solution but it will allow the application to run in lieu of the regions being updated.
Aaron Smith 90 Reputation points

2023-11-30T10:57:54.4+00:00

I've tried the "self-contained" option. It worked for our simpler background application, but it didn't work on our larger application! It just timed out eventually so had to rollback again!
CB 5 Reputation points

2023-11-30T11:14:44.3366667+00:00

You can trim down a self-contained deployment to try to make it a bit smaller. Some tips are here: https://learn.microsoft.com/en-us/dotnet/core/deploying/trimming/trim-self-contained

If it is a larger application with quite a few 3rd party dependancies then it may not work. I currently could not get the .Net 8.0 app to fully build and deploy in self-contained mode as some of the 3rd party dll's etc are causing issues.

Unfortunately we are all stuck waiting for Microsoft to deploy a framework that it is says is live but in reality is effectively a POC launch in a few places only.

Answer 3

SnehaAgrawal-MSFT 22,706 Moderator

Update- Early access label is removed from Portal for .NET 8 and with this there are no more open items for .NET 8. User's image Please let us know if further query or issue remains. Please accept as "Yes" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.

Share via

When will .NET Core 8 web apps run on Azure?

2 additional answers

Your answer