Note:This article pertains to the CodePlex SDK initially released late 2009. The Windows Azure team has since then released a newer version of the Azure SDK for PHP on Github. Please refer to the Windows Azure PHP Developer Center for documentation on this more recent version of the SDK.
Please stay tuned and come back here regularly as we are working on refreshing the tutorials to deliver up to date and useful content for our PHP developers.
;
A significant amount of code is used in the articles on this site. For your convenience all of the sample code has been placed in a repository on GitHub. Most of the articles on this website will reference a specific folder in the repository which you can use to follow along with the article.
Where to find the samples
The Microsoft Interoperability team maintains a Github repository at https://github.com/Interop-Bridges. All of the samples on this website can be found in the Windows-Azure-Sample-Kit-4-PHP.
Downloading the samples
There are 2 ways in which you may obtain the sample code:
- Through usage of a Git client
- Download an archive containing all the samples
Using Git is the preferred method as it will allow you to keep your local copy of the samples up to date with contributions to the sample kit. If you do not have a Git client you can click on theDownloadbutton located above and to the right of the file names to download an archive in the .zip or .tar.gz format.
Installing a Git client
If you do not already have a Git client but would like to use the Git repository rather than downloading an archive you will need to install a Git client. A large list of Git clients can be found at:
https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools
Accessing the sample kit files from a Git client
After you have installed a Git client you will need to use the URL listed on the Github page in order to retrieve the samples.
You may currently retrieve all the samples with this URL
git://github.com/Interop-Bridges/Windows-Azure-Sample-Kit-4-PHP.git
Using the samples in articles
At the beginning of each article the sample that goes along with the article will be clearly specified via the name of the folder containing the sample. Generally articles will work out ofC:\tempin order to provide the reader with the most seamless experience between running the sample code and the article content. It is not mandatory, however it is recommended that you also useC:\tempwhile working through an article as it will make debugging easier by allowing you to find the exact difference between your configuration and the article author's configuration.
;
