We recently upgraded the MiniProfiler version 2.0.1 from version v1.7, and since then we have not been able to use it on our MVC3 website, because when she tries to get her resources, she gets 404 instead.
Example of a resource call: /mini-profiler-resources/includes.js?v=tNlJPuyuHLy/d5LQjyDuRbWKa0weCpmO3xkO6MH4TtA =
When searching around, most people think that setting runAllManagedModulesForAllRequests should be set to true . For a giggle, I went ahead and found that it was true, and yes, it really worked. But this is not an acceptable answer.
How can I keep runAllManagedModulesForAllRequests=false and still use MiniProfiler v2?
web-config asp.net-mvc-3 mvc-mini-profiler
Adam Spicer Apr 24 '12 at 19:22 2012-04-24 19:22
source share