title: Define an initialization order of WebActivator.PreApplicationStartMethod classes
body: <p>I have several WebActivator.PreApplicationStartMethod decorated classes.</p>
  
  <p>One is for Ninject, another class for AwesomeMVC and a third one is for background task scheduler.</p>
  
  <p>The problem is that the scheduler class needs to take advantage of the dependecies, that are resolved by IoC container.</p>
  
  <p>My questions are:</p>
  
  <ol>
  <li>Can I have several WebActivator.PreApplicationStartMethod classes?</li>
  <li>Can I define order, in which they are initialized, so that IoC, being the most important, comes first?</li>
  <li>Can WebActivator.PreApplicationStartMethod static class instances rely on IoC container to resolve their constructor-defined dependencies?</li>
  </ol>