-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
.NET 6 Preview 1 #5967
Comments
Not the most pressing issue -- is there a reason Linux repositories are x86_64 only? This has been the case for past releases, but there was talk that it could change for 6: |
Great question/topic @lmcdougald. We are working on adding additional repositories (Arm64, Alpine, and previews). Thanks for raising this. The feedback legitimately helps. |
@lmcdougald the work add additional packages for Arm64 is tracked with this .NET 6 issue: #5446 |
Where do I go to find out more about .NET 6 and Windows Store Apps? |
@mandalorianbob Depends on what exactly you're interested in, but you may wish to check the WinUI roadmap and this Project Reunion thread. As of this time, I believe there is no public ETA for being able to run UWP apps in .NET 5 or 6. |
Yeah I'm interested in being able to run UWP apps in .NET 6, so I guess that answers the question haha. I'm also posting inquiries to Project Reunion. |
On the subject of .NET 6, I think it might be a good idea to take a look at this for possible implementation. Should be relatively effortless of an upgrade: https://github.com/thpatch/win32_utf8 Additionally, I'd look into adding native support for things like Large Memory Pages, Ravioli Memory, and OpenACC/OpenMP. This way, people migrating to .NET 6 would get these features right out of the box! |
Unless I’m mistaken the feature window probably won’t be expanding much at this stage.
Also, .NET 6 is supposed to be a clean recompile from .NET 5 supposedly (unless that promise is dead) so I’d expect the UTF8 change to be a non-starter as well.
|
I was more referring to the fact that it's a drop-in replacement for stdio.h / windows.h, which transparently turns ANSI and UTF-16 Win32 functions into UTF-8 versions... and as an added bonus, also helps troubleshoot various compatibility issues by giving you error messages that are actually helpful. Also, because you're just importing a library, and swapping a couple of include lines... It really is a pretty trivial thing, IMHO. |
Closing in favor of #6057 |
Release Notes
Please report any issues you find with .NET 6, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:
Known Issues
If there are any issues with this release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.
The text was updated successfully, but these errors were encountered: