autofac/autofac.extras.nhibernate — explained in plain English
Analysis updated 2026-07-15 · repo last pushed 2026-05-20
Connect NHibernate internal objects to application services like loggers when using Autofac for dependency injection.
Build a .NET app using NHibernate for database access while keeping all components organized through Autofac.
Allow NHibernate event listeners or data objects to access services like email senders without awkward workarounds.
| autofac/autofac.extras.nhibernate | froggacuda/tl2-lobby | d2phap/happlabox | |
|---|---|---|---|
| Stars | 6 | 6 | 7 |
| Language | C# | C# | C# |
| Last pushed | 2026-05-20 | — | 2023-03-14 |
| Maintenance | Maintained | — | Dormant |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 2/5 | 3/5 | 2/5 |
| Audience | developer | general | general |
Figures from each repo's GitHub metadata at analysis time.
Project is archived and retired since 2015, so usage relies on an external blog article linked in the README rather than maintained documentation.
Autofac.Extras.NHibernate is a bridge library that connects two .NET tools: Autofac, which handles dependency injection (a way of automatically supplying software components with the resources they need), and NHibernate, a system for working with databases. Normally, NHibernate creates its own internal objects behind the scenes, and those objects can't easily tap into the rest of your application's resources. This package fixes that gap. When a program runs, it often needs to connect different pieces together at runtime. Autofac manages this by maintaining a container of ready-to-use components. NHibernate, for its part, works with database records by turning them into code objects. The library works by swapping in a custom provider that tells NHibernate to ask Autofac's container whenever it needs to build one of its behind-the-scenes objects. This means those internal pieces can be configured and connected just like the rest of your application. A developer would use this when building a .NET application that relies on NHibernate for database access but also uses Autofac to keep code organized and maintainable. For example, if a developer wants NHibernate's internal event listeners or data objects to access application services like a logger or an email sender, this integration makes that possible without awkward workarounds. The project is archived, meaning it is no longer receiving updates or support. It was put into a limited maintenance mode in 2015 and officially retired with no further development. Anyone considering it should be aware that it is a legacy package, and the README points to an external blog article for usage details.
A bridge library for .NET that lets NHibernate's internal database objects use Autofac's dependency injection, so behind-the-scenes components can access app-wide services like loggers. Archived since 2015 with no updates.
Mainly C#. The stack also includes C#, .NET, Autofac.
Maintained — commit in last 6 months (last push 2026-05-20).
The license is not mentioned in the explanation, so it is unclear what permissions apply.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.