Publish Bicep.LangServer binary with release so the language server can be used in other editors

[damienpontifex]

Is your feature request related to a problem? Please describe.
The language server can be used in other tools like neovim lsp. It'd be nice to be able to grab the latest executable of this from a release for use in other tools like this. Currently I clone the repo and build locally to use in this context

Describe the solution you'd like
A release also builds Bicep.LangServer and publishes/attaches a single file application executable such as 'bicep-ls-osx-x64' (and others per platform) to the GitHub release artifacts

[damienpontifex]

I'd be happy to contribute to this end if this is deemed a desirable addition

[alex-frankel]

At one point I think we were publishing the language server binary in our builds, but we took it out. @anthony-c-martin / @majastrz is there a way for us to get damien unblocked?

We also have #480 just as FYI

[damienpontifex]

Thanks @alex-frankel
I might close this one as it seems very similar to #480

[damienpontifex]

Just for clarity, this isn't really blocking me as I have workarounds for clone and build so feel free to prioritise appropriately. Just interested in simplifying/streamlining that process

[majastrz]

I reopened it because #480 is about creating an atom package which is different than this.

For VS code, we're keeping the extension size tiny by publishing runtime-agnostic binaries. Would this apply to your scenario? I would assume that the runtime is already present on your machine.

The alternative would be your suggestion to publish self-contained apps (possible even single-file to reduce size further via runtime trimming) for each runtime we support.

What do you think?

[damienpontifex]

It's probably a pretty safe assumption that you'd have dotnet on your machine :) and in my case it is on my machine.

I haven't tried the single file publishing with .NET 5 and so was even just curious what an exe published liked this would be like (probably mainly binary size after trimming I was curious).

I was thinking the self-contained app (with trimming) also to the fact that if you happen not to have the runtime, the language server executable would work regardless.

Summary - I'd be happy if just the dll was published as I could use that. But equally happy if a standalone executable was published to simplify things even further

[majastrz]

Gotcha. So I checked in our builds and the language server bits do get uploaded to artifacts (https://github.com/Azure/bicep/actions/runs/421971130). We just don't have them included with a release.

[majastrz]

The next release (we're planning on one this week) should include assets with the runtime-agnostic server bits.

[damienpontifex]

Thanks @majastrz