1. Home
  2. Text Editors
  3. Microsoft Visual Studio Code Reviews
  4. User Review of Microsoft Visual Studio Code
Pros and Cons of Visual Studio Code for Legacy Microsoft Shops
June 30, 2021

Pros and Cons of Visual Studio Code for Legacy Microsoft Shops

Mark Orlando | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Microsoft Visual Studio Code

Our team is using Visual Studio Code to develop Angular web applications. Visual Studio Code was chosen because it's built to work with Git. The previous version of our product was developed in Visual Studio NS used Team Foundation Server for source control. Since the team decided to switch development to pure Angular instead of a hybrid model, Visual Studio Code and GIT were no-brainer choices.
  • Lightening fast UI.
  • Very easy to prototype individual components and later roll those up into larger ones.
  • Vast array of free add-ons available from the public.
  • Easy integration with Git.
  • Easy to learn what monthly updates were delivered.
  • Lack of button bar like ones found in Visual Studio.
  • Lack of integrated help that could link to YouTube, Channel 9, or other Microsoft videos on how to learn about features.
  • Integration with Team Foundation Server.
  • Would like to see it having some sort of integration into a Web API testing harness.
  • Transparent integration with GIT.
  • Ability to prototype components from the ground (HTML, CSS, JS) up.
  • UI speed is much faster than working in Visual Studio.
  • It's eased development because Visual Studio can be unwieldy sometimes with all its features buried in menus and submenus.
  • Unlike Visual Studio Code which is pretty much what you get when you install, Visual Studio Code provides new features monthly and does a darn good job with publishing nice release notes that can be called up quickly.
  • It took longer for us to decide to use Visual Studio Code because our legacy source control system as Team Foundation Server and Visual Studio Code didn't support it. We had to decide to make the switch to Git before adopting Visual Studio Code.
Visual Studio Code stacks up nicely against Visual Studio because of the price and because it can be installed without admin rights. We don't exclusively use Visual Studio Code, but rather use Visual Studio and Visual Studio code depending on the project and which version of source control the given project is wired up to.

Do you think Microsoft Visual Studio Code delivers good value for the price?

Yes

Are you happy with Microsoft Visual Studio Code's feature set?

Yes

Did Microsoft Visual Studio Code live up to sales and marketing promises?

Yes

Did implementation of Microsoft Visual Studio Code go as expected?

Yes

Would you buy Microsoft Visual Studio Code again?

Yes

If your Source Control Software is Team Foundation Server then skip Visual Studio Code. If you're using GitHub and are creating small projects Visual Studio Code is the way to go. If you need to create a large, enterprise-level application, Visual Studio Code makes it easier to set up interactions between related projects (client & server). If you're interested in getting back to the old way of using the command line to create projects and you know what to enter in the console window then Visual Studio Code is great. Visual Studio Code is a better choice if you don't know the console commands and prefer to make selections from a menu.