microsoft / microsoft/vscode-dotnettools
C# workspace requirements should signal when unsupported project
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Describe the issue
when I open webtools in C# dev kit, it is not an SDK style and I expect that C# dev kit wont work. the message says it wont work in the corner
but then I go to workspace requirements, and it says things.
I think that workspace requirements should be disabled or say something about how non-style projects aren't supported this is a confusing experience.
if this were an SDK-style project then the workspace requirements would be met because the global json is satisifed, but there is an issue here.
Collect logs
no logs
Steps to reproduce
- open Webtools repo in C# dev kit
- see correctly
expected: C# workspace requirements says something about the project is not SDK style because it is a confusing experience here
Expected behavior
No response
Environment information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by opening the Webtools repo in C# Dev Kit and then opening the C# workspace requirements view. Start by tracing the workspace requirements view and its handling of non-SDK-style projects; done means it clearly indicates that the project type is unsupported instead of reporting only the global.json requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100