Remember the days when every website wanted to maintain its own database of users and related data? To download some restricted content you have to register there, provide a password, successfully forget it after a couple of minutes and use "Restore password" feature every time you visit the website later.
The same kind of website was our corporate X-tensive.com website. Moreover, our support website was configured to work with users from x-tensive.com only. Until...
Until we rejected the model above and switched to OpenID authentication scheme and made all versions of DataObjects.Net available for download without registration. The same change was applied to support.x-tensive.com — now anyone who has OpenID may log in and post an issue/feedback.
Having that done, we closing user registration area on x-tensive.com as now it doesn't have any sense, however, all user accounts will be preserved and users may sign in in their x-tensive.com profile as usual.
Note for owners of DataObjects.Net licenses: we launched new customer area, don't miss it. All your license-related data is migrated from x-tensive.com to get.dataobjects.net website.
Tuesday, August 21, 2012Moving towards openness
Labels:
announcements,
community,
licensing,
support,
website
Saturday, August 11, 20129-th anniversary, new prices, community edition and much more
Hello everybody!
Today we are celebrating the fact that 9 years ago the first version of the award-winning, revolutionary ORM named DataObjects.Net was released. Due to this we are launching our new edition & pricing policy, new customer area and we are hoping that you'll like it. DataObjects.Net 4.5.4 finalThe main change in this version in addition to all listed in RC 1 & RC 2 is Community edition support. Download it from official website or from NuGet repository.Community editionMany users requested Community Edition of DataObjects.Net with full set of features and with possible limitation of number of persistent types. Well, here it is, the Community edition is rolled out today. It has the following characteristics:
Professional editionProfessional edition is available for $150 and includes 2 hardware licenses. Comparing to the previous pricing scheme (500 euro), the price cutting is more than 65%. Moreover, 3 items are available for $120 each and 5 items - just for $100.Get Professional edition. Ultimate editionUltimate edition also gets its new shiny price, from now it is available only for $1500 instead of 2500 euros. The edition provides the unlimited number of hardware licenses. Ultimate edition contains access to the source code no more.Get Ultimate edition. Access to source codeWe extracted 'Access to source code' feature to a separate package to make it available to all our customers, not only for Ultimate edition owners as it was earlier. So anyone, even an owner of Community edition has a chance to dive deep in DataObjects.Net white and black magic. The price for the package is set to $500. The source code is available in download area of our website.Get access to source code. New customer areaWe are inviting you to the new customer area that we have built for you for better and easier license management. No more registration, we migrated to OpenID authentication scheme. We added license sharing feature, so your developers won't bother you with anything concerning licenses and hardware locks, you may share the license with all of them.The area can be accesses by clicking on 'My Account' link in the main menu: ![]() Soon you'll receive our invitation e-mail. We need you to log in the area to get your licenses associated with your account. Don't forget to periodically check your mailboxes! Join the celebration! Thank you! Links:
Labels:
announcements,
community,
licensing,
pricing,
website
Monday, August 06, 2012DataObjects.Net Extensions 4.5.3
DataObjects.Net Extensions are updated to the latest version.
What are these so-called extensions? They are small projects that extend standard functionality of DataObjects.Net core. Version 4.5.3 contains of the following extensions: Each of them has a corresponding nuget package so they can be installed separately or in any combination. Using NuGet is a recommended way of installing the extensions. DataObjects.Net Extensions are published on CodePlex with source code opened. You may also want to check the documentation before start using them. The extensions are maintained by Xtensive engineers and by volunteers from DataObjects.Net community. Changes
Download
RoadmapThere are several new extensions that are now being developed and tested:
Thank you!
Labels:
announcements,
extensions,
releases
Friday, August 03, 2012DataObjects.Net 4.5.4 RC 2
Today we are publishing the next release candidate for the upcoming version of DataObjects.Net.
Changes
Download
Labels:
announcements,
releases
Friday, July 13, 2012DataObjects.Net 4.5.4 RC
Today we are publishing the next release candidate for the upcoming version of DataObjects.Net.
ChangesChanges in 4.5.4 RC:[main] Fixed comparion of Key fields in interaces in LINQ queries under certain scenarios[main] Visual experience of License Manager has been improved [main] Fixed incorrect handling of RemoveFieldHint under certain scenarios [main] Fixed incorrect behavior in DisconnectedEntityState.UpdateOrigin method Download
Labels:
announcements,
releases
Monday, July 02, 2012DataObjects.Net 4.5.3 is released
Today we are publishing the final version of DataObjects.Net 4.5.3.
ChangesChanges in 4.5.3 comparing to 4.5.3 RC 4:[main] Fix NullReferenceException under certain validation scenarios[main] Fixed memory leak in Domain.Build() process Download
Labels:
announcements,
releases
DataObjects.Net 4.4.3 is out
Today we are publishing the final version of DataObjects.Net 4.4.3.
ChangesChanges in 4.4.3 comparing to 4.4.3 RC 2:[main] Fixed memory leak in Domain.Build() process[main] RemoveFieldHint, ChangeFieldTypeHint are now correctly handled for Structure fields Download
Labels:
announcements,
releases
Friday, June 22, 2012DataObjects.Net 4.5.3 RC 4
Today we are publishing the next release candidate for the upcoming version of DataObjects.Net.
ChangesChanges in 4.5.3 RC4:[main] Fix POCO materialization when subqueries are used[main] Fix translation of multiple aggregate subqueries when calculated columns are used [main] Throw descriptive exception when RenameTypeHint has invalid old type name [main] Improve detection of serialization failure errors for SQL Server Download
Labels:
announcements,
releases
Thursday, June 14, 2012DataObjects.Net 4.5.3 RC 3
Today we are publishing the next release candidate for the upcoming version of DataObjects.Net.
ChangesChanges in 4.5.3 RC3:[main] Finally, change log is included in distribution =)[main] RemoveFieldHint, ChangeFieldTypeHint are now correctly handled for Structure fields [main] Correctly skip full-text indexes if storage does not support them [mysql] Fixed index direction support for MySQL [mysql] Improved translation of DateTime.Date for MySQL [mysql] Fixed incorrect translation of Math.Truncate and Decimal.Truncate for MySQL [mysql] Fixed incorrect translation of String.IndexOf for MySQL [mysql] Fixed mapping of Single and Double types for MySQL [mysql] Fixed schema extraction with case-sensitive collation for MySQL [postgresql] Hex format for byte array literals is used for PostgreSQL 9.0 and later Changes in 4.5.3 RC2 (wasn't officially announced):[main] Validation now works in ClientProfile[main] Fixed various errors with certian EntitySet usage scenarios in ClientProfile [main] Fixed "Scope can't be disposed" error under certain query enumeration scenarios Download
Labels:
announcements,
releases
Saturday, May 12, 2012DataObjects.Net 4.5.3 RC and 4.4.3 RC3
DataObjects.Net 4.5.3 RC and 4.4.3 RC3 are available.
Both contain the same fixes that are listed below:
Rollback exceptions suppression
Option SessionOptions.SuppressRollbackExceptions tells DataObjects.Net to catch (and log) any exception that occurred during rollback. Rollback typically occurs when some exception is already thrown. So any exception during rollback will cause original exception to be lost. New option could be used to prevent such behaviour.
Migration path
No special migration is required.
Subscribe to:
Posts (Atom)
|
SubscriptionBlog Archive
Labels
|








