@brianlagunas wrote:
Actually, the dependencies are not the issue. Although, NuGet will not bring down a newer package with an install. For example; if Prism.Unity has a dependency on Prism.WPF v1.0 and then I updated Prism.WPF to v1.2; when I install the Prism.Unity package it will still only bring down Prism.WPF v1.0. But, that's an issue with NuGet.
The heart of the issue is that the Prism.Unity package has 3 different platform assemblies which are all versioned differently. When only one of those assemblies update, how do you manage the NuGet package version?
Here is a scenario: let's say the PrismUnity NuGet package is currently v3.0.0 and contains these assemblies
Prism.Unity.Wpf.dl v3.0.0
Prism.Unity.Windows v1.0.0
Prism.Unity.Forms v2.0.0Notice how all assemblies are versioned differently. This makes sense, because not every assembly gets an update or bug fix.
Now, let's say that we make an update to Prism.Unity.Windows and increment it to v2.0.0. What is the new package version?
Since developers always associate the NuGet package version to a direct match to an assembly version, this makes for a very confusing situation. Also, when we only update one assembly and publish a new package, the other platforms get prompted for an update even though they didn't actually change.
What does everyone else do?
FYI: I changed the category
