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

Intellisense broken after opening solution and restoring packages #3930

Closed
maxinfet opened this issue Aug 30, 2018 · 5 comments
Closed

Intellisense broken after opening solution and restoring packages #3930

maxinfet opened this issue Aug 30, 2018 · 5 comments
Assignees
Labels
Feature-NuGet NuGet integration including pushing it properties, project and package references, and Pack support. Legacy Issues against the legacy project system.
Milestone

Comments

@maxinfet
Copy link

maxinfet commented Aug 30, 2018

When we open a new branch with no packages restored the intellisense will be broken for anything that is referenced from a nuget package. Then once we restore packages it will still be broken. The odd thing is that it is marked as an error but we can still build fine.

Our solution is using the old project system and uses package.config to restore nuget packages. Also we are on Visual Studio 15.8.2 but we started experiencing this issue in 15.8.1.

Here is a project I put together to demonstrate the issue https://www.dropbox.com/sh/pvuk4m8eponihro/AABkKghoPvUIyRJ2aU91R_Kqa?dl=0

To see the issue restore packages after opening the solution and then notice that the types from log4net in Program.cs are still marked as missing. Expanding references and then clicking on the log4net reference with the properties window opened seemed to cause it to evaluate whether it knew of those files or not.

@maxinfet maxinfet changed the title Intellisense broken after opening solution without packages restored Intellisense broken after opening solution and restoring packages Aug 30, 2018
@Pilchie Pilchie added Feature-NuGet NuGet integration including pushing it properties, project and package references, and Pack support. Legacy Issues against the legacy project system. labels Sep 4, 2018
@Pilchie
Copy link
Member

Pilchie commented Sep 4, 2018

@panopticoncentral can you take a look and see if this is related to the design time build changes?

@tmeschter
Copy link
Contributor

@maxinfet Does this still reproduce when using 15.8.6 or newer?

@maxinfet
Copy link
Author

maxinfet commented Oct 24, 2018

@tmeschter I can not confirm this in our main project because of issue #4158. I can no longer produce it in the reproduction project I attached to this issue.

@maxinfet
Copy link
Author

@Pilchie
Copy link
Member

Pilchie commented Nov 15, 2018

Closing given above.

@Pilchie Pilchie closed this as completed Nov 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature-NuGet NuGet integration including pushing it properties, project and package references, and Pack support. Legacy Issues against the legacy project system.
Projects
None yet
Development

No branches or pull requests

4 participants