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

Make NuGet a first class citizen. #582

Closed
jlaanstra opened this issue May 7, 2014 · 6 comments
Closed

Make NuGet a first class citizen. #582

jlaanstra opened this issue May 7, 2014 · 6 comments
Assignees
Labels

Comments

@jlaanstra
Copy link
Member

Currently the packages folder is checked into the ReactiveUI repository and not all libraries are coming from NuGet.

I believe this was done because of Xamarin, but we should definitely switch when Xamarin supports NuGet.

@shiftkey
Copy link
Contributor

shiftkey commented May 8, 2014

@jlaanstra
Copy link
Member Author

You mean like this? https://github.com/mrward/monodevelop-nuget-addin

I have not checked if it was already supported or not :). At least we now have an issue to track this.

@jlaanstra
Copy link
Member Author

I'd really like @paulcbetts his opinion on this.

@anaisbetts
Copy link
Member

We can probably do this now - before, we had a lot of churn in Rx and other libraries, not everything was available in NuGet, etc etc. There was a ton of reasons to keep everything in ext, but none of them are really true anymore. Even NuGet added a feature for us where packages.config couldn't be used if you kept all of your csproj files in the same folder.

So what I'm saying is, 👍 on NuGet'ing everything :)

@jlaanstra jlaanstra self-assigned this May 11, 2014
@jlaanstra jlaanstra added this to the ReactiveUI 6.0 milestone May 11, 2014
@anaisbetts
Copy link
Member

This is a good idea, but probably not blocking RxUI 6.x release, we can do this whenever

@anaisbetts anaisbetts removed this from the ReactiveUI 6.0 milestone May 11, 2014
@jlaanstra
Copy link
Member Author

I'll hold of on this until #590 and #552 are done.

@jlaanstra jlaanstra mentioned this issue May 29, 2014
4 tasks
@lock lock bot added the outdated label Jun 26, 2019
@lock lock bot locked and limited conversation to collaborators Jun 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants