Issue a message or a warning when project isn't built because of .sln configurations
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 1.5k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 133
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
No contributing guide indexed for this repository
Research direction
Start by tracing MSBuild's handling of .sln project configurations and how each listed .csproj is selected for the current configuration. The change is done when a project excluded because its GUID lacks the active configuration produces a clear message or warning, with coverage for that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100