dotnet/msbuild

Issue a message or a warning when project isn't built because of .sln configurations

Open

#1,935 opened on Apr 3, 2017

View on GitHub
 (0 comments) (1 reaction) (0 assignees)C# (1,364 forks)batch import
Area: LoggingArea: Solution (.sln)help wantedneeds-designtriaged

Repository metrics

Stars
 (5,062 stars)
PR merge metrics
 (Avg merge 11d 7h) (125 merged PRs in 30d)

Description

If the .sln file doesn't include a project file listed with the configuration being built, the project is silently excluded from building.

I thought it would be nice to at least issue a message that the .csproj listed in the file wasn't built because a list of configs for this project's GUID doesn't mention the current configuration.

As far as I can tell right now there's no message or warning at all.

Contributor guide

Research direction
Investigate the MSBuild solution parsing code to detect when a project is excluded due to missing solution configuration mapping, and add a warning message.
Tech stack
csharp
Domain
backendbuild systemdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#MSBuild internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40