Alpha 4 released! Changes:
* Added Obsolete-marked classes with documentation to ease migration from old versions. * This release shares history with castleproject/ Castle.Services.Transaction by means of merging, so it includes Henry's changes and improvements. * Renamed solution file to Castle.Transactions.sln. * This version also uses haf/Castle.Releases -- it's pretty easy to update NHibernateFacility and this project by "git pull -s subtree Releases master", so I think it's a possible way forward for manage the buildscripts. Tell me what you think about this. * AutoTx is tracking Transaction Services exactly. I'm considering merging also the assemblies, but first I want the beta out of the door. Lingering problems: * Uses Windsor 2.5.1.2127 as I'm getting unexpected NullReferenceException in NHibernateFacility on .Net 4.0 with Windsor 2.5.2 NET40 and Windsor 2.5.3 NET40. A reproducible problem occurs at https://github.com/haf/Castle.Facilities.NHibernate/commit/bc2257cd4e0992f1d2bde70de14da383910927b9 for the linked libraries in /packages --> 1. Set up .\SQLEXPRESS, and a database "CastleTxTests" --> 2. Run "rake" to run tests, you need first to run "gem install rake albacore version_bumper" I hope that reverting to an earlier version will allow me to release something till the root cause is found. Remaining for Beta: * Awaiting/WaitAll on Tasks created with Fork=true at the end (Commit/ Rollback) of a transaction, and throwing an aggregate exception (wrapped in a TransactionException or otherwise), to avoid having failed DependentTransaction-tasks throw on finalizers. * ILMerging Reactive and Interactive Extensions to internal visibility to avoid the direct dependency. * Migrating solution to open wrap (owrap_test-branch is left to merge, only thing left for me to merge is the command line build version setting) --> If owrap 1.1 delays, I'll do dependency tracking with nuget in the mean-time and then merge the branch with owrap 1.1 later. The same goes for a fix or a root cause of the NullRefEx from Windsor/.Net and the Windsor dependency. At least this is my idea. Remaining for RC/GA: * AsyncCommit/AsyncRollback -> This could be pushed to v3.1 also and probably will. Otherwise, if the beta above goes well, it will be made into a RC for a week (or something like that) and then be released as v3.0. v3.1 could then have the async features and could also target Windsor 3.0 when that is released. * Stable usage a few days in customer projects without leaks and problems together with NHibernateFacility (going to start another thread on that) Henrik On Apr 25, 10:54 pm, Henrik <[email protected]> wrote: > I am happy to announce a new alpha release! > > Get it while the bits are > fresh!https://github.com/haf/Castle.Services.Transaction/downloads > > This is a sort of 'preview' of things to come; public API and new > features. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
