Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop Radical.Extensions.Castle package #132

Closed
mauroservienti opened this issue Mar 28, 2015 · 4 comments

Comments

@mauroservienti
Copy link
Member

commented Mar 28, 2015

Actually the content of the Radical.Extensions.Castle assembly is only used by the Radical.Windows.Presentation.CastleWindsor assembly, we should merge them.

@mauroservienti

This comment has been minimized.

Copy link
Member Author

commented Mar 29, 2015

How to self remove from package list?

@mauroservienti mauroservienti self-assigned this Mar 29, 2015
@micdenny

This comment has been minimized.

Copy link
Member

commented Apr 1, 2015

you can't permanently remove the package from nuget, you can unlist it:

  • login to the nuget.org portal
  • now go to the package
  • then you will see a button Delete Package (as I said it is not a permanent deletion, and is explained in the next page)
  • uncheck the List ...
  • save
  • done
  • 😄
@mauroservienti

This comment has been minimized.

Copy link
Member Author

commented Apr 2, 2015

ok, those are the steps to remove it from the NuGet servers. The other question is: is there a way to remove it from the installed packages on the user machine?

Since we are merging it into another package already installed I fear that an update can cause conflicts because the same classes are now defined in different assemblies. Can we release an update that auto-remove it self from the installed packages in the project?

I've found this: https://github.com/Particular/NServiceBus.Bootstrap.WindowsService/blob/master/packaging/nuget/install.ps1

that manually changes the packages.config file.

@micdenny

This comment has been minimized.

Copy link
Member

commented Apr 2, 2015

As far as I saw the script is the way to accomplish those stuff but I never implemented one, I think it worth a try

@mauroservienti mauroservienti added in progress and removed ready labels Apr 3, 2015
mauroservienti added a commit that referenced this issue Apr 3, 2015
mauroservienti added a commit that referenced this issue May 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.