Govorunov

Hello.

You are right, that check would not be easy. With Ape you would check presence of the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Helicon\Ape
But this indicates only Ape is installed but say nothing about whether it is working for this particular web site or not. To tell more it would require analysis of IIS metabase, which may be of different versions, have various API to access (rely on IIS version) and different bitness. And the worst of all the IIS application pool user (the one who run WordPress) depending on system settings may not simply have permissions to read either registry or metabase.

So according to our experience simple manual switch would be the best choice. Or simply remove the check. Presence of .htaccess file will not harm IIS if no .htaccess emulation modules are installed.

Hello!

I represent ISAPI_Rewrite support service.
May I suggest you to take a look at another our product – Helicon Ape which implements much more features than ISAPI_Rewrite. Please see the compatibility chart – http://www.helicontech.com/ape/doc/compatibility.htm

Helicon Ape is recommended if you are using IIS 7 or higher. For IIS 6 and prior versions ISAPI_Rewrite is still better solution. But for never IIS versions Ape is the best choice as it supports nearly all built-in Apache modules and directives. There are better chances that BPS module will work with Ape without modifications.