Our developers prefer to use Visual Studio 2019/2022 environments, too. We switched using CMake for our implementation projects as @JamesBallard1 suggested. I know CMake is a different beast - especially when it comes to caching and multiple configurations - but migrating to the new version 200.x being based on Qt6 worked like a charm for our projects. We still see some issues with CMake and caching in the VS environments in more complex scenarios like compiling the Qt Maps SDK using vcpkg e.g. with pybind11 into a core foundational Python module, because our data engineers love to use Maps SDK functionality in their Python environments. So that, we setup a new project or solving issues for existing projects using Qt Creator with CMake and then switch back to Visual Studio.