Providing or Filtering assemblies when registering areas for an ASP.NET MVC 2.0 application

Question

I have a large application that currently exists as a hybrid of WebForms and MVC 2.0. Startup of my application is dreadful, and the culprit is primarily because of the

Answer 1

I'm not 100% sure if this will help in this specific case but could you combine all your 3rd party dlls into one dlls (hence removing the processing of all the individual files). This is what we have done using ILMerge at build time. Works like a charm. It will still need to look at the metadata for the dll (which will now be a bit larger) but it wont have to do as much IO.