reactiveui/splat

housekeeping: vs2022 go live CI changes

dpvreony opened this issue · 2 comments

Is your feature request related to a problem? Please describe.
When VIsual Studio 2022 goes RTM rather than delete the current update block out the CI action I was thinking

  • put a variable at the top of the build (or hide away in the repo settings)
  • put a run condition on the VS2022 update task
  • rename it to "Use Visual Studio Preview"

Describe the solution you'd like
as above

Describe alternatives you've considered
deleting it, remarking it

Describe suggestions on how to achieve the feature

Additional context
i suggested variable rather than repo setting due to the security on the repo settings, and it can be done on a long running branch etc without affecting main

Not something we need to secure really. So happy with the variable in the yaml myself.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.