Yes, this is what I've figured out to do. It's inconvenient because I'll have 3-4 SE editors open with different msbuild settings, so I have to make sure that if i open a project, it is in the SE instance that uses the correct msbuild environment. Creating a shortcut to call vsvars64 of the right version to do this is annoying because it leaves a small dos shell instance open on the tool bar. That may not sound bad, and it isn't the end of the world, but I have a BUNCH of command windows open too, so it's confusing. I'll write something to handle this (set the environment, spawn SE, and then terminate), I guess, but it's a small quality of life issue. It would be nice to associate the msbuild environment with the project, so that when I open the project, it chooses the correct toolset. This is mostly a minor annoyance except for WSL2 projects, where VS2022's build environment is much, much more pleasant for WSL builds. (VS2019 requires some mildly annoying setup per machine to work in WSL, while VS2022 just works when I move the project between machines.)
