-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Open
Labels
Area: LoggingArea: ResolversFeature RequestGood First IssueSelf-contained issues good for first-time contributors.Self-contained issues good for first-time contributors.Priority:2Work that is important, but not critical for the releaseWork that is important, but not critical for the releaseinternal-team-onboardingtriaged
Description
Summary
In dotnet/sdk#41268 I was able to use the SDK Resolver features to ensure that only the NuGet SDK resolver was used for a restore. In this case we should be able to remove MSBuild wrapping around the 'error list' and only surface the single Resolver's message.
Background and Motivation
We want to remove visual noise around error experiences and make it easier for users to diagnose the core problems.
Proposed Feature
msbuild/src/Build/BackEnd/Components/SdkResolution/SdkResolverService.cs
Lines 277 to 280 in 0032522
| if (failOnUnresolvedSdk) | |
| { | |
| loggingContext.LogError(new BuildEventFileInfo(sdkReferenceLocation), "FailedToResolveSDK", sdk.Name, string.Join($"{Environment.NewLine} ", errors)); | |
| } |
Alternative Designs
No response
AR-May
Metadata
Metadata
Assignees
Labels
Area: LoggingArea: ResolversFeature RequestGood First IssueSelf-contained issues good for first-time contributors.Self-contained issues good for first-time contributors.Priority:2Work that is important, but not critical for the releaseWork that is important, but not critical for the releaseinternal-team-onboardingtriaged