What is our primary use case?
The main use cases for Visual Studio Professional 2022 are somewhat diminished compared to before. Previously, it had a significant advantage for C++ developers because it had an edit and continue feature, which is unique. Java has a similar feature called hot reload, and Visual Studio and Microsoft compilers allowed for similar functionality on C++, but despite it still being declared, it does not work in most cases recently, probably because of CMake and maybe a conflict with the edit and continue feature.
Currently, the most significant advantage is the convenience of running tests, with good filtering of test results and a good view, but there are not many advantages for C++ professionals.
How has it helped my organization?
The key benefits I have seen from using Visual Studio Professional 2022 include resolving conflicts in Git and, since edit and continue is no longer functional, advanced test view and test running. It supports parallel test running and allows viewing test results during test running, which somewhat optimizes my workflow. It allows me to debug particular tests and filter enabled and disabled tests, letting me see which tests can be enabled again after fixing, which is probably the best advantage in terms of performance.
What is most valuable?
I have used the IntelliSense feature in Visual Studio Professional 2022 a lot and think it is a very good feature. However, in the modern world, Clangd, which is from the LLVM compiler toolchain infrastructure, serves C++, C, and C++ and provides good information similar to IntelliSense, but more precise, as it uses a program database, which IntelliSense also utilizes.
I find refactoring capabilities in Visual Studio Professional 2022 to be a very good feature with multiple ways to refactor code, but unfortunately, lately, those features have degraded. It is interesting that some features of Visual Studio just stop working for C++ while keeping working for C#, indicating that the focus has switched to C# and TypeScript and is losing focus on C++, unfortunately.
I do use Git source control in Visual Studio Professional 2022, and some feedback regarding Git source control has caused improvements in the UI. Visual Studio has pretty good support for Git conflict resolving features, but it still does not support rebase, so this user experience is not solid and still requires the console to use Git.
What needs improvement?
Apart from the editing feature, I would like to see improvement in Visual Studio Professional 2022 because performance has dropped significantly, making it currently about 100 times slower than Qt Creator, which is unreasonable to use in a multi-core environment such as the 128 cores that I use.
On Windows, Visual Studio does not provide much of a performance gain, so for professional developers, Ubuntu with some KDevelop or at least Visual Studio Code or Qt Creator gives much better results.
Configuring a CMake project takes about a couple of minutes in Visual Studio Professional 2022, while the same project takes about 10 seconds in Ubuntu.
Apart from the editing feature, performance, and IntelliSense in Visual Studio Professional 2022, the most important missing aspect is that the focus on maintaining existing features has been lost. Feedback processing should be restored or improved. Features and feedback are being closed before being addressed, with timeouts of a couple of weeks and months, closing feedback regardless of its importance. I wonder if they began editing use cases or stopped tracking whether test cases passed or not, which should be controlled somehow.
For how long have I used the solution?
I have been working with Visual Studio Professional for more than five years in total. Regarding Visual Studio Professional 2022, I had it recently, but currently, no. During the past year, I did have Visual Studio Professional 2022 and worked with it.
What do I think about the stability of the solution?
Regarding the stability and reliability of Visual Studio Professional 2022 on a scale of one to ten, I think that stability and reliability are different marks. Given that features are disappearing, I would rate reliability as a three out of ten, while stability is pretty stable and does not crash much, so I can give it an eight or nine.
What do I think about the scalability of the solution?
Regarding scalability in Visual Studio Professional 2022 in terms of code size and how big the project is, I find it pretty scalable and would rate it as an eight or nine.
How are customer service and support?
Concerning technical support and customer service for Visual Studio Professional 2022, I have tried to create feedback several times, and unfortunately, I can say that if it yields results, the process remains silent from my perspective.
I feel it is a team that can be safely removed from the company without any changes, so I would rate them as one, given that zero is not an option.
How was the initial setup?
The setup process for Visual Studio Professional 2022 is quite advanced; I think it is one of the best on the market as it allows me to select features.
However, I am not sure about the safety of this setup process because everything can be improved, so it remains a question of when and how to do it, with some areas needing improvement.
What's my experience with pricing, setup cost, and licensing?
Regarding the pricing aspect of Visual Studio Professional 2022, I find that there are many free and open-source tools on the market that do provide a good alternative. Even from Microsoft itself, Visual Studio Code is a very good tool that is free and open-source, so I cannot call pricing an advantage, but for open-source, it is not a disadvantage.
For professional licensing, from a developer's perspective, it has been inconvenient to track a license, request licenses, and remove software, so tracking the license itself becomes a usability performance drop.
Regarding the procurement aspect of Visual Studio Professional 2022, I download it from the Microsoft website and install it, then log in using a corporate account, and it fetches the license automatically. It connects to a license server, and in three months, if there is a bug with the license server, it can indicate that the probationary period is over, but if a license is picked up successfully, it just continues to work, so from a usability perspective, whether it is a trial period or not should be highlighted.
What other advice do I have?
Regarding the Live Share feature of Visual Studio Professional 2022, I have not used Live Share. Visual Studio Code also supports Live Share, and as far as I remember, in similar scenarios, I usually use it with Teams during calls because I need to communicate with the person, and we are using chat and calls, so it is usually some meeting software such as Teams or other Google or Slack solutions.
Given my experience with Visual Studio Professional 2022, I would recommend that other organizations consider implementing test view features, which the Qt company could quite simply do in a month or two if a task is created.
Regarding edit and continue, I think that LLVM infrastructure should work on hot reload. Microsoft should start tracking use cases to ensure everything continues to work, and I see they have started moving to LLVM infrastructure as well, with Clang support for Visual Studio, which they should continue to do, moving hot reload for edit and continue into the LLVM and starting to use Clangd for IntelliSense purposes. I would rate Visual Studio Professional 2022 an overall score of five out of ten.