(Though, I would guess that they use a lot of common code under the hood.) And, here’s the confusing bit: Visual Studio Code has very little to do with Microsoft Visual Studio. Microsoft Visual Studio is Microsoft’s big and comprehensive IDE/compiler/debugger package for C# and C++ development that has been around for many years and is available for Windows and macOS (but not for Linux). Many of you are most likely familiar with Microsoft Visual Studio. When I move focus, my changes are already there (or I just need to hit the “Yes to All” button in the reload confirmation dialog) and I am getting the best of both worlds.īefore I go into greater detail, I’d like to explain a bit about Visual Studio Code. Some things I do in Qt Creator, while others I do in Visual Studio Code. I have configured both to auto-save and auto-reload so that I can switch seamlessly between the two. My current work setup uses both in parallel. I am not advocating to ditch Qt Creator altogether. Also, I am doing a lot of my development on macOS, and Qt Creator does not always have the same level of stability there as it does on Linux and Windows. The first question you want to ask is probably, “Why use another editor or IDE at all if we have Qt Creator, which is a perfectly good and, in particular, Qt-specific IDE, ready at our disposal?” And, of course, that’s a very valid question to ask.įor me, the main reason is that Visual Studio Code simply does some things better than Qt Creator – and other things worse, which I’ll discuss later. Motivation of using Visual Studio Code instead of Qt Creator So in this blog post, I am going to share with you some of the experiences some of us here at KDAB have had using Visual Studio Code for Qt development.

Software developers like tools, and in particular tools that make them more productive.

Visual studio code format clang