Open nguerrera opened 7 years ago
Adding the repro steps above.
What is that second error? Is that coming from assets targets? We should also avoid outputting if the reference failed to resolve.
@davkean Good point. I filed dotnet/sdk#829 for that. Of course, it's completely separate and less severe than the general issue of missing errors in error list.
Yep absolutely,
Was a "build" always involved?
I believe so. @jinujoseph ?
thatz right build was always involved.
@heejaechang any idea what's going on here - is this related to the issue where the Roslyn package is not initialized soon enough?
@srivatsn sounds like same issue. let me check.
this is dup of https://github.com/dotnet/roslyn-project-system/issues/1411
Still seeing some errors not propagate to error list. See dotnet/sdk#910 for repro.
Is this because the error is actually thrown from the referenced project, when it detects that it can't satisfy the TFM requested by the referencing project?
I think so. Dave mentioned that at some point but I can't find the issue.
Is this related to #1510 or #1511?
@davkean this sounds related to #1510 or #1511 and should get fixed with the CPS changes?
@srivatsn No those look unrelated.
Repro Steps
Create a 1.1 NET Core project (there are templates in VS for 1.1 web projects) Add a unit test project - the default template in VS targets NetCore 1.0 Add a ref from the test project to the first one. Build
It is not happening to me, but I've seen this in two different instances on @jinujoseph's machine.
https://github.com/dotnet/sdk/issues/798#issuecomment-277329066
Output Window:
Error List:
@davkean @srivatsn This is especially bad because in both instances I've seen it, there were helpful messages in the output that are harder to read there and the error list picked up only secondary consequences of the root problem with undecipherable messges.