Errors about invalid references are not associated with a project

[davkean]

1. Create a new Console App targeting .NETCoreApp1.0
2. Create a new Console App targeting .NETCoreApp1.1
3. Reference 2 from 1

Severity	Code	Description	Project	File	Line	Suppression State
Error		Project ConsoleApp49 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Project ConsoleApp49 supports: netcoreapp1.1 (.NETCoreApp,Version=v1.1)			0	
Error		One or more projects are incompatible with .NETCoreApp,Version=v1.0.			0	

Not sure if this is our bug or SDK, but these should be associated with a project.

[davkean]

Maybe this is NuGet outputting this?

Can we stop NuGet from adding errors to the error list, and instead use our errors from Resolve the reference?

[srivatsn]

@natidea @emgarten where did we land on who's outputting the errors for unresolved package refs?

[natidea]

I think these errors are coming from NuGet. The plan is for NuGet to add these to the assets file, and we can raise to the error list as needed.

Right now NuGet emits unresolved package refs to error list, and the SDK task adds some errors to the solution explorer where applicable (but suppresses messages to the error list for now, tracked by dotnet/sdk#585)

[davkean]

Where's the bug tracking this work?

[davkean]

The other thing I'd like to see is the errors around, references, package references and project references to be unified so that they look and feel similar. Right now it the error message for packages is really hard to parse:

Severity	Code	Description	Project	File	Line	Suppression State
Error		Package System 4.1.311.2 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Package System 4.1.311.2 supports: net451 (.NETFramework,Version=v4.5.1)			0	

[davkean]

I also don't understand this, Dependency node makes it out to seem this is a bug:

Whereas, error list tells me the correct story:

Warning		Dependency specified was System (>= 1.0.0) but ended up with System 4.1.0311.2.			0	

[natidea]

The NuGet work is tracked at NuGet/Home#1599

The dependency warnings were copied from the CLI (see dotnet/sdk#26 (comment)). They may have slightly different wordings from NuGet, or I may have selected the wrong one for this scenario.

[abpiskunov]

yes , message in the tree should be same as warning in error tree (it should come form the sdk, tree just display's it). Another thing is we need to add a correct icon for warnings instead of a question mark (that i will do)

[srivatsn]

Tracking this as part of #1660