In January 2007 we started designing and developing v2.5 of LLBLGen Pro and today is the day we finally are able to release our work to our customers
On wednesday the 22nd we hope to release the demo version of v2.5 as well as an updated main site to the rest of the world .
To download the full installer of v2.5, please login with your v2.0 customer id and click on 'v2.5' at the left to get to the download section of v2.5
A BIG Thank You! goes out to all the people who have discussed with us about features for v2.5, have beta tested v2.5 and have contributed with ideas to make it even better. Thanks!
To answer some questions which will likely pop up:
Q: Where is Template Studio v2.5?
A: We couldn't get it finished today, so it will be released in the coming days
Q: Where is the documentation in PDF format?
A: We're planning to release several different manuals in PDF format and to convert the documentation to these different formats takes some time. Expect it in the coming weeks
Q: I'm not a customer, where is the demo?
A: It will be released on Wednesday the 22nd or thereabout.
Q: I get a crash with the designer when I create a new project on Oracle 10g saying I don't have ODP.NET installed (this is also valid for DB2 and MySql)
A: We've build the drivers and DQEs for Oracle 10g ODP.NET, MySql and DB2 against the latest provider builds. We also have included builds of the drivers and dqe's against the providers used in v2.0. Please see the What's New page for details about how to use the designer with these drivers and where they're located. Also see the Using the generated code -> Compiling the code for details about the DQEs
Q: Where are the examples?
A: We'll release the examples in the coming days.
Q: Is HnD already updated to the new v2.5?
A: No, but we're planning to do that soon.
For the new features, please check the What's new section in the manual. It was a long period of hard work, but I think it was worth it . For completeness, the last changelog since the RC1 build:
20-aug-2007
- REVERTED: DRIVERS: The view meta data retrieval for SqlServer has been reverted as the code turned out to be unreliable but it was unclear why. Due to time constraints we can't let this hold up the project, so we reverted the code. The routine is left in the sourcecode for users who want to utilize it.
- CHANGED: RUNTIMELIBS: DaoBase.ReadRowIntoFields and DataAccessAdapterBase.ReadRowIntoFields are now protected virtual so you can add low-level value caching, for example string interning, during entity fetches. This could lower memory footprint.
- ADDED: DESIGNER: Task/Taskgroup execution now log their display names together with their real names if the display name was filled in. This greatly enhances the logging value of the task execution process.
- ADDED: RUNTIMELIBS: Added small guard clause in routine which collects fields to update. If there isn't a fieldpersistenceinfo object for a field (e.g. manually added field to the fieldslist) the field is skipped.
- FIXED: TEMPLATES: The CustomInheritanceInfoProviderSingletonCode user code region had the wrong name.
- FIXED: RUNTIMELIBS: UnitOfWork2 entities weren't serialized/deserialized properly when fast serialization was enabled.
- FIXED: RUNTIMELIBS: Auditing for Update of entities directly was triggered twice (Selfservicing)
- FIXED: RUNTIMELIBS: Auditing for Delete of entities directly was always called no matter if there weren't any entities affected. (selfservicing)
- FIXED: DESIGNER: A discriminator field could be used as an fk field in a relation (both in custom relations and in db based relations. ). This is no longer possible: FK fields can't be made a discriminator field, and relations won't be created / can't be created between fields where one of them is a discriminator field.
- FIXED: TEMPLATES: When no entities were in the project, the code didn't compile as there was still a class called CommonEntityBase which referred to a namespace which didn't exist.