Archives / 2009 / November
  • Final RTW version of WINCACHE 1.0 released

    I am extremely proud to announce that we have released the final RTW version of WINCACHE 1.0. Please look at the forum announcement of the same at which contains all the details about the release. I would strongly recommend everyone running Beta/RC version of WINCACHE 1.0 to upgrade to the final RTW release. If you installed WINCACHE 1.0 RC from Microsoft Web Platform Installer, you can use the same to upgrade to RTW. Upgrade from RC to RTW is supported through WPI. If you have installed WINCACHE 1.0 RC/Beta manually, you will need to install the new binaries manually. Here are the steps:

  • Troubleshooting PHP Installation on Windows

    My PHP installation is not working? I am not able to run my PHP scripts? A simple PHPINFO page is not loading in my browser? These are typical questions I hear from users in the forum. I would still say the best way to install PHP is to use WPI as described by me here and here. I am telling this because WPI installation involves non-manual steps of installing PHP 5.2.11 or PHP5.3.

  • Enabling WINCACHE on per site basis

    With WINCACHE 1.0 RC one can configure parts of WINCACHE solution on a per site basis. As you know WINCACHE has two kinds of cache namely output code cache and file cache. With RC release, you have the ability to turn output code cache on a per site basis. We have got a new WINCACHE directive named WINCACHE.OCENABLEDFILTER which can be used to enable/disable output code cache on a per site basis. This INI directive can take a string which is list of comma separated  numbers. Each number in the string represents a valid site id which is a unique identity IIS gives to each Web Site when the site gets created. All the site id included as part of this string will actually toggle the value of WINCACHE.ocenabled while running WINCACHE functionality. Example, if you have below in your PHP INI file:

  • Running PHP displays the code itself

    At times we get posting on the forum where user complain that when they are running a PHP file, the output is the file itself. This means that the script was not recognized as a PHP script and rather it was treated as plain text by the browser. There are two reasons why you can run into this situation to my knowledge.