The idea behind the extension is fairly simple - when a developer writes an application in one of the languages we support on, they can get some reference material by leveraging a key combination within the editor. Visual Studio Code was already installed on my machines, as it’s by far the most used app in my toolbox, but in case you need do download it - you can get it here. I got started by just downloading the Hello World example, provisioning npm and Yeoman on both developer machines and then starting to introduce modifications to the scaffolding. Of course, that doesn’t mean you can’t use another editor, but it certainly makes the workflow easier. It’s a little meta, but you will be developing extensions for Visual Studio Code in Visual Studio Code. Getting started - setting up the environment There was absolutely zero friction, as everything is done within the same environment and with the same cross-platform toolchain. I will start this by saying right away how easy it is to work on the extension across two platforms - part of it was written on a Windows machine, and another part of a mac. Last week I thought I would sit down and learn how to write a Visual Studio Code extension - what better way is there to test the documentation your company ships and give yourself the best holiday present of the year? Visual Studio Code And API Docs Combine the power of Visual Studio Code and with the API documentation lookup extension.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |