search

tintoy / msbuild-project-tools-vscode

VS Code extension for MSBuild intellisense (including PackageReference completion).
MIT License
82 stars 16 forks source link

Vscode infra #109

Closed DoctorKrolic closed 1 year ago

DoctorKrolic commented 1 year ago
  1. Added new task for building LSP server locally
  2. npm task is now dependent on Build LSP dev meaning you can modify LSP files, start debugging and LSP changes will be applied
  3. Removed top-level task since I don't see a reason to keep it
  4. Added Attach to LSP process launch configuration. I tried to do it in a semi-automated way, where you attach to LSP process right after extension host starts, but unfortunatelly, I didn't find a way to do it. So the correct usage of this configuration as of now is the following:
    1. Start debugging with Launch Extension configuration
    2. After A new VS Code instance pops up, select Attach to LSP process and select proper .NET process to attach to.
  5. stopOnEntry is not supported argument for extensionHost debugging type. Removed them
  6. Updated BUILDING.md to use new script instead of separate commands
  7. When I built extension for the first time package-lock.json automatically updated itself to newer format. I decided to kkep that
tintoy commented 1 year ago

Thanks for contributing! I'll have a look at these changes first thing tomorrow (it's bedtime here) 🙂

tintoy commented 1 year ago

Looks good!