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# (5,062 stars) (1,364 forks)batch import
Area: LoggingArea: Solution (.sln)help wantedneeds-designtriaged

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

Tech stack
csharp
Domain
build system
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C#MSBuild basicsSolution file structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate how MSBuild parses .sln files and determines which projects to build. Look for classes like ProjectConfigurationInSolution and SolutionFile. Identify where projects are silently skipped and add a warning message there. Review any existing tests to understand expected behavior.
Issue a message or a warning when project isn't built because of .sln configurations · dotnet/msbuild#1935 | Good First Issue