I written the document that might help the people choosing among DataObjects.Net and NHibernate to make a decision. Currently its second part related to feature-based comparison (feature matrix) is actually a preliminary one (that's explained in the document), so later I'll rewrite it. But anyway, I hope this will be helpful.
As usual, any comments and suggestions are welcome.
Monday, November 08, 2010
Thursday, November 04, 2010
Monday, November 01, 2010
Sorry for keeping the silence - I really haven't been writing here for a while. Usually this means we're quite busy with some new stuff, and in this case this is absolutely true. We're working on two main features we're going to bring quite soon:
It is almost finished, and will be launched quite soon. Few screenshots:
Hopefully, you'll like it.
As I wrote, we implement a set of dramatic changes there, but mostly they are related to refactoring we planned for pretty long time. Most important changes there include:
All above changes are mainly related to API. But certainly, this isn't all:
All these changes (along with the dedicated web site) must make the product much more user-friendly - especially, for its adopters.
v4.4 will be released during November.
We're pushing the development of DataObjects.Net in two directions:
As you see, initial release of v4.4 is mostly focused on initial user experience and compatibility / similarity with competitors, but its subsequent updates (v4.4.X) will be devoted mainly to extensions.
Our further (pretty near) plans include:
This update includes a set of bugfixes; probably, the most important one is multithreading bug in prefetcher.
IMPORTANT, PLEASE READ CAREFULLY:
1. You must upgrade to this version, if your trial is expired today. A hard-coded limitation of operational period is extended to February 1st, 2011 in this version. Certainly, this is related to trial version only. 60-day expiration of trial version is still intact.
2. It's strongly recommended to change just DataObject.Net assemblies while upgrading to this version. You must run the upgrade in PerformSafely or Perform mode.
3. We've fixed issue 813 in this version; the issue affects on default mapping. So if you used: