You’ll see the only “real” file in there is the package.json. Just have a look at my pack here: waldo1001/ALExtensionPack: An extension pack for th AL Language (Microsoft Dynamics 365 Business Central) (). It actually only needs a manifest (a package.json) and that’s it. Well, such an extension pack, is SO easy to create.
Visual studio code plugins how to#
I also did a demo on how to create your own VSCode extension at NAVTechDays in 2017. Here is everything you need to start: Your First Extension | Visual Studio Code Extension API.
Visual studio code plugins install#
A simple concept that – when you have the pack installed – has as an extra benefit (well, if you’re ok with it -)) that it will also install extra apps when they would be added to the pack.Ĭreating such an extension is VERY simple, which you’ll have to compile to a VSIX and upload it to the marketplace for easy distribution. A very simple, no-code VSCode extension that will install extensions that are defined in the pack. You might have heard of the “ AL Extension Pack“. What we did: we created an extensions.json for all workspaces and we added it as part of our “template project” so that we’re sure that we do what we can to get the necessary extensions at the developers. You could also simply go to extensions, and filter to see the list that’s recommended for this workspace.Įasy peasy. The result is that you’ll get a notification every time you open the workspace (and are about to contribute to the code) and you have one of the recommendations not installed. vscode folder of your workspace (or as a workspace-setting), which you simply fill with a collection of extensions that you think are necessary for this workspace. When searching for a solution, there is one topic you always come across on various forums, and that’s the use of the extensions.json for “ workspace recommended extensions“. but if someone has better suggestions or solutions, please let me know -). So I’m going to try to make some suggestions that can help you for this. Well, I can already tell you: there is no decent solution as far as I am aware. How can I force my developers to install certain vscode extensions when they are working for our repositories? If one person doesn’t use it, the object ids are not being reserved, and you’ll still end up with conflicts.
Thing is, while this is an awesome extension, it actually ONLY really works when the ENTIRE team has it installed.
And the setup is kind of a no-brainer as well, as Vjeko is managing the backend for you. It isn’t getting more intuitive than this. In short: it’s a VSCode extension that will help you manage the Object Ids in team, by reserving them (right from instellisense) in a backend, where the team is connected to. vjekob/al-objid: AL Object ID Ninja ().AL Object ID Ninja – Visual Studio Marketplace.If you haven’t, well, let me make your day and show you some resources: You must have seen the launch of Vjeko’s extension: the “AL Object ID Ninja”.
0 kommentar(er)
