News, examples, tips, ideas and plans.
Thoughts around ORM, .NET and SQL databases.

Monday, November 14, 2011

Upcoming major update

Hello everybody,

Despite the fact that there was no news in this blog from DataObjects.Net team for a couple of months, this doesn't mean that we were having rest or watching endless TV-series. We've been fixing bugs and inventing some really cool features for our customers. Let's take a closer look at the details.

First of all, bugs fixed:
Updates to the existing functionality:
The most interesting part, features:
Simply put, the features are so dramatic that we are releasing the stuff as a major version update. DataObjects.Net 4.3.7 branch will become 4.3.8 and 4.4.0 will be known as 4.4.1 (one of our lead developers call this update as DataObjects.Net R2 and I understand him pretty much). 

While the above mentioned changes are being thoroughly tested under various environments and being prepared for the release, we'll describe the features listed above in a dedicated series of posts.

Thank you! Stay tuned.


  1. Nice to hear from you again.

    In relation to the 4.4.1 release what is the status of the 4.5 Beta (4) release.?

    I assume that geoSpartical functions have been implemented for SQL Server due to a client request as PostGres/PostGis is a much more widely used GeoSpartical database (and free). Are there any plans to implement this in the PostGres driver?

  2. Hello Tony,

    Right after the 4.3.8 & 4.4.1 branches are out, we'll return to active 4.5 development.

    As for geospatial data types support, you are right, a request was the reason for that feature.

    The next 4.5 beta will have slightly reorganized structure of assemblies, we are doing this to increase the extensibility of various SQL servers support, e.g. this will help us to add support for geospatial or any other data types and functions with minimal efforts and without making any changes to the core part of the ORM.

  3. This comment has been removed by the author.