Home/ Questions/Q 6383551
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T02:39:49+00:00

I have troubles consuming unity container in ASP.NET MVC3 application. I have several project

  • 0

I have troubles consuming unity container in ASP.NET MVC3 application.

I have several project with interfaces and their implementation. All interface to concreete type binding is performed in the application startup method.

I have several problems with this aproach:

1) How to handle registration of types that are not dirrectly required by MVC application but by classes that it using (Repository uses ContextManager to retrieve context instance). If this class is located in assembly that is not used by mvc app, I will have to add reference to it.

2) How to share configured container? Should I create separate assembly with static class wich will store created by mvc app container?

3) What kind of unity container usage can possibly bring cross thread problems? How to register singletons so that they will be avaliable only in this thread (web server call) etc.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    1. You should explicitly reference all assemblies to your ASP.NET MVC application. It is the outermost layer in the onion architecture and it is allowed to know about inner layers. All assemblies must be in the bin folder anyways so the ASP.NET MVC application will know about them one way or another. Just externalize your DI framework configuration into a single place in your ASP.NET MVC application.
    2. See 1.
    3. Per thread storage could be dangerous in ASP.NET. Per HTTP Context is better.
    • 0