![]() There's almost no more need to leave VSCode in my general workflow. Then there's the integrated terminal which can be customized as well. ![]() On top of that, I can trigger one (or more) tasks as a precondition for my launch config. I use one for debugging, one for unittest etc. I have a task to build binaries, unit tests, doxygen, etc.On VS Code, I can define custom launch configurations, e.g. I can assign a keyboard shortcut to trigger these tasks. Both instances are setup almost identically. I have VS Code on both Windows and a Linux VM. We use a Makefile based toolchain to build our software.We use the same toolchain to build for Windows and (cross-compiled) embedded Linux. I was happy and didn't think I would ever use VSCode as my primary IDE. When I came to my current position, I was used to using Visual Studio (201x).
0 Comments
Leave a Reply. |