From the inital post:

I am wondering why there isn't any effort in the PHP community to get PHP into the DLR. If nothing, DLR is yet another platform, and for a php programmer it gives one more playground to showcase his skillset. Anyway, my question is whether there would be any community effort to get MS adopt PHP into CLR too. I am sure there is a genuine customer requirement, and enterprises have made quite a bit of investment in PHP and they would all love to be able to take it to the .NET platform.

Responses so far include the pointing out of problems, possibilities like a Zend collaboration and lots of talk on what such a project would entail.

He goes through five different steps in a QA process that can help you find the issues with your application long before any user gets their hands on it:

• using testing tools like PHPUnit or phpt (including code coverage
• moving on to Selenium or BadBoy (or similar testing tools) to check the runtime flow
• making ample documentation with things like phpDocumentor or Doxygen
• Providing debugging tools for frameworks to make locating errors easier than digging through code and comments
• use code analyzers to check for attacks/vulnerabilities like cross-site scripting or SQL injections

So what am I missing? Any tool I should have mentioned, team management approach? I am sure I have since I just wrote this blog post very quickly and I do not have a check list yet. Speaking of checklist, that sounds like a good thing to have when doing QA.

VC8 (Visual Studio 2005) was causing trouble with loading the new C runtime. You can read about the details of the problems encountered in this thread. So I had to make yet another build, this time using good old VC6.

The post has links to all of these new builds:

• PHP 5.2.1RC2 Win32
• PHP 5.2.1RC2 Win32 installer
• PECL 5.2.1RC2 Win32
• PHP 5.2.1 Debug Pack Win32

• PHP 5.2.1RC2 NTS Win32
• PECL 5.2.1RC2 NTS Win32
• PHP 5.2.1 Debug Pack NTS Win32