Hi,
I just installed Umbraco using Nuget (v7.4.3) and I've seen there are 20 dependencies that are outdated.
Some are just a small patch version changes, like examine (0.1.68 -> 0.1.69) or ModelBuilder (v3.0.2 -> v3.0.4), some other are minor versions, like ClientDependency or HtmlAgilityPack or ImageProcessor, but many other are major version, like AutoMapper (v3 -> v5) or JSON.NET (v6->v9) or Lucene.
Given semver, I guess it should be safe to update the patch release and probably the minor versions, but not the Major ones, but it can become a mess to go and look which package to update.
What is the best practice? Do not update any dep unless there some known bug in it?
Outdated nuget packages
Hi, I just installed Umbraco using Nuget (v7.4.3) and I've seen there are 20 dependencies that are outdated.
Some are just a small patch version changes, like examine (0.1.68 -> 0.1.69) or ModelBuilder (v3.0.2 -> v3.0.4), some other are minor versions, like ClientDependency or HtmlAgilityPack or ImageProcessor, but many other are major version, like AutoMapper (v3 -> v5) or JSON.NET (v6->v9) or Lucene.
Given semver, I guess it should be safe to update the patch release and probably the minor versions, but not the Major ones, but it can become a mess to go and look which package to update.
What is the best practice? Do not update any dep unless there some known bug in it?
Thx
Simone
Hi Simone,
In my experience I found that you could easily end up having dependency issues.
I suggest leaving the versions as required by Umbraco. Though if you need to use newer versions you can redirect specific assembly versions to a path.
Snippet:
See following article on how to redirect required assembly versions if Umbraco is unhappy with updated version: https://msdn.microsoft.com/en-us/library/7wd6ex19(v=vs.110).aspx
Ok, thx
will leave as it is :)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.