/mini-profiler-includes.tmpl?v=1.6.0.0 returns 404

[GoogleCodeExporter]

What steps will reproduce the problem?
Running a localIIS solution using .NET 4.0 with WebForms.

What is the expected output? What do you see instead?
No profile information appears on the page.  The RenderIncludes() call is 
working fine.  Presumably, the 404 on this .tmpl file is the cause.

What version of the product are you using? On what operating system?
Windows 7, IIS7.5.  Solution file is a local IIS project.

Please provide any additional information below.
I am using jQuery 1.4.2 on this project; I do not know if that makes a 
difference.  It's a webforms project which (re)builds successfully with no 
errors and no warnings.

Original issue reported on code.google.com by andyp...@gmail.com on 22 Jul 2011 at 4:42

[GoogleCodeExporter]

Have you set runAllManagedModulesForAllRequests to true?

Take from the FAQ:
"I needed to add the following line to the web.config section for url routing 
in IIS7:

<system.webServer> 
   <modules runAllManagedModulesForAllRequests="true"/> 
</system.webServer> 
"
http://code.google.com/p/mvc-mini-profiler/wiki/FrequentlyAskedQuestions

Original comment by MHB...@gmail.com on 22 Jul 2011 at 5:02

[GoogleCodeExporter]

That did it.  Thank you - go ahead and close.

I did skim by that comment but I guess I didn't "take it seriously" because it 
was just a comment on the FAQ.  Thanks again. :)

Original comment by andyp...@gmail.com on 22 Jul 2011 at 5:05

[GoogleCodeExporter]

My recently-added issue 60 covers the same ground - my feeling is that all 
sorts of unpleasantness follows from trying to serve files with extensions that 
are either unusual (.tmpl) or static-by-convention (.js, .css) through an 
ASP.NET handler.  It doesn't feel right to me that a profiler should need such 
radical pipeline changes to make it work - Heisenberg will be waiting at the 
door with his studded baseball bat. 

Original comment by prefect_...@indcomp.co.uk on 22 Jul 2011 at 5:39

[GoogleCodeExporter]

Original comment by nrcraver on 25 Jul 2011 at 10:28

• Changed state: Invalid

[GoogleCodeExporter]

I don't think that setting runAllManagedModulesForAllRequests=true is a great 
solution because it forces all static files to be run through the pipeline so I 
usually turn this off. Could we render these includes extensionless rather or 
are there any instructions for leaving runAllManagedModulesForAllRequests=false 
and only forcing the mini profiler includes through the asp.net pipeline?

Original comment by g...@bitdiff.com on 20 Aug 2011 at 9:18

[GoogleCodeExporter]

I also think, that setting runAllManagedModulesForAllRequests=true could be 
avoided simply by changing path of requested resource, in that case and even if 
this can be solved using web transforms, I would prefer not to switch it 
between debug and retail builds.

Original comment by Giedrius...@gmail.com on 16 Dec 2011 at 11:12