Provide a way for consumers to validate a VS instance

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
build-system

Research direction

Start by reading OmniSharp's VisualStudioInstanceProvider.cs at the linked lines, focusing on how it checks for the Microsoft.VisualStudio.Components.Roslyn.Compiler package. Then inspect this repository's MSBuild discovery API and determine where consumers could request instance validation; done means a documented validation path can identify whether a discovered Visual Studio instance is suitable.

Written by the indexing model from the issue text.

Description

OmniSharp ships a very similar MSBuild discovery mechanism to this one. However, it verifies that the VS instance that it considers has the "Microsoft.VisualStudio.Components.Roslyn.Compiler" package installed.

https://github.com/OmniSharp/omnisharp-roslyn/blob/master/src/OmniSharp.Host/MSBuild/Discovery/Providers/VisualStudioInstanceProvider.cs#L56-L57

It would be great to provide consumers with some way to validate an instance in a similar manner. Otherwise, it's difficult to determine whether an instance is actually a reasonable choice.

Dominant language
C#
Stars
262
Forks
91
Avg merge
11d 22h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/MSBuildLocator

All issues in microsoft/MSBuildLocator

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.