Support Visual Studio Shared Assembly Cache assembly resolution

Open
#390 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
build-system

Research direction

Start by tracing MSBuildLocator's assembly-resolution logic and compare it with the shared-location behavior introduced by microsoft/msbuild#14739. Confirm how Visual Studio's shared assembly location is discovered, then verify that MSBuildLocator loads the assemblies from that same location.

Written by the indexing model from the issue text.

Description

After https://github.com/dotnet/msbuild/pull/14739, MSBuild will prefer to load many assemblies from a shared location in Visual Studio rather than "next to MSBuild". MSBuildLocator should handle that case and load the assemblies from the same location.

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.