DefaultHttpControllerTypeResolver swallows exceptions encountered during assembly.GetTypes(). There is no tracing there which makes debugging routing exceptions due to controller type load failures extremely hard.
I just got off a call from a customer who was clueless due to this and also hitting https://aspnetwebstack.codeplex.com/workitem/1075
As bonus points improve the whole tracing scenario around controller type resolution.
Comments: Fixed in commit [28c2c138b008](https://aspnetwebstack.codeplex.com/SourceControl/changeset/28c2c138b00857fbe5604acd51b6b78de0231a2c)
I just got off a call from a customer who was clueless due to this and also hitting https://aspnetwebstack.codeplex.com/workitem/1075
As bonus points improve the whole tracing scenario around controller type resolution.
Comments: Fixed in commit [28c2c138b008](https://aspnetwebstack.codeplex.com/SourceControl/changeset/28c2c138b00857fbe5604acd51b6b78de0231a2c)