title: Providing or Filtering assemblies when registering areas for an ASP.NET MVC 2.0 application
body: <p>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 <code>AreaRegistration.RegisterAllAreas</code> call. More specifically, that it is using the <code>System.Web. Compilation.BuildManager.GetReferencedAssemblies</code> to enumerate all types in assemblies directly referenced by the application and test them to see if they derive from <code>AreaRegistration</code>.</p>
  
  <p>Unfortunately, I have a number of third-party assemblies that happen to be quite extensive, so this initial load can be pretty bad. I'd have much better results if I could tell it which assemblies to look for <code>AreaRegistrations</code>, or even register areas manually for the time being.</p>
  
  <p>I can gather up all the internals of <code>AreaRegistration</code> to create and invoke the registration, but I'm just curious if others have had and worked around this issue.</p>