NHibernate Releases 5.1 with support for .Net Core and .NetStandard 2.0

The NHibernate Team has done it! Release 5.1 of the famous ORM for .Net supports both the full .Net Framework and .Net Core. Great work! The library is actually cross compiled for net461, netCoreApp2.0 and netStandard2.0 to account for some of the subtle nuances between net461 and core and to support older tooling that doesn’t know how to work with netStandard libraries.

Caveats

As noted in the release notes, there are a few caveats when running on Core:
  • Binary serialization is not supported - the user shall implement serialization surrogates for System.Type, FieldInfo, PropertyInfo, MethodInfo, ConstructorInfo, Delegate, etc.
  • SqlClient, Odbc, Oledb drivers are converted to ReflectionBasedDriver to avoid the extra dependencies.
  • CallSessionContext uses a static AsyncLocal field to mimic the CallContext behavior.
  • System transactions (transaction scopes) are untested, due to the lack of data providers supporting them.

WebSessionContext and ASP.Net Core

Also, WebSessionContext is not compatible with ASP.Net Core due to changes in how HttpContext is accessed and managed in ASP.Net Core. As an alternative, you can use the ASP.Net Core dependency injection to manage the life cycles of Configuration, ISessionFactory, and ISession. For example (over simplified for brevity):
services.AddSingleton<NHibernate.Cfg.Configuration>((provider)=>{ 
    var cfg = new NHibernate.Cfg.Configuration();
    cfg.Configure("hibernate.cfg.xml");
    cfg.AddXmlFile("hibernate.hbm.xml");
    return cfg;
});

services.AddSingleton<ISessionFactory>((provider)=>{ 
    var cfg = provider.GetService<NHibernate.Cfg.Configuration>();
    return cfg.BuildSessionFactory();
});

services.AddScoped<ISession>((provider)=>{
    var factory = provider.GetService<ISessionFactory>();
    return factory.OpenSession();
});
In our opinion here at Milestone, this is the preferred way under ASP.Net Core to maintain ISession.

New Second-Level Caching Libraries

If you are using ASP.Net Core, NHibernate.Caches also gets some new packages supporting In-Memory Cache, Redis, Memcached, and SQL Server using the Microsoft.Extensions.DistributedCaching libraries.

More NetStandard/Core Support to Come!

Pull requests for NHibernate.Mapping.Attributes and NHibernate.Envers are in the works for NetStandard support thanks to our team here at Milestone. Keep an eye out for them on NuGet.
At Milestone, we’re working on some patterns and practices and new libraries for working with NHibernate in cloud-native ASP.net Core microservices. Stay tuned!

Comments

Post a Comment

Popular posts from this blog

Using NHibernate in Asp.Net Core

Starting with version 5.1, NHibernate now supports .Net Core and .Netstandard as well as the full framework. Let’s take a quick look at how to set it up in an ASP.Net Core 2.x/3.x application. Configuration As of this writing, NHibernate doesn’t support the configuration system within Asp.Net Core based on Microsoft.Extensions.Configuration. The good news is, you don’t have to use a  hibernate.cfg.xml  file or the   section in app.config. You can add the properies manually, and pull the values from Asp.Net Core’s configuration, taking advantage of all the goodies that come with it. This opens up a world of configuration deployment possibilities. var config = new Configuration (); IDictionary < string , string > properties = new Dictionary < string , string > { { "connection.connection_string" , Configuration . GetConnectionString ( "Default" ) }, { "dialect" , "NHibernate.Dialect.SQLiteDialect" }, ...
Read more

Adding New Microsoft Extensions to Legacy WCF and ASMX Web Services

I was asked by several people recently: Can I use dependency injection with my legacy WCF and ASMX web services? Microsoft has some new stuff they released with core–specifically, a new configuration system, caching, and logging providers. Can I use them in my legacy WCF and ASMX web services? The answer to both is yes you can! In fact, I recommend it! To illustrate this, we’ll take a look at taking a sample application that has a WCF service and a ASMX service and we’ll: Add dependency injection using Ninject. Add the new Configuration provider from the new  Microsoft.Extensions.Configuration  packages. Add caching functionality using Microsoft’s new  Microsoft.Extensions.Caching  packages. Use the new logging providers from  Microsoft.Extensions.Logging  packages. Dependency Injection We use Ninject, but you can just as easily use AutoFac or SimpleInjector as they also have packaged integrations for WCF. You can use other containers, bu...
Read more

Code Coverage for Multiple Projects in a Single Build using Dotnet Test and Coverlet

Most of the time, your solution will have more than one project and a test unit project for each of those. Azure DevOps only, as of this writing, only allows you to update a single code coverage summary. If you upload more than one, each overwrites the next and only the last one remains. To accomplish this, we can use the merge functionality in Coverlet . I use the MSBuild extension, because it is better suited for CI pipelines. In your test project XML, add the package... <PackageReference Include="coverlet.msbuild" Version="2.7.0">     <PrivateAssets>all</PrivateAssets>     <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference> Then, in your dotnet test command or msbuild command, tell it to use Coverlet and to merge results. If you're using Azure DevOps, your test task looks this... (line wrapped for read ability in the article) - task: DotNetCoreCLI@2 displayName: Test i...
Read more