-
Notifications
You must be signed in to change notification settings - Fork 3.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
Add .NET Framework 4.7.2 SDK in the Windows 2022 image #10942
Comments
We're working on this issue , we will share the update ASAP. thank you ! |
Fixed in #10943 |
Hi @JoostVoskuil , thanks for the response, we look into it and update you ASAP. |
Hello @JoostVoskuil , could you please rebase your PR? We would like to test your changes and merge the PR if successful. |
Hi @Alexey-Ayupov it is rebased. |
HI @JoostVoskuil , sorry but I cannot approve your PR. It changes 68 files, it looks like rebase went wrong.
|
Hi @Alexey-Ayupov yeah something went wrong. Sorry |
Hi @JoostVoskuil , We're closing the issue as completed. thank you ! |
Tool name
Microsoft.Net.Component.4.7.2.SDK
Tool license
Free
Add or update?
Desired version
4.7.2. SDK
Approximate size
No response
Brief description of tool
Microsoft.Net.Component.4.7.2.SDK is not installed as part of Visual Studio 2022 within the windows 2022 image.
Some developments are still using it. Since Windows Server 2025 is GA, I expect that the Windows 2025 image is coming soon, slowly deprecating the windows2019 image. Without this issue we cannot build 4.7.2. anymore
URL for tool's homepage
https://learn.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-build-tools?view=vs-2022
Provide a basic test case to validate the tool's functionality.
Platforms where you need the tool
Runner images where you need the tool
Can this tool be installed during the build?
- Add "Microsoft.Net.Component.4.7.2.SDK" to the toolset.json under section visualstudio/workloads
Tool installation time in runtime
No response
Are you willing to submit a PR?
yes
The text was updated successfully, but these errors were encountered: