Good afternoon, such a problem, the package in Nuget is ticked, but in References it is not. In particular EntityFramework. How can I fix it?
1 answer
Normally, nuget adds the downloaded packages to the packages
directory (but you can configure this). The nuget functionality is to ensure that the packages
have the correct package. He does not monitor whether there is a link in your project, he doesn’t care. Therefore, the easiest solution would be to simply find your package in packages
and add a link to it again, manually.
When you add a package through a package manager (or package manager console), you have light magic: not only is the package loaded, but also a link to it is added to the properties of your project. So if you are too lazy to look for where the package lies, you can invoke this magic again: just remove the package from the package manager and add it again.
- Hm On the one hand, the topstarter helped, I see a daw. On the other hand, what kind of rake doesn’t happen with references in a project - sometimes you have to manually edit project files in a notebook. - AK ♦
- @AK: Well, yes, sometimes I have to. But in this case, in theory, the problem is more simple, and should be treated by simply adding the link again. The essence of the answer is the division of responsibility between nuget (to ensure the availability of the library) and the project file (to ensure the connection of the existing library). - VladD
packages
. Or if you are completely reluctant, remove it from nuget and add it again, it will add you a link to the project again. - VladD