Recently we upgraded to MiniProfiler version 2.0.1 from v1.7, and since then we have not been able to use it in our MVC3 website because when it tries to get its resources, it instead gets a 404.
An example resource call is: /mini-profiler-resources/includes.js?v=tNlJPuyuHLy/d5LQjyDuRbWKa0weCpmO3xkO6MH4TtA=
In searching around, most people are suggesting that simply setting runAllManagedModulesForAllRequests
should be set to true
. For giggles, I went ahead and set it to true, and yes it did work. But that is not an acceptable answer.
How can I keep runAllManagedModulesForAllRequests=false
and still use MiniProfiler v2?
I had a similar issue and what I did to fix it was change the application pool to 'integrated' and then I added this new line below to my web.config and it then worked.
Here is what the complete web.config looks like now for mini-profiler.
I had the same issue - the resources being requested use "static" file extensions (such as
.js
) and therefore IIS wants to handle them using its static file handler.Luckily all of the MiniProfiler resources are requested with the path
mini-profiler-resources
, so you can add the following to yourweb.config
:The entry above instructs IIS that any request for the
mini-profiler-resources
path to be routed through ASP.NET.As David Duffet says in the comments in the accepted answer, you might also need to add the following entry to your web config. This worked for me: