Provide a tooltip on the Yellow Exclamation on Nuget References aka the yellow pain in the stomach

NuGet / Home

Repo for NuGet Client issues

Other

1.5k stars 253 forks source link

Provide a tooltip on the Yellow Exclamation on Nuget References aka the yellow pain in the stomach #8621

Open vsfeedback opened 5 years ago

vsfeedback commented 5 years ago

This issue has been moved from a ticket on Developer Community.

Provide a tooltip / dialog on the Yellow Exclamation on Nuget References why this appears.

Provide any/more information why this /!\ Yellow Exclamation is shown , so I can guess if I care or not - old cache information, reload solution, csproj stetting are worng, ... what ever. Now it'S a wild guess why this happens.

The situation with all the TargetFrameWork, RuntimeFrameworkVersion, ... differences with visual studio, msbuild core, msbuild framework, ... is IMHO not easy.

txs Flori

Original Comments

Visual Studio Feedback System on 9/16/2019, 00:32 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Original Solutions

(no solutions)

nkolev92 commented 5 years ago

This is an external partner bug, but originally tracked on NuGet side since it was filled there. We should analyze the experience and file project-system bugs respectively.

Nefcanto commented 4 years ago

I have the same issue here:

As you can see, it's driving me crazy. Any update I make to the .csproj file, I get no results. I can't build. Also dotnet restore command does nothing at all.

I've removed .vs folder (after closing all VS instances). No results. I've removed all bin and obj folders after closing VS instances, and still no results. I've managed to clean cache of VS, still not working I've removed repository and got a fresh version from Version Control System, still not working

At least tell us why. It's sooooooooooo frustrating. We can't test everything heuristically to find out the error.

Nefcanto commented 4 years ago

The exact same .csproj works on another solution. It's exactly the same. Only the name is different. We have a microservice platform and accounts, configurations, taxonomy, ticketing, sales, and other microservices have the same project structure in the layer of CodeGenerator, and the other one works, this one is stuck.