Comments (3)
Are you concerned about reliability? The difference between
Experimental and Stable is the API contract, not quality - i.e. the
thing being experimented on is the shape of future methods /
operators. I can assure you, that the Experimental version is just as
high-quality as the Stable version.
otherwise I've got a big assembly versioning problem on my hands.
Git makes maintaining your own branch and keeping it up-to-date
really easy, so if you don't believe me, you can always live on 1.0
:)
I realize this isn't optimal, but the build and release process for
RxUI is already really complex and messy because we support 4
architectures, and VS loves to mess with the Rx version #s in the
csproj file and break stuff. Maintaining both a 1.0 and 1.1 branch
(and making sure they both work!) would be bad for my sanity :)
Paul Betts [email protected]
On Fri, Jul 22, 2011 at 12:04 PM, Iristyle
[email protected]
wrote:
We're already using Rx in other projects, but the 1.0 official and not 1.1 experimental, which we don't want to take a dependency on.
I grabbed your source and rebuilt -- doesn't look like you're using anything from 1.1. I would like to see official releases based off of 1.0, otherwise I've got a big assembly versioning problem on my hands.
Thanks for the consideration.
Reply to this email directly or view it on GitHub:
https://github.com/xpaulbettsx/ReactiveUI/issues/22
from reactiveui.
Reliability, no... API churn, yes.
We have a number of projects here, where the binaries are shared in a few common subrepos (using hg internally) to kind of standardize everything in a very build-server friendly kind of way (Jenkins).
I'm trying to keep down the size of our shared /lib folders since we're using DVCS and I'm trying to make sure managing our dependencies doesn't get out of control by only picking up new binaries for our common toolset as they hit major milestones / have things we need (xunit / autofixture / fakeiteasy / autofac / automapper / fluentvalidation / restsharp / servicestack / rx / nlog / caliburn micro / reactiveui ... etc). Since you use Git, you know that growing your repo over time can be a problem, so I try to do it carefully ;0
Since the experimental version has a ways to go before finalizing, and we currently don't need anything in it, I'd rather hold off on stuffing temporary binaries into the tree until we need to.
from reactiveui.
So I just did a quick check to see if NuGet has gotten close enough to Maven in terms of allowing package manifests to be committed, then the binaries brought down as needed, without storing them in source control.
That has basically been the biggest deal breaker for me, given the care we take in managing dependencies + repository sizes.
As it turns out, I didn't realize that they had addressed that problem:
http://blog.davidebbo.com/2011/03/using-nuget-without-committing-packages.html
So I may have a better way to address my root problem.
from reactiveui.
Related Issues (20)
- [Bug]: ReactiveUI incompatible with .NET Assembly Load Contexts HOT 2
- [Bug]: On Maui initial NavigateAndReset pushes the same screen twice HOT 8
- Make generic IViewFor<TViewModel> implementation optional in favor of non-generic IViewFor HOT 15
- Add overloads for the command binders that accept IViewFor HOT 1
- [Bug]: got imcompatible message when using with .net 7 HOT 2
- [Bug]: Visual Studio hot reload broken HOT 21
- [Bug]: Putting RoutedViewHost inside a TabControl on Avalonia causes an app crash after navigating the second time HOT 7
- [Bug]: `ObservableAsPropertyHelper` emits property changed for lazy initial value after first-time reading and doesn't respect `DistinctUntilChanged` HOT 1
- [Bug]: WPF ReactiveCommand stays disabled after first execution HOT 9
- [Bug]: Mark ReactiveObject IObservable properties with DisplayAttribute for Winforms HOT 9
- ReactiveUI.WPF does not include .net 8.0 as a target: HOT 3
- [Bug]: Unable to use activation of views on Windows with MAUI HOT 2
- ViewModelViewHost: Better to Allow Developers Bypass the Default Fallback Behavior That Resovles View With No Contract HOT 2
- [Bug]: WireUpControls throws exception in net8.0-android HOT 7
- [Bug]: ViewModelViewHost does not set DataContext in WPF HOT 2
- [Bug]: WPF targeting issue for net6.0-windows HOT 4
- Dependency Dashboard
- [Bug]: iOS threading exception on command execution. HOT 4
- Bounce transition duration support HOT 3
- [Bug]: WinUI/WAS - ReactiveUI.WinUi nuget attempts to load the ReactiveUI.XamForms assembly when WhenActivated is called on a IActivatableViewModel HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from reactiveui.