home / Change Log Browser

Change-logs for the LLBLGen Pro system

Below you are able to browse through the changelogs of all elements of the LLBLGen Pro system for various versions. There's also an easy to use search function for you available (shown when applicable) which allows you to search through all the change log entries using Full text search queries.

Application

LLBLGen Pro 4.2

All changes logged for:

  • Application: LLBLGen Pro 4.2


Number of logged changes found: 167

Change type Package Component For build Logged on Change text
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 02162015 16-Feb-2015 GuidByteArrayConverter returned a byte[] as default value, which should have been Guid.Empty
Fix Designer 4.2 Designer Core 4.2 February 16th, 2015 16-Feb-2015 GuidByteArrayConverter returned a byte[] as default value, which should have been Guid.Empty
None Designer 4.2 Designer Core 4.2 February 12th, 2015 12-Feb-2015 Fix of February 5th introduced a NullReferenceException condition when a relationship was saved with one or more field relationships without an FK field: loading the project again would then result in an NRE in the code added on February 5th.
Fix Designer 4.2 Designer GUI 4.2 February 9th, 2015 09-Feb-2015 When the designer was run windowed on a secondary monitor and that monitor was disconnected after the designer was closed, the designer was opened outside the visible area of the monitor still connected. It now opens at 0,0 of the visible area of the connected monitor if it is opened outside the visible area of the currently connected monitors.
Fix Designer 4.2 Designer Core 4.2 February 5th, 2015 05-Feb-2015 When an entity had a compound FK pointing to itself (so multiple fields of the FK were also part of the PK and effectively pointed to themselves) it could be the length / precision / scale values of the FK fields (and thus pk fields) were reset to the defaults due to type syncing during project load.
Fix Designer 4.2 Designer Core 4.2 January 29th, 2015 29-Jan-2015 Added some fail save checks so when the user closes the designer during code gen inside vs.net (as vs.net allows that to happen), it will not bork with a disposed exception.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 01272015 26-Jan-2015 Linq: Corrects an issue introduced with fix on January 5th, where metaData.Entity.Take(1) would crash in the enumerator creation method.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 01212015 21-Jan-2015 Fixed some small memory leaks in First/FirstOrDefault/Single/SingleOrDefault/FetchFirst etc. queries in Linq and Queryspec as well as nested entity queries in projections in Linq and Queryspec, where the container collection used to fetch the element(s) wasn't cleared so potentially could stay in memory due to an event handler referenced from the entity fetched.
Change Runtime Libraries 4.2 Runtime Libraries 4.2 01212015 21-Jan-2015 Oracle, ODP.NET: change: for like expressions, the parameter is now set to the type of the field used in the Like expression instead of always the default type Varchar2 using the following rule: NClob will result in an NVarchar2, Clob in a Varchar2, NChar/Char/Varchar2/NVarchar2 in a parameter of the same type and it falls back on the default Varchar2 if the type is different
Fix Templates 4.2 Templates 4.2 01092015 09-Jan-2015 Linq to Sql: if a subtype was mentioned earlier in an xml mapping file, it could be the xml mapping file was considered invalid by the Linq to Sql context.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 01052015 05-Jan-2015 Linq: First or Single or Default variants called on a query which results in a set of sets (e.g. metaData.Customer.Select(c=>c.Orders).First()) would crash at runtime due to a cast violation as the post processor to obtain the first value didn't properly work with a set of sets.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 12122014 12-Dec-2014 Linq: if an entity instance was present in a projection, and a field F from the same entity which is present in the projection was placed in the type projected (e.g. : select new { Customer=c, CustomerId = c.CustomerId}), the field F would not be readable from the resultset.
Fix Templates 4.2 Templates 4.2 12112014 11-Dec-2014 Entity Framework, Code first: Fields which type was set to a value type didn't get the HasColumnName() method emitted, even though this was required to make value typed fields be useable, as EF doesn't infer the field name from the value type field name, but uses the complete valuetype + field name by default.
Fix Templates 4.2 Templates 4.2 12112014 11-Dec-2014 Entity Framework, Code first: If the project had Typed View definitions (which are ignored in code first projects), the generated context still had a typedview namespace reference
Fix Templates 4.2 Templates 4.2 12112014 11-Dec-2014 Entity Framework, Code first: FK fields which had a different name than their target fields and when FK fields were ordered to be generated, didn't get a HasColumnName() call
Addition Templates 4.2 Templates 4.2 12092014 09-Dec-2014 LLBLGen Pro: added type default values for DateTimeOffset, SByte, UInt, UShort, ULong, TimeSpan
Fix Templates 4.2 Templates 4.2 12092014 09-Dec-2014 Entity Framework: Stored procedure names with double quotes weren't always properly escaped, creating uncompilable code.
Fix Drivers 4.2 Drivers 4.2 12052014 05-Dec-2014 Sybase iAnywhere / ASA driver: For obtaining view columns, the sp_columns stored procedure was used, which isn't correct, as it returns columns in ASE format, which could lead to wrong types.
Fix Drivers 4.2 Drivers 4.2 12051214 05-Dec-2014 Sybase iAnywhere / ASA driver: TIME and TIMESTAMP were seen as the same type, which isn't correct.
Fix Designer 4.2 Designer Core 4.2 December 4th, 2014 04-Dec-2014 When a root of an inheritance hierarchy was copied and not its subtypes, some inheritance information was carried over when the entity was pasted into another project. This has been corrected in the importer plugin as it is used for copy/paste as well.
Addition Documentation 4.2 Documentation 4.2 11242014 24-Nov-2014 Added info about the trace info emitted now by ORMPersistenceExecution if an action is denied by an authorizer/allowed action combination.
Addition Documentation 4.2 Documentation 4.2 11242014 24-Nov-2014 Added remark about allowed action combinations as a breaking change for entities mapped onto views.
Addition Runtime Libraries 4.2 Runtime Libraries 4.2 11242014 24-Nov-2014 Added trace information to ORMPerformanceExecution at Info level (3) for when a persistence action (insert/update/delete) was denied, either by an authorizer or by the defined allowed action combination.
Fix Designer 4.2 Designer Core 4.2 November 19th, 2014 19-Nov-2014 When a table field was marked for deletion and it was still used in a field mapping and update DDL SQL scripts were exported, the table field was correctly removed from the catalog data but not from the field mapping, causing the project not to be loadable after it was saved.
Change Runtime Libraries 4.2 Runtime Libraries 4.2 11102014 10-Nov-2014 Projections: small performance improvement for projection based queries.