Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

What is the current recommendation for dependent NuGet packages?#1698

thirstyape started this conversation inGeneral
Discussion options

Hi there,

I manage a NuGet package that depends on theDocumentFormat.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 frompublic 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 inthis issue.

Anyhow, please let me know what the recommended way to proceed is.

You must be logged in to vote

Replies: 0 comments

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
None yet
1 participant
@thirstyape

[8]ページ先頭

©2009-2025 Movatter.jp