What is the current recommendation for dependent NuGet packages? #1698
thirstyape
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
I manage a NuGet package that depends on the DocumentFormat.OpenXml NuGet package. As I would like to allow consumers to have a flexible package I have been allowing any version 2.18.0 or greater.
Now with version 3.0.0 available there have been a slew of breaking changes, some of which have affected the package I am working on. What I am wondering is do I need to force consumers of my package to choose between either the 2.X and 3.X branches or is there a way to continue supporting multiple versions?
In this particular case the problem is the change from
public enum ImagePartType
topublic static class ImagePartType
. Because I have usedImagePartType
as a variable type and method parameter, I will need to change this to something such asPartTypeInfo
; the problem here is thatPartTypeInfo
is new in version 3.X so I cannot use it in the older versions.I am genuinely surprised that a package with so many dependent NuGet packages would make a change like this. I would have thought this would have been a much larger consideration in this issue.
Anyhow, please let me know what the recommended way to proceed is.
Beta Was this translation helpful? Give feedback.
All reactions