> Who use Microsoft build of PHP?

Surely I'm not the only person who has worked on PHP application that needed to stay running while it was being converted, piece by piece, to ASP.NET? Of course these days with dotnet Core this can all be done on Linux or the traffic routing can be trivially handled by nginx...

I'm trying to think of an answer to "We've got to do this on Windows!" but nothing realistic is coming to mind that doesn't involve legacy-ware that is over ten years old -- which is still beyond the scope of this general discussion.

Surely I would think that "PHP on Windows" going forward would be a feature delivered from WSL and not on Windows itself.

In my company some small internal web sites and simple apps run PHP on Windows; we always got the PHP zip from php.net and manually configured about 15 parameters to suit our needs, this was once per minor release, so about once a year (monthly updates did not need any config change). I am using PHP for scripting anything that does not require an exe, but more complex than a batch file, it is the default scripting solution (I connect to SQL server a lot from these scripts).

I built an internal web app a few jobs ago around 2015.

Windows server vm, IIS, PHP 7, and sql server. This replaced an asp app.

My only major issues were SQL driver or coding. I did struggling with session timeouts for a while.

I really wish I had known about nginx back then. Even if it were just to show a "down for maintenance" screen while doing a release.

Edit: I upgraded to php 7 in early 2016 before the app officially launched

SQL driver works just fine, and "down for maintenance" takes seconds to put in IIS, no PHP needed. Not perfect, but working.

I had trouble years ago when the php 7 version first came out. It was fine after a few months.

Maybe XAMPP bundles that Microsoft build of PHP.

There's IIS.

I would guess most Windows PHP users would just install WAMP (https://www.wampserver.com/en/).

XAMPP, WAMP, Appserv.