arrow-left arrow-right brightness-2 chevron-left chevron-right circle-half-full dots-horizontal facebook-box facebook loader magnify menu-down RSS star Twitter twitter GitHub white-balance-sunny window-close
Magellan Major Changes
1 min read

Magellan Major Changes

This is an old post and doesn't necessarily reflect my current thinking on a topic, and some links or images may not work. The text is preserved here for posterity.

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.

Paul Stovell's Blog

Hello, I'm Paul Stovell

I'm a Brisbane-based software developer, and founder of Octopus Deploy, a DevOps automation software company. This is my personal blog where I write about my journey with Octopus and software development.

I write new blog posts about once a month. Subscribe and I'll send you an email when I publish something new.