I suggest you ...

Support Paket

Paket ist an NuGet Alternative since "NuGet is broken by design" (statement of the NuGet Team itself: http://blog.nuget.org/20141010/nuget-is-broken.html)

There is a good alternative called Paket:
http://fsprojects.github.io/Paket/

The only thing you have to do in order to support Paket is to drop the usage of install.ps1 which is already declared deprecated by NuGet. I wrote a blog post about that:
https://uliarmbruster.wordpress.com/2015/03/18/how-to-get-the-postsharp-package-running-with-paket/

33 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Uli André ArmbrusterUli André Armbruster shared this idea  ·   ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • gfraiteurAdmingfraiteur (Admin, PostSharp Technologies) commented  · 

        We're reworked the plan last week and 4.4 is going to be scaled down and merged with 5.0. Work should begin in July, so we're one quarter late.

        Note that in theory you should be able to repackage PostSharp yourself with relatively little work. An alternative is to use the "zip" deployment option that is now supported in PostSharp 4.3 but not yet documented.

      • Petter BrodinPetter Brodin commented  · 

        Is this still on the roadmap for 4.4? I'm evaluating using PostSharp, and since we're currently tied to using Paket, this is relevant for our situation.

      Feedback and Knowledge Base