This is a technical preview release of Orchard. Our intent with this release is to demonstrate representative experiences for our audiences (end-users, designer/scripters, and developers), and to raise interest among developers for writing Orchard modules on the Orchard CMS platform. This is an early release intended to solicit feedback only - it is not intended for production use; many features remain to be developed and/or stabilized, and the development APIs will certainly evolve and change going forward. That said, there is alot you can do with Orchard today, so please check it out and let us know what you think!
The full release notes are available for download above, and describes some common "gotchas" and known issues.
Setup instructions:
Alternative setup instructions:You can also set up this release by manually downloading and extracting the appropriate zip file (either 32-bit or 64-bit) to your local machine. The zip contents are pre-built and ready-to-run. Simply extract the zip contents to an IIS virtual directory (or site root) and then point your browser to the site. You can also just extract to a local folder and open the included project file in Visual Studio to run it under the local ASP.NET Development Server (Cassini).
- Download OrchardIIS.zip for a 32-bit machine
- Download OrchardIIS_64.zip for a 64-bit machine
You can also download matching source code for this release here:
- Download OrchardSource.zip (contains source for built-in Orchard modules and core).
Who should install Orchard using these files?
Those zip files are
not the latest work from the team. They only represent the most stable release of the application so far.
If you just want to use Orchard and don't care about the source code, OrchardIIS.zip is what you want to use, preferably through the
WebPI instructions.
If you want to take a look at the source code, or only want to create new modules but do not want to write patches or contribute to the core, OrchardSource.zip is fine. It is the source code for OrchardIIS.zip, so just as OrchardIIS.zip, it won't be the latest version of the code, only the latest stable release.
Both zip files are releases and are going to be provided on each major milestone.
If you want something more up to date than that, or if you want to write patches or modify the core modules, you can enlist in our source control by following the instructions here:
enlist or you can just download the latest version by going to the
Source Code tab and clicking "Download" on the top-right corner under "Latest Version".
There are always at least two active branches: the dev branch, which is likely to be unstable but very up to date, and the default branch, which is the result of the latest three-week iteration and should be fairly stable at all times, but not as stable as OrchardIIS.zip. Unless you have a good reason (such as wanting to follow the progress of the core team closely), we recommend you always sync to the latest in the default branch.