Visual Studio Code extension doesn't work

[Markproveau]

The extension doesn't show up in VScode after placing the LSL folder in my extensions directory (which does contain all the other extensions I've installed)

I have the newest VScode version. It might be my fault, I'm a VScommunity 2015 user and this is my first time using VSCode. but all the other extensions I installed showed up, with similar file structure in those folders, but the LSL extension has no effect on VSCode when I open a .lsl file. and it doesn't show up in my extensions list in VSCode either.

[buildersbrewery]

I'll look into this when I have time. I previously had this issue which was fixed then in

buildersbrewery/linden-scripting-language@4f73668

Will report back here when appropriate.

[buildersbrewery]

@Markproveau Could you check whether the current state of files works for you?

---

Currently working through these:

• docs:
  • https://code.visualstudio.com/docs/extensionAPI
• code example:
  • https://github.com/search?utf8=%E2%9C%93&q=topic%3Avscode+topic%3Alinter&type=Repositories

---

Still want to add:

• lslint integration

[BoxximusPrime]

Also having this issue. Using Visual Studio Code version 1.17.0.

[buildersbrewery]

@BoxximusPrime

Currently I'm not too familiar with vscode and how to make things work there. Also, I'll have to check if generating binaries is mandatory or not through their generator.

In the meantime though you could have a look at @ebickle's lsl-vscode plugin. I sent him a pull request earlier this week with some updates.

[ebickle]

I had some issues with the VSCode LSL logic awhile back and ended up creating my own plugin from scratch. Never could quite figure out what was wrong with the code in buildersbrewery, likely some breaking change VSCode made along the way.

At some point I'm hoping to put in a proper LSL Language service into the plugin to get first-class support for documentation and code completion ("intellisense"), but its a lot of heavy lifting and quite a ways off.

[buildersbrewery]

@ebickle did you start with the language service? If you have the code, I could start adding the full LSL data, which I have here locally.

[night-herons]

@strawberryangel current VSCode does not seem to be able to activate it by placing it directly in the extensions folder. You need to run vsce package from a terminal to create a VSIX installation package for the extension and then install it.