In today post I will talk about what you should never do when you are using NuGet.
We have an application developed 2-3 years ago. Coming to V2, means also uprating different version of stacked used like Entity Framework, Unity and so on. When the first version was develop, each package from NuGet was installed in one or two project and added as assembly reference in the other one. Until now everything sounds good.
But there is a small mistake. When you reference the assemblies in the other project, you are referring them something like this “../packages/FooPackage 1.2.3”. When you will upgrade the package using NuGet, the references to the package in the projects where package was installed are updated to the new version of the package. But, in the project where there are only references to the assemblies from the package nothing will happen.
This means that you will end up with two version of the same stack (package) in the same application. This is the dream of every developer. In each package you will need to update the reference to the new package version.
Don’t to something like this. This is only a dirty fix, which will not resolve the root problem. Instead I prefer the other way. Uninstall all the packages, delete the package folder, remove all the references to packages and start from scratch. Install in each project the packages that you need.
We have an application developed 2-3 years ago. Coming to V2, means also uprating different version of stacked used like Entity Framework, Unity and so on. When the first version was develop, each package from NuGet was installed in one or two project and added as assembly reference in the other one. Until now everything sounds good.
But there is a small mistake. When you reference the assemblies in the other project, you are referring them something like this “../packages/FooPackage 1.2.3”. When you will upgrade the package using NuGet, the references to the package in the projects where package was installed are updated to the new version of the package. But, in the project where there are only references to the assemblies from the package nothing will happen.
This means that you will end up with two version of the same stack (package) in the same application. This is the dream of every developer. In each package you will need to update the reference to the new package version.
Don’t to something like this. This is only a dirty fix, which will not resolve the root problem. Instead I prefer the other way. Uninstall all the packages, delete the package folder, remove all the references to packages and start from scratch. Install in each project the packages that you need.
In this way, next time when you will update the packages, you will don’t need to do anything else.
Enjoy!
In see this quite often - usually the cause is that even today there are still some developers that did not bother to learn about NuGet and add references directly to an asembly in a folder..
ReplyDelete