Skip to content

Project source of warnings not immediately obvious when building a solution #42190

Open
@richlander

Description

@richlander

I built a solution, which had the following (correct) warning. It wasn't immediately obvious to me that that the two warnings were in relation to the distroessed project. It is obvious to me now. I wonder if there is a way to make this relationship more clear.

$ dotnet build
Restore complete (0.7s)
You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
  EndOfLifeDate succeeded (0.1s) → EndOfLifeDate/bin/Debug/net8.0/EndOfLifeDate.dll
  MarkdownHelpers succeeded (0.1s) → MarkdownHelpers/bin/Debug/net8.0/MarkdownHelpers.dll
  DotnetRelease succeeded (0.1s) → DotnetRelease/bin/Debug/net8.0/DotnetRelease.dll
  LinuxPackagesMd succeeded (0.2s) → LinuxPackagesMd/bin/Debug/net9.0/LinuxPackagesMd.dll
  SupportedOsMd succeeded (0.5s) → SupportedOsMd/bin/Debug/net8.0/SupportedOsMd.dll
  distroessed succeeded with 2 warning(s) (0.9s) → Distroessed/bin/Debug/net8.0/distroessed.dll
    /usr/local/share/dotnet/sdk/9.0.100-preview.6.24328.19/Microsoft.Common.CurrentVersion.targets(2176,5): warning : The referenced project '../DotnetSupport/DotnetSupport.csproj' does not exist.
    /usr/local/share/dotnet/sdk/9.0.100-preview.6.24328.19/Microsoft.Common.CurrentVersion.targets(2176,5): warning : The referenced project '../ReleaseReport/ReleaseReport.csproj' does not exist.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions