-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue running .net6.0 (arm64) under IIS on Windows 11 ARM64 - missing version '6.0.o' (arm64) #42699
Comments
Support for running ASP.NET Core on ARM64 IIS/IIS Express is new in .NET 7, so it's not unexpected that 6.0 doesn't work. Glad to hear that 7.0 applications are working for you. I don't know where the "6.0.o" came from though, that is weird 😄 |
I know it's brand new. That is why I wanted to share this info. I've updated VS to the latest 17.3 Preview 3 version (released today). Even though new SDKs are included unfortunately it is still looking for "6.0.o" version :(
If it helps, there is absolutely nothing else installed on my system - this is it's sole purpose at this point :) |
Can you share the contents of your [appname].runtimeconfig.json file? |
sure ... there it is:
|
Thanks for contacting us. We're moving this issue to the |
I tried this on one of our arm64 VMs and I don't see error message you are seeing, it still doesn't work, but I see an error message: HTTP Error 500.33 - Failed to load ASP.NET Core request handler with an event log saying it can't find the inprocess handler. Regardless net6.0 on arm64 isn't a scenario we are supporting |
Is there an existing issue for this?
Describe the bug
When trying to run a .net6.0 web application under IIS (InProcess) on Windows 11 ARM64 the following 500.31 error occurs.
The weird part is that it is searching for the "6.0.o" version (arm64) - with the letter "o" at the end.
The setup:
Meanwhile .net7.0 applications are working properly under IIS (InProcess) without x64/arm emulation enabled.
Only .net6.0 apps cannot start (with or without emulation), built with AnyCPU or dedicated for either x64 or arm64?
Apparently, this .NET SDK 6.0.400-preview.22301.10 installs the 6.0.5 runtime, at least it does according to the output of
dotnet --info
(see below).I've tried manually installing:
... but no luck :(
I cannot figure out why it searches for 6.0.o version (which is obviously not there).
Unfortunately, it doesn't look like you can uninstall the preview SDKs that ship with VS Preview, because that will basically uninstall the VS altogether.
Any ideas? What am I missing?
It would be great if I could run at least .net6.0 (arm64) apps like this, not to mention x64 or older editions.
stdout
log output at failed launch:Expected Behavior
Since .NET SDK (together with the installed runtime for arm64) is installed, I would expect that if a valid web.config configuration is presented - i.e. valid path to the executable that was built with AnyCPU or arm64 configuration, IIS would run the web application using the InProcess hosting model.
web.config:
Steps To Reproduce
Unfortunately, I believe this to be an SDK/Runtime issue so I'm not able to offer any steps except the following:
Exceptions (if any)
No response
.NET Version
7.0.100-preview.5.22307.18
Anything else?
I have the following .net stuff installed (note: .net7.0 apps work OK under IIS, .net6.0 apps don't)
dotnet --info
output:The text was updated successfully, but these errors were encountered: