Friday, 28 Oct 2011 will be my last day in Redmond, and unfortunately Microsoft and the patterns & practices team.

My decision to leave Redmond was driven solely by the poor real estate market in this area. I really want to build a new home, but know too many people here who are upside down (big $$$$) in their mortgages or who short sold their home. This was not a risk I wanted to take. Some say the market is near the bottom and now is a good time to buy here; maybe, but the cost to build a new home is higher than I want to take on and a long or hard commute is not an option for me. I prefer a 10-15 minute traffic-free drive (doesn’t everyone?)

This was a very difficult decision choosing between a life goal of building a new home, a short commute, and trying to stay with Microsoft in Redmond.

On 29 Oct 2011, I’ll be moving to Boise, Idaho and after a short break will begin a new career with Gayle Manufacturing Company. I’m looking forward to becoming part of the GMC family and transitioning back to an architect-developer role. Over the winter I’ll work with a home builder in Boise and hope to break ground in March or April of 2012. The other night I was studying home automation; it felt good to look forward to building a home, something I have not felt in long time.

Leaving Microsoft

Leaving Redmond is easy (for the above reason), leaving Microsoft is difficult. I’m grateful for the opportunities I’ve been given over the last 3 years. Except for the Marine Corps, Microsoft is the best company I’ve ever worked for. I would not hesitate to recommend the opportunities at Microsoft to anyone, this super place to work.

I will very much miss the dedicated and very smart people at Microsoft.

Leaving Redmond also means moving away from friends in the area; I will miss you as well.

Staying Connected

My blog will continue with WPF, Prism, and enterprise development topics, and will venture into WinRT land as well. I’m looking forward to joining the user groups in Boise.

I will also continue to stay close with Microsoft teams and groups by participating on advisory boards and other customer channels.

Close

Microsoft and the people of Microsoft, thank you very much for the last three years.

Have a great day,

Just a grain of sand on the worlds beaches.

One tool I’ll be using is the new Windows Phone Marketplace Test Kit.

From the above MSDN page:

The Windows Phone Marketplace Test Kit provides a suite of automated, monitored, and manual tests to help prepare your applications to be accepted in the Marketplace the first time you submit them. The test kit enables you to identify and fix issues prior to Marketplace submission, which saves time in the submission process. You can use the test kit to evaluate applications that target Windows Phone OS 7.1 or later.

To open the Marketplace Test Kit, select your Windows Phone 7.1 project in the Solution Explorer. Then from the Project menu select, Open Marketplace Test Kit.

The below tool will open allowing you to run a set of prepackaged tests and provides a UI to import the required images for your application.

Thanks go out to the Windows Phone team for shipping this.

Have a great day,

Just a grain of sand on the worlds beaches.

Project Silk

Client-Side Web Development for Modern Browsers

Project Silk provides guidance for building maintainable cross-browser web applications that are characterized by an intentional design, rich interactivity, and a responsive user interface (UI). The result is an immersive and engaging user experience (UX). Such applications take advantage of the latest web standards, including HTML5, CSS3, and ECMAScript version 5, and modern web technologies such as jQuery and ASP.NET MVC 3.

The concepts explained in this book are demonstrated via a real-world customer-facing web application called the Mileage Stats Reference Implementation (Mileage Stats). Mileage Stats allows users to track and compare their vehicles’ fuel efficiency, usage, and operating costs, and to schedule vehicle maintenance reminders. The image below shows the Mileage Stats client-side objects and their implementation mapped to libraries or frameworks.

Building a rich web application that reduces the number of full-page loads, includes animations, and is responsible for updating the UI dynamically requires a thoughtful approach to managing structure, modularity, communication, navigation, and data. The book details how the Project Silk team designed Mileage Stats and solved a number of challenges.

Links

• Project Silk download
• Project Silk Home Page on MSDN
• Project Silk Community on CodePlex
• Project Silk Road Map
• Mileage Stats Video

Audience

• This guidance is intended for web developers and assumes you have some hands-on experience with ASP.NET MVC, CSS, HTML, JavaScript, and jQuery.

In this Release

• Project Silk Mileage Stats Reference Implementation full source code
• Widget QuickStart documentation and source code
• Unit Test Hands on Labs (3)
• Project Silk: Client-Side Web Development for Modern Browsers online documentation
• Mileage Stats Video

About patterns & practices

The Microsoft patterns & practices team provides a wide range of guidance to help customers save time and reduce risk on their software development projects by incorporating proven patterns and practices.  This applied engineering guidance includes both production quality source code and in-depth documentation.

The guidance is designed to help software development teams:

• Make critical design and technology selection decisions by highlighting the appropriate solution architectures, technologies, and Microsoft products for common scenarios
• Understand the most important concepts needed for success by explaining the relevant patterns and prescribing the important practices
• Get started with a proven code base by providing thoroughly tested software and source code that embodies the recommendations

For more information: http://msdn.microsoft.com/practices

Have a great day,

Just a grain of sand on the worlds beaches.

To try and add anything to what has been clearly communicated would be foolish on my part.  Instead let me tell you about my “Lazarus” experience this week.

I’ve been eyeing the Asus EP121 for several weeks now. I got to play with one at the Bellevue Microsoft Store. This is one sweet unit.

Well, I have a dusty, HP tm2 TouchSmart Laptop/Tablet. It has a Core i3 1.2ghz, 4GB memory, integrated graphics card, slow 5400rpm drive. My thinking was, if I can pull a Lazarus on this computer for 6-12 months, I’ll save myself the $1,000 now and wait for the next generation hardware and with fast CPU, SSD, HD screen, etc.

I did use the HP tm2 for Window Phone 7 development and OneNote note taking.  It was kind of slow, especially compared to other modern hardware.

The slowness was not attributed to Windows 7, but rather to lame hardware. 

PC hardware manufacturers please start making decent hardware that competes with Apple’s hardware and PLEASE stop putting crapware on my new PC. All crapware should be a line item, opt-in.

I need to move off this topic before I go into a tirade.

On the good side, one of the keynotes at BUILD showed new hardware coming soon that looks like the MacBook Air, metal, thin, etc.  At last. Please offer good components in your units, I’ll pay for them.

So I replaced the first generation 5,400rpm hard drive with a 7,200 second generation SATA. Was getting just a little excited, breathing new life into my laptop.

Lazarus!

Following simple directions on Scott Hanselman’s blog, I loaded the Win8 Preview on a USB.

When I booted the laptop I change the default boot to the USB so I could install Windows.  When Windows restarts, don’t forget to change the default boot back to your hard drive.

Installation took 12 minutes; Windows, Visual Studio, demo applications, etc.  Core i3 and a decent disk, still respectable.

The laptop boots very quickly, applications are responsive and fun to use.  I have not installed Office yet, but will soon. For now, just learning to get around Windows 8 and how to write Metro XAML apps.

Scud Missile

After I logged in, I ran Windows Update and one of the items installed was the, “Microsoft IntelliPoint 8.2 Mouse Software for Windows – 64 bit” This update on my laptop caused the touch to quick working.  So I used Add Remove programs to uninstall it, rebooted and got touch working again.

Visual Studio XAML Designer Patch

You need to install a patch published by the Expression Team to correct a mouse issue with the designer.

https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=38599

After downloading, don’t forget to “Unblock” the .zip file.  The instructions left this out.

You MUST follow the installation instructions, most important you must install the patch as an administrator.

The fun part will be trying to figure out how to open an Administrator Command Prompt. I could not figure out how to do this using the Metro interface.  So… I opened Windows Explorer in the Desktop, navigated to the \Windows\system32 folder, right-clicked on the cmd.exe file and selected, “Run as Administrator.” While you at it, go ahead and pin that Administrator Command Window to the TaskBar, problem solved.

Getting Around Windows 8

Since you probably won’t be writing code using your TouchScreen keyboard, you’ll want to get up to speed on Windows Shortcuts. The following blog post is being recommended by several on Twitter so I’ve included it here as well.

http://www.winrumors.com/windows-8-tips-and-tricks-for-mousekeyboard-users/

Before Your Frist Project

Before you dive into your first Metro project, take time and watch some of the BUILD videos. If you only watch one video, watch this one: http://channel9.msdn.com/events/BUILD/BUILD2011/BPS-1004. Jensen Harris clearly explains Metro and the thinking behind it. He is also one of the best presenters at BUILD and connects with the audience and viewers alike.

Video

The below video shows my HP tm2 after the Lazarus operation.  Short, 3 minutes gives you a good feel for how a Core i3 runs Windows 8.

http://www.vimeo.com/29222402

Close

These are good times for Windows developers.

For me, I’m finishing up my WPF/Prism BBQ Shack program and will move the cash register and online purchasing modules to Metro.  Metro is perfect for a touch screen cash register.  This will be so much fun to write.

Have a great day,

Just a grain of sand on the worlds beaches.

All the details and sign up for the Redmond GiveCamp can be read here:  http://seattlegivecamp.com/

What I like about weekend events like this is the challenge:

• Working with a team you may have never met
• Writing an application you have zero up front context on
• Delivering over the weekend an application that will be deployed and used the next week

For this event, I’ll be joining a group of of Microsoft LightSwitch team members to take up the challenge of delivering an application using LightSwitch over the weekend.

This is a great opportunity for you to meet others, exercise your skills on a team, learn from other team members and have fun at the same time.

If you find yourself in Redmond in October, we hope to see you there.

Don’t forget you need to sign up here: http://seattlegivecamp.com/

Have a great day,

Just a grain of sand on the worlds beaches.

New to Prism 4 was the Navigation API’s. The use of the Navigation API’s greatly simplifies application development because the Navigation API takes over the responsibility of object creation and siting objects in the target region.

The Prism library is designed to support applications that can target WPF and Silverlight with good code reuse. While not all developers need this capability, a lot of thought and design decisions were made to fully support this scenario.

One API that took this capability into account while being designed is the Navigation API; specifically the confirmation of a navigation request. Objects that implement IConfirmNavigationRequest have the option to veto a navigation request. In order to support the limitation that Silverlight does not allow blocking dialog boxes, the IConfirmNavigationRequest.ConfirmNavigationRequest method had to be written so that Silverlight objects could participate in vetoing a navigation request without a blocking dialog.

Without going into all the details (you can read them here), objects that implement IConfirmNavigationRequest are required to invoke the callback in the ConfirmNavigationRequest method arguments. Objects are free to implement any vetoing code they want as long as the callback is invoked.  In practice the navigation request is halted until the callback is invoked. This design enables Silverlight developers to implement a variety UI solutions for prompting the user, for example the Prism Interaction Request.

I’ve found that I’m my WPF development that I had to jump through the above hoops just to have navigation confirmation, when in fact WPF has out of the box support for modal, UI blocking dialogs. In an effort to simplify my WPF applications I’ve created a replacement for the Prism RegionNavigationService that allows for synchronous navigation confirmation.

The implementation is very straightforward and only requires that you add one class and one interface to the Prism library and recompile it.

The RegionNavigationSynchronousService is the replacement for the stock RegionNavigationService. This class uses the new synchronous (blocking) navigation confirmation interface IConfirmNavigationRequestSynchronous, listed below.

public interface IConfirmNavigationRequestSynchronous : INavigationAware
{
    /// <summary>
    /// Determines whether this instance approves being navigated away from.
    /// </summary>
    /// <param name="navigationContext">The navigation context.</param>
    Boolean ConfirmNavigationRequestSynchronous(NavigationContext navigationContext);
}

By default, Prism automatically registers the RegionNavigationService in the container as part of the bootstrapping pipeline. However, we want to use the WPF friendly synchronous confirmation service, RegionNavigationSynchronousService.

All that is required is to override the ConfigureContainer method in your bootstrapper and register RegionNavigationSynchronousService as I’ve done below.

namespace TestBench {
    using System.Windows;
    using Microsoft.Practices.Prism.Modularity;
    using Microsoft.Practices.Prism.Regions;
    using Microsoft.Practices.Prism.UnityExtensions;
    using Microsoft.Practices.Unity;
    using TestBench.Customers;

    class Bootstrapper : UnityBootstrapper {
        protected override IModuleCatalog CreateModuleCatalog() {
            var catalog = new ModuleCatalog();
            catalog.AddModule(typeof (CustomersModule));
            return catalog;
        }

        protected override DependencyObject CreateShell() {
            var shell = this.Container.Resolve<ShellView>();
            Application.Current.MainWindow = shell;
            Application.Current.MainWindow.Show();
            return shell;
        }

        protected override void ConfigureContainer() {
            base.ConfigureContainer();

            // register the new navigation service that uses synchronous navigation
            // confirmation instead of the async confirmation.
            this.Container.RegisterType(typeof(IRegionNavigationService),
                typeof(RegionNavigationSynchronousService));
        }
    }
}

Below is a very simple implementation.

PLEASE do not put MessageBox code in your view models!  This is for demo purposes only and to keep the code simple.  Please use a dialog service that abstracts the UI dialog away from the view model.

The below code is from the included download and is in the CustomerMaintenanceViewModel. The below ConfirmNavigation property allows the demo to confirm or not but is not part of the Navigation API. This method returns true or false to continue the navigation request or not.

public Boolean ConfirmNavigationRequestSynchronous(NavigationContext navigationContext) {
    if (this.ConfirmNavigation) {
        if (MessageBox.Show("Close form and navigate?", "Confirm Navigation",
            MessageBoxButton.OKCancel, MessageBoxImage.Question) == MessageBoxResult.OK) {
            return true;
        }
        return false;
    }
    return true;
}

Demo Application

Very simple Prism application that demonstrates confirming navigation requests and region lifetime. The status bar indicates the views in the ContentRegion on the right.  As you open or close views their name will be displayed; for the Customers, the customer number will be displayed.

Crack the code open, you’ll have this down in a few minutes.

Download

As always, don’t forget to “Unblock” the zip file after downloading from the Internet before you unzip it.

Synchronous Prism Navigation (177KB)

The download includes a sample Prism solution that your can run without modifying your Prism library code.  I’ve included a \Lib folder in the solution with pre-built, modified Prism library code.

I’ve also included two files in the \PrismSource folder that you can add to your Prism library. Simply copy these two files into the below folder and recompile Prism. You now have the option to use a simpler navigation confirmation API in your WPF projects. 

This only works in WPF and NOT Silverlight.  If you have the requirement to share code between WPF and Silverlight this will not work because Silverlight requires the navigation confirmation to be async.

Have a great day,

Just a grain of sand on the worlds beaches.

This presentation was on data forms for Windows Phone 7.

The MangoForms demo application consists of a series of forms that each focus on a single aspect of a form such as, scrollability, type mismatch exceptions, validation, ICommands, IDataErrorInfo, sample data, design-time tooling, MVVM, etc.

I’ll try and publish a few videos that capture the teaching presented at the meeting.

Download

You can download the code and deck from my Sky Drive here.

Note:  The deck is in the folder SiliconValleyCodeCamp and is for the Application Life Cycle training.  There is no deck for this presentation, just code.

Have a great day,

Just a grain of sand on the worlds beaches.

Video

If you have not seen the Project Silk video check it out here.

Chapters

The following chapters are ready for review:

• Design and Layout (new)
• Modularity (early draft)
• Communication (early draft)
• Navigation (early draft)
• Server-Side Implementation (updated)
• Introduction (updated)
• Architecture
• Client Data Management and Caching
• jQuery UI Widgets
• Application Notifications
• Security
• Unit Testing Web Applications
• Widget QuickStart
• How to: Check UIElement Properties with Coded UI Test
• How to: Create Automation Negative case with Coded UI Test
• How to: Create Web Client UI Test using Coded UI Test

The following chapters are currently being written or will be started soon:

• HTML Templates

Close

We welcome and appreciate your feedback on the application and book content.

Have a great day,

Just a grain of sand on the worlds beaches.

Contents

C# early version of Ocean.

• Data Binding
• M-V-VM
• Commands in M-V-VM
• Dialogs in M-V-VM
• Data Validation
• M-V-VM Tips & Tricks
• Unit Testing & Moq
• Introduction to Prism
• Unity and Dependency Injection
• Shell and Bootstrapping
• Modules
• Regions
• Events
• Navigation

Download

The download includes PowerPoint decks for most of the sessions and source for all sessions.  Also included is an  Extras folder with goodies.

Please READ THE READ ME.

You can download the code and decks from my Sky Drive here.

Have a great day,

Just a grain of sand on the worlds beaches.

The next drop will be on or about 6 July 2011.

Chapters

We are providing the guidance chapters in Word document, .pdf, and .chm format. Providing the chapters in Word format makes it easier for the community to provide feedback by using the Word Track Changes feature. If you provide feedback on a chapter, you can upload your feedback to: Project Silk Issue Tracker.

The following chapters are ready for review:

• Introduction (new)
• Modularity (new – early draft)
• Architecture (updated)
• Client Data Management and Caching (updated)
• Server-Side Implementation (updated)
• jQuery UI Widgets
• Application Notifications
• Security
• Unit Testing Web Applications
• Widget QuickStart
• How to: Check UIElement Properties with Coded UI Test
• How to: Create Automation Negative case with Coded UI Test
• How to: Create Web Client UI Test using Coded UI Test

The following chapters are currently being written or will be started soon:

• Navigation
• Communication
• HTML Templates

Close

We welcome and appreciate your feedback on the application and book content.

Have a great day,

Just a grain of sand on the worlds beaches.

Developers leveraging Prism will be happy to find enhanced support for exploring objects from the Prism and Unity frameworks.

Several fixes will make our large user base in Germany quite happy, including the ability to use a list separator, other than a comma, in exported CSV files.

Mole v1.3 Enhancements

• Fixed bug where Mole would not close properly when computer has a touch-enabled screen (worked around a WPF issue).
• Enabled viewing and drilling into more collection types. Mole 2010 now supports drilling into any IEnumerable object.
• Both the Key and Value properties of a DictionaryEntry object are now shown in the MoloScope’s Value column.
• Collection items for NameValueCollection now show the keys and values in the MoloScope.
• Improved support for working with Prism and Unity applications (support for drilling into the RegionManager and Unity container collections).
• Enabled drilling into objects with only non-public fields.
• Exporting collection data to CSV now uses the list separator defined by your system locale, instead of always using a comma.
• The Options dialog allows you to specify a list separator to use in the CSV files, if necessary.
• MoloScope column widths are no longer set to incorrect large values when running on a system with the German locale.
• Snapshot rendering of Windows Forms controls has been modified to properly handle some edge cases.

Current Registered Users

Current registered users of Mole can download this updated version and install the new version over old one.

http://www.molosoft.com/wp-content/uploads/2011/06/Mole2010.zip

Demo Version Available

If you are interested in trying out Mole 2010 before buying it, visit the Molosoft Demo page to get the latest release of the trial version. The trial version includes the new features and fixes listed on this page.

Learn About Mole

To learn about the Visual Studio 2010 Debugger Visualizer Mole and how this debugging tool can help you when debugging applications in Visual Studio 2010, please visit Molosoft.com.

Close

We welcome and appreciate your feedback on Mole!

Have a great day,

Just a grain of sand on the worlds beaches.

Code Updates

• Significantly reduced the coupling to the mstats global object. Widgets are no longer stored as members on mstats. Instead, widgets are either created in the bootstrapping mileagestats.js or in another managing widget.
• Added a utility function for mixing in helper methods that simplify the syntax for invoking public method on widgets (when used inside of another widget).
• Significantly reduced the number of hard-coded URLs. URLs are generally pulled from data- attributes.
• Corrected an issue with the way that the chart vehicle selection UI was constructed. Changes in jQuery 1.6.1 caused this to surface.
• Now correctly redirects to the Login page when a session timeouts and JSON request is made while using the Single Page Interface.

Chapters

We are providing the guidance chapters in Word document, .pdf, and .chm format. Providing the chapters in Word format makes it easier for the community to provide feedback by using the Word Track Changes feature. If you provide feedback on a chapter, you can upload your feedback to: Project Silk Issue Tracker.

The following chapters are ready for review:

• Client Data Management and Caching (new)
• Architecture (updated)
• jQuery UI Widgets (updated)
• Application Notifications (updated)
• Server-Side Implementation
• Security
• Unit Testing Web Applications
• Widget QuickStart (updated)
• How to: Check UIElement Properties with Coded UI Test
• How to: Create Automation Negative case with Coded UI Test
• How to: Create Web Client UI Test using Coded UI Test

The following chapters are currently being written or will be started soon:

• Introduction (in progress)
• Modularity (in progress)
• Navigation
• Communication

Video

We have also made a new video for Project Silk that includes a short tour through the countryside with stops for gas and parts. During parts of the video, the Mileage Stats UI displays as a HUD (heads up display). After this short but entertaining introduction a new tutorial video beings.  This video is currently in production and will be released on Channel9 soon.

Close

We welcome and appreciate your feedback on the application and book content.

Have a great day,

Just a grain of sand on the worlds beaches.

On the server-side we refactored business services layer into task handlers used by the controllers.

On the client-side we refactored and cleaned up the widget code as follows: use of option, _setOption, and _setOptions to be consistent,  namespaced event bindings and unbound them in the destroy method, removed endpoint Url’s from the widgets options these are now extracted from data dash attributes, and cleaned up conditional statements.

On the client-side data manager and widgets, we consolidated saveData and getData into a single call (sendRequest) that takes an option indicating whether or not to cache.

We are now providing the guidance chapters in Word document, .pdf, and .chm format. Providing the chapters in Word format makes it easier for the community to provide feedback by using the Word Track Changes feature.

The following chapters are ready for community review:

• Application Notifications (new)
• Server-Side Implementation (updated to reflect refactoring)
• Architecture
• Security
• Unit Testing Web Applications
• jQuery UI Widgets
• Widget QuickStart
• How to: Check UIElement Properties with Coded UI Test
• How to: Create Automation Negative case with Coded UI Test
• How to: Create Web Client UI Test using Coded UI Test

Close

We welcome and appreciate your feedback on the application and book content.

Have a great day,

Just a grain of sand on the worlds beaches.

One of the early project work items was to demonstrate IE9 windows shell integration or pinned sites. Project Silk has a nice pinned sites experience that includes static and dynamic jump list items as well as dynamic notification icons.

The dynamic jump list items and notification icons are driven by the number of overdue maintenance reminders the currently logged in user needs to attend to.

Our team had a lingering problem with the dynamic jump lists; they were not displaying consistently across team member computers. As you can imagine, this was a source of frustration since the feature is actually cool and requires very little in the way of code to implement.

I got up early this morning and started writing the Application Notifications chapter which includes our implementation of IE9 pinned sites. I’ve not been able to see the dynamic jump list items on my laptop or home computers. I spent about an hour debugging our JavaScript, hoping to find something wrong. No such luck.

Others on the Internet have reported similar problems with solutions ranging from disabling all shell extensions, to clearing out the jump list folders. (Not something I want to recommend to users of Project Silk.)

Turns out, the displaying of jump list items is tied to a Taskbar and Start Menu Properties dialog setting, “Store and display recently opened items in the Start menu and the taskbar.”

Required Configuration for Jump List Items to Display

If you’re like me and don’t want Windows adding items to an already busy start menu, you turn off both of the below options. However, for jump lists to work, you’ll need to enable the second option.

Not sure why jump list item displaying is tied to this setting, will have to inquire about this.

Close

You can follow Project Silk, provide feedback on the code and book chapters here.

Have a great day,

Just a grain of sand on the worlds beaches.

Guidance Chapters Ready for Review

Today’s drop includes the following chapters (provided in CHM or PDF format) that are ready for community review. Our team very much appreciates your feedback and technical review. All documentation feedback should be posted in the Issue Tracker; if required, a document can be attached along with the feedback.

• Architecture
• jQuery UI Widgets
• Server-Side Implementation
• Security
• Unit Testing Web Applications
• Widget QuickStart
• How to: Check UIElement Properties with Coded UI Test
• How to: Create Automation Negative case with Coded UI Test
• How to: Create Web Client Test Automation with Coded UI Test

jQuery UI Widget Chapter

The jQuery UI Widget chapter provides comprehensive coverage of the jQuery UI Widget Factory and how to author your own widgets.

Project Silk uses widgets to modularize its client-side JavaScript. Widgets are powerful objects that provide a good amount of built-in infrastructure yet are simple to use. The above Architecture chapter provides the high-level view of Project Silk and explains the important role widgets play.

What you can expect to learn from the widget chapter:

• How to define and apply widgets
• How to manage the lifetime of widgets
• How to define default options that permit overrides and change notifications
• How to use options for decoupling behavior and facilitating event subscriptions
• How to use private methods to improve the readability of the code
• How to define and use public methods, properties, and events
• How to inherit from a base widget

Downloads

Latest documentation drop (24 May 2011): http://silk.codeplex.com/releases/view/66995

Latest code drop (Drop 9 – 10 May 2011): http://silk.codeplex.com/releases/view/66045

Have a great day,

Just a grain of sand on the worlds beaches.

Registration is now open for the  patterns & practices Prism, Unity, WPF, MVVM training event, 27-29 June in Boise, ID. All event information can be found on the registration page.

Register:  http://prismboise-eorg.eventbrite.com/

In addition a dinner is planned for Sunday, 26 June at the Goodwood Barbecue Company at 6:00pm.

Register: http://prismboisedinner-eorg.eventbrite.com/

Very much looking forward to these events.

Have a great day,

Just a grain of sand on the worlds beaches.

Save the dates for a 3 day patterns & practices Prism, Unity, WPF, MVVM training event, 27-29 June in Boise, ID.

Join three Prism Team members Bob Brumfield (lead developer), Geoff Cox (developer), and myself (program manager) for an information packed 2 days of instruction followed up by a day of pair-programming.

Day one will consist of WPF and MVVM topics; day two Prism 4.0 and Unity; day three is dedicated to pair-programming, getting your questions answered, and an opportunity for you to apply the last two days’ training against your scenarios and programming style. The pair-programming day is always so much fun along with some wicked coding.

This is a free event for 75 attendees. Each seat has a desktop, power and wireless.

Registration will open soon and will be announced on my blog and twitter.

Very much looking forward to spending time with developers and taking in the beauty of Idaho.

Have a great day,

Just a grain of sand on the worlds beaches.