Recent Posts and Articles
Orchard 1.4 was released the other day and has some very important features as well as a lot of bug fixes and performance enhancements. It also comes with some breaking changes that will make upgrading to Orchard 1.4 a bit more effort. Since the Orchard 1.4 release notes just don't capture the coolness of this release, I thought I would play Orchard Developer Evangelist for a day and provide much more detail and context around the new features in Orchard 1.4 and why now is a great time to learn more about this ASP.NET MVC Content Management System ( CMS ).
The main new features in Orchard 1.4 include Autoroute and Alias, Projector Module, and new Fields.
The Rules module in Orchard enable you to set-up “if this then that” types of rules. The system is fully extensible in terms of what “this” and “that” are of course, but Orchard comes with everything you need out of the box to set-up comment notifications. Let’s create this rule...
Finally! Today we officially announced the new Orchard release - version 1.4. It's a big step forward from the previous, 1.3.10 version, both in terms of performance and features.
Unfortunately, it comes with a price... There are some breaking changes which might cause some modules to stop working. Especially those modules that utilize the routing features (ie. deal with all the items accessible by URLs). It also affects the Advanced Menu module, so the current 1.3 version won't work with Orchard 1.4 out-of-the-box. I'll be submitting the compatible version to the Gallery tomorrow.
You can find detailed information on the release notes page.
One of the new features in Orchard 1.4 is Autoroute, which like most features, arrives in the form of an Orchard Module. Autoroute is a new Content Part that attaches to Content Types and replaces the Route Part to offer much more flexibility in routing patterns for routable content types. Autoroute provides the ability to create and select custom route patterns, override patterns on a case by case basis, and the ability to regenerate the route when new versions of the content item are saved. In addition to specifying static values in the routes, Autoroute also leverages tokens in Orchard that allow you to create routes based on dynamic information such as creation date, user, and other information that may vary from content item to content item.
Drivers in Orchard are responsible for taking content parts and using them to generate shapes for the rendering engine to transform into HTML. A little known fact is that there can be more than one driver for any given part. You might be wondering what this can be used for: one shape per part seems like a reasonable assumption.
I’ll show one case where this ability to add a driver to the one that already exists came in really handy.
Join us for an Orchard CMS developer’s meetup, which will be held online on Tuesday, March 6, 2012.
Date: Tuesday, March 6, 2012 Time: 8 AM Pacific, 4 PM UTC (other timezones) Location: http://www.livestream.com/microsoftdevelopers Register here (free): http://orchard-mar-2012.eventbrite.com/
Bertrand Le Roy will present on what’s new in Orchard version 1.4. Matt Harrington will demonstrate how to run Orchard on Azure using a 3 month free trial. There will be time for questions from the chatroom. No prior experience with Orchard is necessary, but consider downloading WebMatrix beforehand to become familiar with it.
Orchard is a free, open source, community-focused project aimed at delivering applications and reusable components on the ASP.NET platform. The Orchard project as a very active and vibrant community that is actively developing and also using it for personal and commercial offerings.
Iron Foundry is an open source project that extends .NET to Cloud Foundry (The Open Platform as a Service). available for the Windows Server Environments with the ability to run the full spectrum of .NET Web Applications, SQL Server, and more. Iron Foundry places the Microsoft tool stack on an even footing with the Linux-based stacks. This platform is all open source and can be deployed anywhere. Today we are going to use the free trial environment provided by the Iron Foundry project.
With Iron Foundry and Cloud Foundry Orchard can scale within minutes to handle load on the system. This also gives an environment for rapid testing and staging of your application.
In four easy steps you can deploy and start configuring your Orchard CMS instance on Iron Foundry.
Orchard CMS works really well with TortoiseHg as detailed in the documentation, but if you use Team Foundation Server then there are a few hoops you need to jump through to get it to play nicely. You may be tempted to just right click on the solution and click "Add Solution to Source Control", but this will cause you a few issues - especially if you work in a team and have predefined modules as part of a recipe. If you follow this step by step you should be fine and other team members are able to get all the third party DLL's too.