Skip to content

UUF: Needs Windows version explanations #43055

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

Closed
gewarren opened this issue Oct 15, 2024 · 0 comments · Fixed by #45657
Closed

UUF: Needs Windows version explanations #43055

gewarren opened this issue Oct 15, 2024 · 0 comments · Fixed by #45657
Assignees

Comments

@gewarren
Copy link
Contributor

gewarren commented Oct 15, 2024

Type of issue

Missing information

Description

This page is opened when you click the ? icon against the 'Target OS version' and 'Supported OS version' in the Project Properties dialog/window in Visual Studio. The assumption would be it would actually show you what the values, ie 10.0.17763.0, corresponded to in the actual Windows. A table (like all the other tables on the page) which lists them Windows version ie Windows 10 22H2 etc. Either the page should be updated or the link needs to point to the actual page.

Page URL

https://learn.microsoft.com/en-gb/dotnet/standard/frameworks

Content source URL

https://github.com/dotnet/docs/blob/main/docs/standard/frameworks.md

Document Version Independent Id

4352856b-5ccf-8e62-48b4-3151340cac56

Article author

@gewarren

Metadata

  • ID: 49205137-dcec-a120-e5e7-1b9c79cdafbb
  • Service: dotnet
  • Sub-service: standard-library

Related Issues

@dotnetrepoman dotnetrepoman bot added the ⌚ Not Triaged Not triaged label Oct 15, 2024
@BillWagner BillWagner removed the Pri1 label Jan 22, 2025
@gewarren gewarren added the user-feedback Issues related to "Unified User Feedback". label Mar 17, 2025
@gewarren gewarren self-assigned this Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants