Magellan Major Changes

The latest CodePlex Magellan build includes a couple of changes that are worth noting:

  1. The new Forms controls
  2. No need to import the Magellan namespaces
  3. Various bug fixes

That second item is worth focusing on. In previous builds, to use any of the Magellan classes in XAML, you had to write:

<Page ...

I wrote before about an idea to move them to the default XAML namespace, and while a few potential issues were suggested, I thought the benefits outweighed the issues. This means you can now do this:

<Page ...
    <Layout ...

With the new Forms feature combined with the Shared Layouts feature, the markup gets really minimal:

<Page ...>
        <Zone ZonePlaceHolderName="Content">
                <Field For="{Binding FirstName}" />
                <Field For="{Binding LastName}" />
                <Field For="{Binding EmailAddress}" />
        <Zone ZonePlaceHolderName="Actions">
            <Button Content="Submit" Command="{Binding Submit}" />

If you do encounter any issues because of this change, please let me know.

A picture of me

Welcome, my name is Paul Stovell. I live in Brisbane and work on Octopus Deploy, an automated deployment tool for .NET applications.

Prior to founding Octopus Deploy, I worked for an investment bank in London building WPF applications, and before that I worked for Readify, an Australian .NET consulting firm. I also worked on a number of open source projects and was an active user group presenter. I was a Microsoft MVP for WPF from 2006 to 2013.

Carl Scarlett
Carl Scarlett
22 Feb 2010

It sure -looks- a lot cleaner; particularly with so many Magellan elements in the XAML.

Let's hope there's no nasty side effects.