This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 30%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESL%3C/text%3E%3C/svg%3E)
Dotnet 6 is now EOL. The current version of Visual Studio 2022, 17.12, requires Dotnet 6 to install the Windows application development workload.
Who's responsible for for this workload in VS 2022?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hello @Sean Lively ,
Thank you for taking time to post this issue in Microsoft Q&A forum.
Yes, I see the same situation on my side. I’ve raised a ticket here: .NET 6 is EOL, but is still needed for installing and using "Windows application development" workload in Visual Studio 2022.
Please kindly follow up that ticket and if there’s any update, I will inform you as soon as possible.
Update1:
Here's a similar/same ticket => Please remove the .NET 6 dependency of WinUI development component which has been escalated for further investigation. I shared it here for reference.
Update2:
A fix for this issue is now available in preview release. Currently, you may try the latest preview version of Visual Studio 2022(Visual Studio 2022 version 17.13 Preview 3).
Update3:
Visual Studio 2022 version 17.13 was released on February 11, 2025.
According to this ticket: Please remove the .NET 6 dependency of WinUI development component, this issue has been fixed in Visual Studio 2022 version 17.13.
Please try to update Visual Studio 2022 to the latest version.
Thank you for helping us make Visual Studio better, have a nice day!
Sincerely,
Tianyu
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Sean Lively,
As the status of the Developer Community ticket which I reported is currently still triaged, may I know if you have any further concerns? Please don't hesitate to let us know :)