Visual Studio 2022 can now Always Update on Close!

Sayyeda Mussa

Program Manager

Do you want Visual Studio 2022 to always stay up to date with the latest goodness with little-to-no action from your end? Then look no further, because as of now, we support the ability to “Always Update on Close”! Starting with Visual Studio 2022 version 17.5, we’ve made it easier to apply available updates when Visual Studio closes if you’ve made a one-time configuration change in Visual Studio. You can find this option in the Tools > Options > Product Updates dialog.

This setting is configurable on a per instance basis of Visual Studio 2022 and we highly encourage you to enable this feature to stay current, updated and secure. Then, you will be all set! For more information, please visit Update Visual Studio | Microsoft Learn.

Let us know your thoughts!

We would love to get your feedback on this feature, so please give it a try and let us know what you think. You can share any feedback via Developer Community to help us make Visual Studio better for you!

Topics

Author

Sayyeda Mussa

Program Manager

15 comments

Discussion is closed. Login to edit/delete existing comments.

Greg Tulenko April 7, 2023 · Edited

Absolutely not!
Half the time when I run updates, my projects have issues and I have to track down what the latest update did to break my projects. Having updates happen automatically on close would just add another layer of confusion and frustration.
Roberto Mencia February 27, 2023

In every update there are new bugs and it’s not always good to update your VS without being 200% sure that your stuff still works. So many times I’ve updated and something stopped working.
Better to check the change log and only update if something really needed. I.e: no need to update if working on asp.net and the fixes are on C++ and xamarin.
Nikolay Baklicharov February 26, 2023

To be honest, many times when I update VS, the project stops building(C++), because of some kind of compiler regression or other kind of "fixes". We had times when our Jenkins pipelines were always installing the latest version of VS build tools once per day, but sadly enough, we often got compile errors and a really quick fix had to be developed to unblock the builds...

Yes, I know that I can use the latest version of VS with older version of MSVC, but that does require additional work which kind of defeats the purpose...

My suggestions regarding the topic:
1. Make...
Read more
To be honest, many times when I update VS, the project stops building(C++), because of some kind of compiler regression or other kind of “fixes”. We had times when our Jenkins pipelines were always installing the latest version of VS build tools once per day, but sadly enough, we often got compile errors and a really quick fix had to be developed to unblock the builds…

Yes, I know that I can use the latest version of VS with older version of MSVC, but that does require additional work which kind of defeats the purpose…

My suggestions regarding the topic:
1. Make better regression testing and prioritize fixing(and backporting) regression bugs(I have reported such bugs myself which are not fixed for months…).
2. Make the update more seamless. Like, install everything on the background and next time when I launch VS, I’m directly on the latest version. Something like how the modern browsers are updated.

Read less
Stephen Jovanovic February 23, 2023

Not a bad idea. In fact its pretty good idea. Less work, and I’m into that big time!!!

Moreover, beats having to keep an eye on when updates and etc are they’re going to happen, and you don’t have to worry about missing any updates.