[Feature Request]: Reduce the wrapping around SDK Resolver messages when only one resolver is actually invoked · dotnet/msbuild#10191

(4 comments) (1 reaction) (0 assignees)C# (5,062 stars) (1,364 forks)batch import

Area: LoggingArea: ResolversFeature RequestGood First IssuePriority:2internal-team-onboardingtriaged

Description

Summary

In https://github.com/dotnet/sdk/pull/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

https://github.com/dotnet/msbuild/blob/003252215533cca375dfc6578d8cb9e029418f37/src/Build/BackEnd/Components/SdkResolution/SdkResolverService.cs#L277-L280 should change the way it logs to not log the wrapper if only one resolver was used.

Alternative Designs

No response

Contributor guide

Tech stack: csharp
Domain: build systemdeveloper experience
Issue type: feature
Difficulty: 3
Estimated time: 1-3 hours
Activity status: active
Clarity: clear
Prerequisites: C#MSBuild build systemSDK resolver
Newbie friendliness: 65
Research direction: Examine the referenced code in SdkResolverService.cs around line 277-280 to understand the current wrapping logic. Review the linked SDK PR #41268 to see how the single resolver condition is detected. Propose a change to conditionally log the wrapper only when multiple resolvers were used. Ensure the change maintains backward compatibility and includes appropriate tests.