File extensions

I have a client running IIS to serve his .NET application. He wants to run his corporate web site on the same server but wants the web site developed in PHP. He is concerned for whatever reason about the appearance of mixing URLs that end in .php with ones ending in .aspx.

I think this is possible on Apache, but will IIS allow me to have all of my file have a common extension, say ".html" and parse some as PHP and others as .NET based on the directory they live in?

The simple answer... set up a test system and try it... it's the only way to learn... you may even be able to just tell IIS to process .html tags as PHP AND ASP.NET... it should be able to figure out which engine to use based on the tags in the document. Not positive if this would work, but you could try it.

For the sake of sanity I'd try to reject that idea myself. You'll end up with an un-maintainable setup imho.