Performance loss due to add asp.net_isapi to request pipeline?

Question

is there a notable performance loss if all files are handled with the aspnet_isapi in request pipeline using IIS6? IIS7 has the new integrated pipeline so that seems not to be a problem.

I ask this, because I want apply an .net url replacer on .exe files for example. To do so, I have to add them to the asp.net isapi. I fear this could slow down the IIS/Website.

Thank you!

Answer 1

These two posts should help you decide:

IIS 6.0 wildcard mapping benchmarks? (Stack Overflow)
ASP.net MVC performance with extensionless url on IIS 6 (Stack Overflow)

This answer explains how the ASP.NET pipeline handles static files:

ASP.net MVC performance with extensionless url on IIS 6 - Answer (Stack Overflow)