We use Visual Studio for website development and related tasks. It's been quite helpful for us.
From a professional perspective, I've been using Visual Studio since childhood, so I find it very useful. The code analysis tool is particularly valuable as it eliminates the need for manual code reviews.
Many essential features are built-in, making it a great tool. Additionally, it allows for easy integration with other tools like MS Teams, which enhances its usefulness.
Sometimes, the deprecation of packages can be a challenge. Although Visual Studio provides suggestions when we compile and encounter deprecated packages, it can still be confusing. Even after multiple attempts, we may struggle to fix these deprecated packages and related issues. So, it is one of the areas of improvement in Visual Studio.
I have been working on a website that I inherited from a client, and when I tried to run it on my system, I discovered that some of the packages were either depreciated or no longer in use. It would be helpful if Visual Studio could suggest and handle such unused packages in a more user-friendly manner.
I am suggesting this as an area of improvement because recently I was working on a bigger client project. The project was functioning correctly on my system but not on another system. Later, I found that some packages were depreciated, which might have caused the issue. However, we couldn't determine the exact reason for the difference in behavior because we used the same ZIP file and the same Visual Studio version. Then, when the person tried to run the same code on her system, it didn't work. It seemed to be related to the deprecated packages. Ultimately, the solution we eventually found was to set up a new system for her, reinstalling Microsoft Visual Studio and related components.
Another area that could greatly benefit from Microsoft within Visual Studio is unit testing. It's a pain point for every software developer. If Microsoft can provide better tools or features related to unit testing, it would be really helpful. Especially when working on complex projects, writing comprehensive test cases can be time-consuming. However, clients often cannot afford to pay for that additional time in the competitive market.
So in future releases, having some automation capabilities or built-in support for generating test cases would be great. Although we can integrate third-party automation testing tools, they are often paid solutions. For example, I've noticed the presence of plugins like ChatGPT in Visual Studio Code, but I'm not fully aware of their capabilities. Therefore, if Visual Studio could offer some level of automation for test cases, it would be a valuable addition.
I have been using Microsoft Visual Studio for over 15 years.
I would rate the stability of Visual Studio a ten out of ten.
Microsoft has gained a lot of confidence in the market, so I would rate the scalability of Visual Studio around eight out of ten.
Based on my recent experience, sometimes, we faced difficulties with the same set of codes. Therefore, considering the recent incident, I leaned toward an eight and not a ten for scalability.
In my company, around 20 people are using this solution.
The initial setup is very simple. Microsoft has made it very easy to set up.
Price-wise, it is good. We are using the paid versions, and the price is reasonable. For our company, it's a genuine price.
I have only worked with Visual Studio.
Overall, I rate it a ten. It's very user-friendly and feature-rich.
However, there's always room for improvement in the product. Features like automation test cases to meet market requirements would be beneficial.