Open softwaretirol opened 9 months ago
Hi @softwaretirol , thanks for reporting, currently we are working on more prioritized issues, we will get back on this soon.
I was upgrading our clients to .NET 8 just to find out the release pipelines don't support it. Kind of crazy considering this is maintained by Microsoft...?
Runtime Stack is an editable field and is of type string
. In the meantime you can enter DOTNETCORE|8.0 and it will work.
Hi @v-mohithgc, I'm happy to work on this if you can assign this to me.
@amitjaura thanks, that works!
Is it "DOTNET-ISOLATED|8.0" for azure functions then?
@evaldas-raisutis, I left if blank and it worked fine.
Manually editing the field and changing the 7's to 8's actually unsets the configured stack in the Azure App Service configuration after a release, don't do it!
Just another instance where I get slapped for upgrading to newest version.
I was trying to use .NET 8 isolated, and thought I'd be ok given this statement in the docs:
If there is a newer version of a framework available in the supported runtime versions you can specify it even if it is not in the list.
During deployment, I got errors about a bad request (.NET 7 isolated works fine). I guess .NET 8 isolated needs to also be supported by the task, not just Azure Functions.
Please fix this ASAP!
Any idea when this bug will be fixed?
@v-mohithgc just checking to see if you have any updates on this
Looks like this task uses this API
to get the list of runtimestack, at the moment it doesn't have the Dotnet core 8 version support. I've reached out to some contacts to see if we can get an updated api. I'll keep this chat updated if i get any updates
How this is not a high priority ?!! Please fix..
For app services, setting the Runtime Stack manually works:
Task name
Azure App Service Deployment: ARM - .NET 8 Support
Describe your feature request here
Currently it seems .NET 7 is the highest available version for the runtime stack.
.NET 8 is already released and should be supported.