Added UWP to the .NET Implementations list #47097
Conversation
dotnet-policy-service
bot
added
dotnet-fundamentals/svc
community-contribution
| @@ -79,6 +79,7 @@ There are multiple variants of .NET, each supporting a different type of app. Th | |||
| * **.NET Framework** -- The original .NET. It provides access to the broad capabilities of Windows and Windows Server. It is actively supported, in maintenance. | |||
| * **Mono** -- The original community and open source .NET. A cross-platform implementation of .NET Framework. Actively supported for Android, iOS, and WebAssembly. | |||
| * **.NET (Core)** -- Modern .NET. A cross-platform and open source implementation of .NET, rethought for the cloud age while remaining significantly compatible with .NET Framework. Actively supported for Linux, macOS, and Windows. | |||
| * **UWP** -- UWP is an implementation of .NET that is used for building modern, touch-enabled Windows applications and software for the Internet of Things (IoT). It's designed to unify the different types of devices that you may want to target, including PCs, tablets, phones, and even the Xbox. | |||
There was a problem hiding this comment.
UWP is not the correct name to use here. The other doc is wrong as well. UWP Is Windows technology, not specific to .NET. .NET that runs on UWP is called .NET Native.
.NET Native is no longer developed, and we are encouraging users to migrate to .NET Core that runs on UWP as well.
Given that this is intro doc, I do not think it is an improvement to mention .NET Native and UWP in it. This list does not have to be complete.
Instead, I would delete the section about UWP from https://learn.microsoft.com/en-us/dotnet/fundamentals/implementations to resolve the issue.
There was a problem hiding this comment.
Yeah this feels a bit off. The list is titled ".NET implementations", but the whole point of modern UWP is that it just uses the same .NET as everyone else. If we want to mention UWP (which I think doesn't hurt), I think it would be better and more accurate to just edit the previous item, so that it ends with:
"Actively supported for Linux, macOS, and Windows (including UWP)."
Thoughts?
There was a problem hiding this comment.
"I would delete the section about UWP from https://learn.microsoft.com/en-us/dotnet/fundamentals/implementations"
Not entirely sure about that specific part, just because .NET Native is still officially supported for production, and receiving security updates. And there's still plenty of customers using it. If we removed it from there it might send the wrong message (i.e. that it's deprecated, which it isn't) perhaps?
Also cc. @tommcdon for that one since he owns it 😄
There was a problem hiding this comment.
Not entirely sure about that specific
We can leave out "supports" and just talk about main .NET implementations like in this doc.
Also, Microsoft does not support Mono anymore so that part is incorrect too.
Summary
This pull request is a fix to the issue #47096 (only if the omission of the UWP is a mistake).
Internal previews