autofac/autofac.extras.commonservicelocator — explained in plain English
Analysis updated 2026-07-27 · repo last pushed 2026-07-09
Connect Autofac-managed services to third-party libraries that rely on the Common Service Locator interface.
Use frameworks that expect a Common Service Locator while keeping Autofac as your dependency injection container.
Share application components across different libraries through a common service-lookup interface.
| autofac/autofac.extras.commonservicelocator | d2phap/happlabox | drwuu/playsmart-unity-uitoolkit-extensions | |
|---|---|---|---|
| Stars | 7 | 7 | 7 |
| Language | C# | C# | C# |
| Last pushed | 2026-07-09 | 2023-03-14 | — |
| Maintenance | Active | Dormant | — |
| Setup difficulty | easy | easy | easy |
| Complexity | 2/5 | 2/5 | 2/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Autofac and the Common Service Locator NuGet packages, but no external infrastructure or API keys needed.
This project is a small bridge that connects two tools used in .NET applications: Autofac and the Common Service Locator. Autofac is a popular "dependency injection" container, which is a way for applications to automatically provide the right pieces of code to the right places without hardwiring everything together. The Common Service Locator is a shared interface that lets different libraries ask for pieces of code in a consistent way, regardless of which specific container is running in the background. This package makes Autofac work with that shared interface. Without a tool like this, you can run into a problem when building larger applications. Say you are using Autofac to manage your app's components, and you bring in a third-party library that also needs to fetch services at runtime. That library might not know about Autofac specifically, but if it knows about the Common Service Locator, it can ask for what it needs through that shared interface. This package translates between Autofac and the Common Service Locator so they can talk to each other. The setup is straightforward. You configure Autofac as you normally would, then create an instance of the AutofacServiceLocator class and register it as the active service locator. From that point on, any code that asks the Common Service Locator for a service will get it through Autofac behind the scenes. This is mainly for developers building .NET applications who are already using Autofac and need to work with libraries or frameworks that expect a Common Service Locator. It is a niche integration package rather than a standalone tool, which explains its modest community footprint. The README does not go into deeper detail about advanced scenarios or tradeoffs, pointing instead to the broader Autofac documentation for those topics.
A small bridge that lets Autofac, a .NET dependency injection tool, work with the Common Service Locator shared interface so third-party libraries can request services without knowing about Autofac specifically.
Mainly C#. The stack also includes C#, .NET, Autofac.
Active — commit in last 30 days (last push 2026-07-09).
The README does not mention a license, check the repository or source files for licensing details.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.