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

nuget package depends on rx-main 2.2.5, which has been pulled from nuget #89

Closed
sillyotter opened this issue Jul 1, 2016 · 12 comments
Closed

Comments

@sillyotter
Copy link

Description

Rx-Main 2.2.5, the package this things current nuget package depends on, has been unlisted from nuget. When they updated to v3.0 of rx.net, they changed the name to System.Reactive. We might need a new release of this to track the new Rx library, assuming that they didn't break anything.

@panesofglass
Copy link
Collaborator

Ouch! I am surprised they pulled the package version. @cloudRoutine and I recently discussed the need to update this package to work with .NET Core, as well. We will try to get to that soon. If anyone else can get to it first, please do. I'm happy to review a PR!

@thecoldwine
Copy link

Actually, I got a problem with moving a package to the Rx 3.0, because it seems like Rx team discarded support of 4.0 and 2.59 targets. Fortunately. it is still possible to build Control.Reactive for .NET 4.5 plus.

@TheAngryByrd
Copy link
Contributor

Since #90 (comment) was merge, can we get an alpha/beta nuget package? Pretty please? 🙏

@sillyotter
Copy link
Author

Don't know if it will help anyone else, but while this has been going on, I have taken to using pakets github ability to just grab the Observable.fs file directly from the project and linking it directly into my project.

In the paket.dependencies:

github fsprojects/FSharp.Control.Reactive src/FSharp.Control.Reactive/Observable.fs

and in paket.references:

File: Observable.fs

And of course the needed nuget System.Reactive.* references as well. Works quite well until a nuget package exists.

@dsyme
Copy link
Contributor

dsyme commented Oct 24, 2016

@cloudRoutine @panesofglass Could you update the nuget package after recent merges please?

@cloudRoutine
Copy link
Member

cloudRoutine commented Oct 26, 2016

@panesofglass and @forki are the only ones who have access to the nuget package

@forki
Copy link
Member

forki commented Oct 26, 2016

@cloudRoutine what is your nuget name I can probably set that up for you.

@cloudRoutine
Copy link
Member

it's also cloudRoutine

@forki
Copy link
Member

forki commented Oct 26, 2016

The user 'cloudRoutine' is already an owner or pending owner of this package.

so we tried that already ;-)
Anyways I sent new invitation

@cloudRoutine
Copy link
Member

I guess I missed the first invite, they should really list the pending invites on the profile page, but now I'm setup. I'll upload the new version today or tomorrow.

@thecoldwine
Copy link

thecoldwine commented Nov 8, 2016

@cloudRoutine do you have any updates on NuGet? It would be great if we see updated version on global nuget repo :)

@panesofglass
Copy link
Collaborator

Sorry for the long delay. I just published from AppVeyor. @cloudRoutine, send me your email, and I'll add you to the AppVeyor team so you, too, can deploy successfully built packages. I could also just auto-deploy, if you think that is better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants