search

microsoft / vscode-dotnettools

This is a feedback repository to capture issues logged for the C# Dev Kit and related extensions from Visual Studio Code
Other
216 stars 9 forks source link

[3rd party] Meadow - track compatible projects in workspace #177

Open arkalyanms opened 1 year ago

arkalyanms commented 1 year ago

From vscode-csharp created by Redth: dotnet/vscode-csharp#5833

Is your feature request related to a problem? Please describe.

Similar to #5805 and #5806 today the Meadow extension for VSCode relies on O# events to be notified when the projects in the workspace change. It uses this event to then parse the project workspace in order to determine if there are Meadow compatible projects in the workspace to enable Meadow specific UI and functionality.

Describe the solution you would like

Ideally Meadow could subscribe to a specific query where it matched projects with a known ProjectCapability, and could return matching projects and ideally infer a few evaluated msbuild property values for things like the project output path and build configuration.

Applicable Scenarios

Meadow IoT developers using the VSCode Meadow Extension

Describe alternatives you've considered

Meadow could watch the workspace for .csproj files and parse them out, or even create a shadow Roslyn MSBuild instance to track changes and evaluate properties, however this seems prone to interfering with csdevkit's project system.

arkalyanms commented 1 year ago

This tracks CDK project system events specifically. C# events will be tracked by https://github.com/dotnet/vscode-csharp/issues/5833#

tmeschter commented 1 year ago

Moving to "area-project-cps".