<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 25 May 2013 20:55:23 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Josh Holmes' Blog: Resolving PHP Version Conflicts while Developing for Azure]]></title>
      <guid>http://www.phpdeveloper.org/news/14597</guid>
      <link>http://www.phpdeveloper.org/news/14597</link>
      <description><![CDATA[<p>
<i>Josh Holmes</i> has a new post to his blog today with a <a href="http://www.joshholmes.com/blog/2010/06/03/resolving-php-version-conflicts-while-developing-for-azure">tip on resolving version conflicts</a> while developing PHP applications on an Azure installation.
</p>
<blockquote>
A little while back I wrote a blog post titled <a href="http://www.joshholmes.com/blog/2010/04/13/easy-setup-for-php-on-azure-development/">Easy Setup for PHP On Azure Development</a>. One of the things that I touched on is the PHP version conflicts. I had a much better idea which I've tried and have working so I thought I'd blog that here. What I had you doing in the <A href="http://www.joshholmes.com/blog/2010/04/13/easy-setup-for-php-on-azure-development/">Easy Setup for PHP On Azure Development</a> is renaming the directory for PHP from something like C:PHP or C:Program FilesPHP to something else so that it wasn't in the %PATH% so there wasn't a conflict. 
</blockquote>
<p>
You don't have to do it this way, though - there's another option that involves editing the web.config file on the Azure side to tell wit there the correct PHP install lives. He also explains how you can test your WebRole code locally instead of having to upload it each time by setting up a virtual directory in your project.
</p>]]></description>
      <pubDate>Thu, 03 Jun 2010 09:15:22 -0500</pubDate>
    </item>
  </channel>
</rss>
