Contents tagged with .NET
-
LLBLGen Pro v5.5 has been released!
After a two week beta period, we’ve released LLBLGen Pro v5.5! To see what’s new, please visit the New features page on our website or go to the beta announcement blog post which lists all the small changes in one place.
-
LLBLGen Pro v5.5 beta has been released!
Last Friday we’ve released LLBLGen Pro v5.5 beta! We expect to release the RTM in a week or two. Below is the list of what’s new in this release. I’ll describe some of the new features in more detail in articles in the coming weeks. The main focus was on our own ORM framework, the LLBLGen Pro Runtime Framework, this time around.
-
LLBLGen Pro v5.4 has been released!
Today we’ve released LLBLGen Pro v5.4! This release comes packed with a lot of small enhancements and some bigger ones. See below for the full list of changes. This update is a free update for all users with an active subscription.
-
Optimizing memory usage
In this post I’ll discuss some memory optimization work I’ve done recently on the LLBLGen Pro runtime framework, v5.3.2. This is a popular (commercial) .NET ORM. LLBLGen Pro is on the market since 2003 and has seen a lot of refactoring work internally over the years, among them performance optimizations and memory usage optimizations. With new features come new challenges to make the overall framework perform the same or even faster and still perform the new features as well, so optimizing the core engine is a recurring effort.
-
.NET (Micro)ORM fetch benchmark results and the fine details
For some time now I maintain the RawDataAccessBencher repository on github, and once in a while I run the suite of benchmarks and post the results. In the benchmarks I included all major micro-ORM and full ORM frameworks for .NET which have a significant group of users. The benchmarks are typical ‘micro’ benchmarks in that they run for a relatively short period of time. They also focus solely on fetch performance, how fast the given framework can create a query, fetch the resultset from the database server (on another machine on the network) and materialize objects from the resultset.
-
LLBLGen Pro v5.3 Beta has been released!
We've released LLBLGen Pro v5.3 beta! Since the EAP we’ve added new functionality and tweaked some things too, based on feedback. Below is the full list of what’s new in v5.3 Beta, and this is also the list of new stuff we’ll include in v5.3 RTM, which is expected within a week or two.
-
LLBLGen Pro v5.3 EAP Released!
After a failed attempt to port our LLBLGen Pro Runtime Framework to .NET Standard 1.6, we’ve ported it to .NET Standard 2.0 and managed to port over almost all features (A very small set of features aren’t supported but you either won’t miss them, or they’re out of our hands and limitations of .NET Core/standard)! This means finally there’s a full O/R mapper framework available for .NET Core 2.0 that’s fast, fully featured and ‘battle-tested’ for many years.
-
LLBLGen Pro v5.2 has been released! (and first quickstart video posted)
LLBLGen Pro v5.2 has been released! It’s a version with a couple of ‘highlight features’ like full model analysis and a lot of smaller new features / changes which together form a large list of new goodies, see my previous post on LLBLGen Pro v5.2.
-
LLBLGen Pro v5.1 Beta has been released!
LLBLGen Pro v5.1 beta is now available. It’s the last public build before RTM, which I hope will be within a week or two. Since EAP2 we’ve added the following features:
-
The .NET support black hole
Today I ran into a bit of an issue. A work-item for LLBLGen Pro v5.1 is to support all the new features of SQL Server 2016. One of the features of SQL Server 2016 is ‘Always Encrypted’. You can enable this feature through the connection string, and after that all data-access is encrypted, no further coding needed. As this is a connection string setting, it’s enabled in every ORM out there out of the box, also in ours. That’s of course not the problem. The problem is adding more control over this feature to the developer writing code which targets SQL Server 2016.