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

RFC: Nuget Packages confusing to users with separate platforms #16

Open
glennawatson opened this issue Aug 7, 2018 · 4 comments
Open

Comments

@glennawatson
Copy link
Contributor

As mentioned in #13 the nuget package system is non-obvious to the user at the moment.

We've had several users get confused by the exceptions being generated.

What do we need to do to fix it?

@glennawatson
Copy link
Contributor Author

AS mentioned by @matthewclendening Kent's book still references the pre Rx 8 information of the bait and switch for WPF etc. How do we get the setup process easier for users?

One proposal are Visual Studio Templates to make it easy to setup different Rx packages with recommended practices (eg a .NET Standard library etc) and some practice code. I know @RLittlesII has been working on this a bit in his spare time.

@matthewclendening
Copy link

This may be just (or partially) a documentation thing. I actually started off yesterday installing the ReactiveUI.WPF package - when that didn't work I started digging. Installing just that single package today (with v8.4.1) does the right thing and works seamlessly.

@RLittlesII
Copy link
Member

I think the System.Reactive 3.1.1 issue was a special snowflake. Granted I don't know how we ensure these things don't happen in the future. We will always be dependent on packages that may or may not play nice together.

I still think some documentation per platform to tell you which packages are required to get up and running is a step in the right direction.

Templates I think should be the ultimate goal of this effort. But that has it's own challenges like maintenance, i.e. cutting a template per packages release. No worst feeling than downloading someones template, and then having to manage the package, and paradigm updates yourself before you can use the latest features. Simply defeats the purpose of convenience the templates provide.

@glennawatson
Copy link
Contributor Author

glennawatson commented Aug 7, 2018

@worldbeater did a fantastic job updating our nuget overview page, but I really had to dig to find it. Plus his getting started page wasn't obvious. We need the documentation first page to kind of put this in your face.

https://reactiveui.net/docs/getting-started/installation/nuget-packages/
and
https://reactiveui.net/docs/getting-started/

ReactiveUI is a composable, cross-platform model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming which is a paradigm that allows you to express the idea around a feature in one readable place, abstract mutable state away from your user interfaces and improve improve the testability of your application.
ReactiveUI is a composable, cross-platform model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming which is a paradigm that allows you to express the idea around a feature in one readable place, abstract mutable state away from your user interfaces and improve improve the testability of your application.

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

No branches or pull requests

3 participants