This release is targeted at module developers.
- The core module API is mostly baked
- Data migrations for updating database schema on module activation and upgrade between versions of modules
- Basic command-line scaffolding of modules and data migrations
- Dynamic compilation of module source, for notepad-style development
- Defining custom content types, parts, and fields
- Define new content types (admin panel or code)
- Add fields to content types (admin panel or code)
- Associate content parts to types (admin panel or code)
- Add fields or parts to existing content types (admin panel or code)
- Packaging and installing modules (as zip files) – can include source, binaries, or both
- Sharing modules via an ATOM feed (to be exposed on OrchardProject.net), and installing from the feed using a new “Gallery” module
- Enabling, disabling, and upgrading module features and their dependencies (admin panel or command-line)
- Localization support for both the Orchard application and database-driven content items
- Azure support
- Multi-tenancy support
- Interactive command-line support for many administrative tasks
- Some basic reporting/logging functionality
- Everything from previous Mix release: pages, blogs, comments, tags, users/roles, media, menu navigation, and basic theme support
Alternative setup instructions:
You can also set up this release by manually downloading and extracting the Orchard.Web.0.5.144.zip file to your local machine. The zip contents are pre-built and ready-to-run. Simply extract the contents of the Orchard folder from the zip file 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).
- You can also download the full source code for this release (Orchard.Source.0.5.144.zip)
Who should install Orchard using these files?
Those zip files are not
necessarily 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. sync to default.