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
Addition Designer 4.2 Designer Core 4.2 June 9th, 2015 09-Jun-2015 A preference setting, UseCurrentCultureForNameSorting, default true, has been added to solve the following: Ordering of elements by Name used the current culture set by the OS. By default this is still the case. Setting the preference UseCurrentCultureForNameSorting to false will make the designer and code generator use the invariant culture for all name ordering, be it in file persist, ordering of elements in the UI and in the code generator.
Change Runtime Libraries 4.2 Runtime Libraries 4.2 06032015 03-Jun-2015 Committing an empty DataScope would default to SelfServicing for its Unit of work as it couldn't determine the type of the template group used as there are no entities inside the scope. An empty datascope will now use a NoOpUnitOfWorkCore instance which does nothing (as there's no data) but will make an empty datascope be able to commit its work silently without errors.
Addition Drivers 4.2 Drivers 4.2 05152015 15-May-2015 PostgreSQL driver: Added JSon/JSonB support
Fix Designer 4.2 Designer Core 4.2 May 5th, 2015 05-May-2015 If a table was excluded from the schema (directly or indirectly), FKs which had the table on the PK side weren't excluded as well if they were contained by a table in another schema.
Fix Designer 4.2 Designer Core 4.2 May 5th, 2015 05-May-2015 If a table was marked for deletion, FKs which had the table on the PK side weren't marked for deletion as well.
Addition Designer 4.2 Designer GUI 4.2 February 9th, 2015 04-May-2015 Updated vsix package to support vs.net 2015.
Change Designer 4.2 Designer Core 4.2 April 16th, 2015 23-Apr-2015 Commented out npgsql line in config files for designer, as npgsql nowadays adds itself to machine.config.
Fix Templates 4.2 Templates 4.2 04162015 16-Apr-2015 Entity Framework, NHibernate, Linq to SQL: A macro on a setting for a base class name wasn't resolved to its true value
Fix Designer 4.2 Designer Core 4.2 April 16th, 2015 16-Apr-2015 A macro on a setting for a base class name wasn't resolved to its true value
Fix Designer 4.2 Designer Core 4.2 April 10th, 2015 15-Apr-2015 Code generator: If a type converter returned a generic type, it could be the code generated didn't compile as the generic type wasn't properly converted to a usable type for sourcecode.
Fix Designer 4.2 Designer Core 4.2 April 10th, 2015 10-Apr-2015 Copy / Paste or Import: When pasting / importing with mappings PK constraints weren't exported for new tables.They were present in the catalog meta data, but not seen as 'new' even though the table was new.
Fix Designer 4.2 Designer Core 4.2 April 10th, 2015 10-Apr-2015 Copy / Paste or Import: When pasting / importing with mappings, for every field in a newly created table a drop statement for the default constraint was created, which was unneeded.
Fix Designer 4.2 Designer Core 4.2 April 10th, 2015 10-Apr-2015 Copy / Paste or Import: When pasting / importing with mappings, FKs weren't properly marked as created by designer and a DDL SQL Update script wasn't including them.
Fix Designer 4.2 Designer Core 4.2 April 10th, 2015 10-Apr-2015 Copy / Paste or Import: When pasting / importing with mappings, UCs weren't properly marked as created by designer and a DDL SQL Update script wasn't including them.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 04102015 10-Apr-2015 Adapter, Transient error recovery: If a transient error recovery was needed on a stored procedure call, it could be the retry failed due to an exception related to parameters being added to a second command
Addition Runtime Libraries 4.2 Runtime Libraries 4.2 04072015 07-Apr-2015 Linq: Added better check code for when, due to e.g. usage of interfaces instead of dedicated types in queries, an entity factory wasn't retrievable because an interface type was all that's known at that point in the expression tree.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 03232015 23-Mar-2015 When a TransientErrorRecovery was used with a RecoveryStrategyDelayType Exponential, it could result in a timespan overflow if enough retries were attempted to overflow Timespan based on the delayparameter.
Addition Runtime Libraries 4.2 Runtime Libraries 4.2 03192015 19-Mar-2015 Added async variants of FetchQueryFromSource for both selfservicing and adapter to be able to fetch using query spec typedviews mapped onto stored procedures and which are generated as pocos asynchronously.
Fix Drivers 4.2 Drivers 4.2 03102015 10-Mar-2015 SQL Server driver: if more than the batch size amount of synonyms were selected (BatchSize is by default 250), only the elements in the last batch were added to the project.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 03092015 09-Mar-2015 Normal Binary serialization could ignore entities in a collection during deserialization if DoNotPerformAddIfPresent is set to true in the collection when the data was serialized
Addition Templates 4.2 Templates 4.2 03032015 03-Mar-2015 NHibernate v4 support added.
Addition Documentation 4.2 Documentation 4.2 02242015 24-Feb-2015 LLBLGen Pro Runtime Framework: Added RecoveryDelay documentation to the transient error recovery documentation
Addition Documentation 4.2 Documentation 4.2 02242015 24-Feb-2015 LLBLGen Pro Runtime Framework: Added nuget references to compiling docs
Addition Documentation 4.2 Documentation 4.2 02242015 24-Feb-2015 Added better clarity to the documentation of Entity Framework support how to compile the generated code.
Change Runtime Libraries 4.2 Runtime Libraries 4.2 02182015 18-Feb-2015 Linq: when a nested query had a limit (.Take(n)) specified and several additional IQueryable method calls were appended to the query, it could be the Take(n) call was copied to the outer queries as well as the original query. While this is harmless in practice, it is also useless processing so on some databases with less stellar optimizers the query could result in suboptimal performance.