Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning icons in Dependencies node of the VS solution explorer with no explanatory text #4716

Closed
danroth27 opened this issue Apr 10, 2019 · 8 comments
Assignees
Labels
Triage-Approved Reviewed and prioritized
Milestone

Comments

@danroth27
Copy link
Member

From time to time I see warning icons in the Dependencies node of the VS solution explorer, but with no explanatory text for what the warning is about.

The situations for when this has occurred vary, but the most recent case was when I installed the latest .NET Core 3.0 SDK build (3.0.100-preview4-011112) and then created a new ASP.NET Core Razor Components project with the latest VS2019 build from the Preview channel of VS2019 (16.1.0 Preview 1.0 [28805.205.d16.1]).

Repro steps:

  • Install .NET Core 3.0 Preview 4 build ((3.0.100-preview4-011112 in my case)
  • Install VS2019 Preview
  • File -> New Project -> ASP.NET Core Web App -> Razor Components

Actual result:

  • A warning icon in the Dependencies node with no explanation:

dependency-node

error-list

1>------ Rebuild All started: Project: WebApplication8, Configuration: Debug Any CPU ------
1>C:\Program Files\dotnet\sdk\3.0.100-preview4-011112\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(151,5): message NETSDK1057: You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
1>WebApplication8 -> C:\Users\daroth\Source\Repos\WebApplication8\WebApplication8\bin\Debug\netcoreapp3.0\WebApplication8.dll
1>WebApplication8 -> C:\Users\daroth\Source\Repos\WebApplication8\WebApplication8\bin\Debug\netcoreapp3.0\WebApplication8.Views.dll
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

Expected result:

  • Some explanation for the warning icon in the error list and on hover
@danroth27
Copy link
Member Author

I hit another instance of these nondescript warning messages, this time with the analyzer node:

dependency-node2
error-list2
buid-output2

Repro:

  • Create a new ASP.NET Core Web App with .NET Core 3.0 Preview 3
  • Open the project in VS2019 Preview with .NET Core 3.0 Preview 4 as the active SDK (3.0.100-preview4-011146)

@jjmew jjmew added the Triage-Approved Reviewed and prioritized label Apr 11, 2019
@jjmew jjmew added this to the 16.1 milestone Apr 11, 2019
@drewnoakes
Copy link
Member

drewnoakes commented Apr 12, 2019

@drewnoakes
Copy link
Member

In-progress CLI changes for FrameworkReference are resulting in the SDK node being shown incorrectly. In preview 5 this changed again, producing a different error state (see https://devdiv.visualstudio.com/DevDiv/_workitems/edit/857810).

We've discussed tool tips. The current way to show meaningful errors to the user is via the error list. This particular error is not caused by the user, nor is it something the user can fix. It's not clear what useful message could be given here.

Closing this in favour of tracking issue #4762.

@drewnoakes
Copy link
Member

drewnoakes commented Apr 29, 2019

I hit another instance of these nondescript warning messages, this time with the analyzer node

This is a separate issue. I suspect that more information about that error is available in the error list, or maybe as a child node in solution explorer. If you can reproduce it, could you open a new issue with enough information to repro it please? I now see the repro steps and will investigate.

@MisinformedDNA
Copy link

@danroth27 @drewnoakes Does this analyzer node issue happen with .NET Standard 2.0? I'm not using .NET Core 3.x, but am also seeing a warning on my analyzer nodes. I'm wondering if my problem is related or if it requires creating a new issue.

@drewnoakes
Copy link
Member

@MisinformedDNA feel free to open a new issue with your repro, just in case it's a different bug.

@ckelley7
Copy link

ckelley7 commented Nov 6, 2019

image

I'm seeing this after migrating from .Net Core 2.2 to 3.0 for my Angular 7 app.

@drewnoakes
Copy link
Member

@ckelley7 that is being tracked by #5418.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triage-Approved Reviewed and prioritized
Projects
None yet
Development

No branches or pull requests

5 participants