I tried posting this to php-win a while back with no result so forgive the duplication.
Under IIS6 (Windows 2003) you 'register' the file extensions in the web extensions manager which /appears/ to preclude running different binaries for PHP with the same file extension. Example 1: Site php extension php version A .php php.exe 4.1.x B .php php.exe 4.2.x C .php php.exe 4.3.x Example 1 is what I currently do under W2K IIS5 to allow individual clients to have their own 'copy' of php complete with php.ini running in safe mode locked to their webroot. Each site is independant of the others and can be upgraded individually as/when required. Example 2: Site php extension php version A .phpa php.exe 4.1.x B .phpb php.exe 4.2.x C .phpc php.exe 4.3.x Example 2 is the only way I can get this working with W3K IIS6 and is a really dumb way to get it going (not in production and not going into production!) If anyone knows how to setup IIS6 to allow the same .php extension to be used with dedicated copies of php.exe + ini files I would really appreciate the assistance. Maybe some clue I am missing about the behavior of the web extensions manager or a method of defeating it? I do run apache on other boxes so that is not the solution here as the sites do some IIS5/IIS6 stuff specific stuff. Regards Petar
