VS Code is a new editor from Microsoft (I guess some may insert an obligatory flaming remark here, but I think they’ve done some pretty good stuff as of late) that I’ve only been following off and on since it was first announced.

VS Code

Before working for myself, I was focused on .NET development and to this day, I’ve yet to find an IDE that I like as much as that.

But then, late last week, I saw this tweet:

Followed by this:

And then this resulted in a good, albeit short conversation.

I’ve never been a fan of switching IDEs in the middle of client projects (for some reasons), so I didn’t plan on giving this particular IDE a try for the foreseeable future.

But given that I’ve got a set of unfinished projects lying around and given that I had some time to myself this weekend, I opted to see how well VS Code worked with a couple of WordPress-based projects.

VS Code For WordPress Development

First, this is not going to be a comprehensive post. It’s going to be far from it. Instead, I’m simply going to focus on what little I was able to get setup and my initial impressions.

Specifically, I set up the following:

  1. Opened a WordPress-specific project,
  2. Setup PHPCS using Composer along with the WordPress Coding Standard ruleset,
  3. Used the integrated Terminal,
  4. Briefly experimented with the integrated debugger.

To be clear, some of these tests required packages, so I’ll make sure to list those off in this post and dive into each of the above points in a future post.

will say that my initial impressions are positive. It didn’t take long to get my bearings, to get started customizing my setup (with my preferred font, font size, whitespace rules, and the PHP Coding Standards).

Using the VS Code Debugger

Using the VS Code Debugger

I’d have to say that the highlight of testing the editor gave me the first experience, out-of-the-box, that few editors  have. This feels like a much more minimal copy of Visual Studio for .NET (as it should).

It’s fast (though I know this is subjective), it has good package management, and it’s easy to get started with all of the various tools one would expect for intermediate-to-advanced WordPress development.

If you get a chance, I recommend reading The Basics of Visual Studio Code

The inevitable question will be if this can hold its own against an IDE such as PhpStorm. Right now, I can’t answer that, but I should be able to do in a future post.

For those who are curious, the main things I’m interested in evaluating are:

  • Debugging,
  • Git-integration (yes, I love Tower but if I can consolidate and do so elegantly, then I will),
  • Subversion integration (for those projects that in the WordPress plugin repository),
  • Symbol Replacement and refactoring,
  • And perhaps a few more than I’ve yet to think of while mentioning here.

All of this will come in future posts, though.

Installed Packages

Here’s a list of all of the packages I’ve installed thus far. If you have any to add (or you’d recommend removing), then let me know in the comments.

I’ll be sure to keep this list updated in future posts, as well. I’m working to keep all of my VS Code related posts tagged as such so it will be easy to find them.

Category:
Articles
Tags:
,

Join the conversation! 3 Comments

  1. What is the Terminal extension for? As per my understanding terminal is built right into vscode and it is not required to install any extension for that.

  2. Lovely post, Tom. Thank you.

    I’d seen VS Code in passing a couple months back, while working on a very small TFS+VS2015 project. I’d also seen you mention this post on Twitter a while back, but I haven’t had time to investigate…till now.

    Chris Coyier’s recent tweet (today), made me take a closer look at VS Code (mainly because I had some spare time). And I’m very glad I did.

    I’m a fan of Visual Studio, and in my opinion, most other IDEs pale in comparison (my opinion).

    Recently I’ve been looking at Atom IDE (for which you also have an excellent intro post), and although I liked it, there was just something not quite there for me (with the Atom IDE). Similarly with Sublime and Brackets. Perhaps that is why I’ve just stuck with Eclipse for so long.

    I have used PHP Tools for Visual Studio, which works well, but VS Code looks to be a game-changer for me, I think.

    After installing some preliminary extensions, I came over here to get some pointers, which have been very useful. Thanks.

    The WordPress snippet extension is good, but I found its autocomplete more manual than auto in places, but I’m sure this will improve over time.

    Overall, a really good experience using the (free) VS Code, and I would definitely recommend it to front-end and WordPress makers.

    Thanks Tom

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.