Skip to content
This repository has been archived by the owner on Jan 24, 2021. It is now read-only.

Split IStartup registration and initialization into two seperate concerns #569

Closed
thecodejunkie opened this issue Mar 22, 2012 · 0 comments · Fixed by #635
Closed

Split IStartup registration and initialization into two seperate concerns #569

thecodejunkie opened this issue Mar 22, 2012 · 0 comments · Fixed by #635

Comments

@thecodejunkie
Copy link
Member

Today an IStartup lets you both register dependencies and perform initialization work. This makes ordering in the Bootstrapper initialization method tricky. We should split the concerns into two interfaces

  • IApplicationStartup - Lets you do Initialize
  • IApplicationRegistrations - Lets you do TypeRegistrations, CollectionTypeRegistrations and InstanceRegistrations

IApplicationRegistrations should happen before IStartup in the Bootstrapper.Initialise() method.

This will also bring the functionality up to par with the changes that was introduced with ConfigureApplicationContainer/ConfigureRequestContainer and ApplicationStartup/RequestStartup

NOTE We probably should also introduce IRequestStartup and IRequestRegistrations

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant