Where in your solution do you typically put your StructureMap Registry classes?

Question

Here's the current layout:

Solution:

• Core

  • Domain
  • Interfaces

• DataAccess

  • Providers
  • Session

• Service

• UI

• UnitTests

• IntegrationTests

I typically try to keep my core domain entities / POCOs as light as possible without very many external dependencies.. So I was thinking it might make sense to put it in the Service layer as it typically has a project reference to all of the layers.

I have noticed that in CodeCampServer they have actually created a separate project called DependencyResolution for their IoC configuration:

http://code.google.com/p/codecampserver/source/browse/trunk#trunk/src/DependencyResolution

Thoughts?

Answer 1

Take a look at this post

Answer 2

IOC configuration should be off to the side. It doesn't necessarily need to be in a separate project, but it needs to be away from the application code. We put it in another project in CodeCampServer to make 'off to the side' more real. But in a current production app, we keep it in a separate namespace in our main project. We consolidated projects to increase compile time.