In current release version of the extension language server is built in debug mode about msbuild-project-tools-vscode HOT 3 CLOSED

for the azure pipelines config.

I think, the right way to fix it would be adding an additional step for the vsix prebuild, e.g. powershell Publish-LSP.ps1 && tsc -p ./, where Publish-LSP.ps1 is a script, that publishes language server in release mod and makes sure all unneded files are deleted. This way both manual vsix build (via vsce package) and official publishing pipeline would be fixed. TBH I thought that you manually build vsix and publish it in the extensions store when writing the issue description

from msbuild-project-tools-vscode.

Yeah that sounds like a good idea; as long as we still produce symbols for it I’m fine with release-mode builds (we have historically had at least one other consumer for the language server - Eclipse). I’ll take a look tomorrow and see what I can do for the azure pipelines config.

from msbuild-project-tools-vscode.

I do currently but want to fix that :)

from msbuild-project-tools-vscode.