NuGet Package Dependency

Esben Bach's Avatar

Esben Bach

03 Apr, 2018 07:20 AM

I am a bit confused as how dependencies are defined in the Postsharp NuGet packages, and why it is so.

The "PostSharp" package 5.0.49 depends on PostSharp.Redist >= 5.0.49 && < 6.0.0 - which means anything can basically upgrade up to version 6.0.0 without getting any grief from the compiler or nuget.
However looking at the PostSharp.Patterns.Diagnostics.* packages for version 5.0.49 (and also the aggregation packages and probably more) the dependency is PostSharp.Patterns.Diagnostics.Redist = 5.0.49
Which means that when i have a library package "A" which is consumed by library package "B", which again is consumed by executable project "C" and "C" wants to upgrade to PostSharp 5.0.50 i will get an error.

Something like this:
C->B->A->PostSharp.5.0.49
C->PostSharp.5.0.50

Is there any reason for having the PostSharp.Patterns.Diagnostics.* using a different dependency pattern than the "main" PostSharp package? Or is it a mistake, in case of the later please fix it, because it is annoying as hell when you have multiple packages using PostSharp.

  1. 1 Posted by Esben Bach on 06 Apr, 2018 08:11 AM

    Esben Bach's Avatar

    So, any comments on this?

  2. Support Staff 2 Posted by PostSharp Techn... on 06 Apr, 2018 11:15 AM

    PostSharp Technologies's Avatar

    Hello,

    I'm sorry for the late response. We still need to finish our internal discussion on this topic before giving you the final answer.
    So far, yes, the current dependencies of Pattern libraries on Redist packages seem to be a mistake, or rather omission. We, however, need to review how flexible the range for these dependencies can be made.

    -alex

  3. Support Staff 3 Posted by PostSharp Techn... on 10 Apr, 2018 07:58 AM

    PostSharp Technologies's Avatar

    Hello,

    We're closing the ticket for now as the bug has been internally filed as issue #15985. We will contact you as soon as the bug fix has been released.

    For more details on our support policies and prioritization of bug fixes, please visit https://www.postsharp.net/support/policies.

    Best regards,
    -tony

  4. PostSharp Technologies closed this discussion on 10 Apr, 2018 07:58 AM.

  5. Esben Bach re-opened this discussion on 10 Apr, 2018 08:34 AM

  6. 4 Posted by Esben Bach on 10 Apr, 2018 08:34 AM

    Esben Bach's Avatar

    Okay, no ideas on what the solution is going to be?

  7. Support Staff 5 Posted by PostSharp Techn... on 10 Apr, 2018 09:01 AM

    PostSharp Technologies's Avatar

    Not yet. The decision will come later as the bug becomes planned within our internal process.

    Best regards,
    -tony

  8. Support Staff 6 Posted by PostSharp Techn... on 25 Apr, 2018 12:46 PM

    PostSharp Technologies's Avatar

    Hello,

    We have decided to apply a version range to all our package dependencies, as it is done for PostSharp -> PostSharp.Redist dependency. And accordingly we will maintain backward compatibility between packages within the same major version.

    We have also discovered some breaking changes in the current 5.1 preview, so we'll have update the version number to 6.0 before the RTM to maintain the contract of backward compatibility.

    Best regards,
    Alex

  9. Support Staff 7 Posted by PostSharp Techn... on 28 May, 2018 11:57 AM

    PostSharp Technologies's Avatar

    Hello,

    We're closing the ticket for now as the bug has been internally filed as issue #15999. We will contact you as soon as the bug fix has been released.

    For more details on our support policies and prioritization of bug fixes, please visit https://www.postsharp.net/support/policies

    PostSharp Team

  10. PostSharp Technologies closed this discussion on 28 May, 2018 11:57 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac