• Get the Bing Maps Silverlight Control
• Get a Bing Maps API Key
• Play with the Bing Maps interactive SDK Application
• Read the Bing Maps blog
• Check out the Bing Maps forum

You can also get the source code to my presentation here:  Download the source.

Note: You will need to download the Bing Maps Silverlight control and re-reference the DLLs before the source will compile.  Also, you have to have a Bing Maps API key in order to use any of the geocoding service examples.

I also have a blog post that steps you through the sample code here.

Like always, if you have any questions feel free to ask.

Recap:

The Silverlight and WPF platforms are very similar, but they do not have binary compatibility; this means that an assembly compiled for one platform cannot execute on the other platform (Although, the story is a little different in Silverlight 4). You may want to target some or all of your application on WPF and Silverlight for a number of reasons.

Due to the fact that Silverlight and WPF are so closely related, the bulk of your application code can be shared between the two platforms. This encourages heavy use of pattern based development to isolate the logic from the presentation and maximize the separation between UI code and non-UI code.

Elements you can share:

• Presenters
• Controllers
• Models
• Services
• Unit tests
• Simple views, if the XAML used is supported by both Silverlight and WPF.

Elements that are harder to share:

• Complex views (XAML)
• Controls
• Styling
• Animation

Like always, if anyone has any questions feel free ask.

Download Sample Code

I know I covered the subject fast, but I was in a hurry. I had to go to the airport. So here is a quick review.

Event Types:

• Direct events are like ordinary .NET events. They originate in one element and don’t pass to any other. For example, MouseEnter is a direct event.
• Bubbling events are events that travel up the containment hierarchy. For example, MouseDown is a bubbling event. It is raised first by the element that is clicked. Next, it is raised by that element’s parent, and then by that element’s parent, and so on, until WPF reaches the top of the element tree.
• Tunneling events are events that travel down the containment hierarchy. They give you the chance to preview (and possible stop) an event before it reaches the appropriate control. For example, PreviewKeyDown allows you to intercept a key press, first at the window level, and then in increasingly more specific containers until you reach the element that had focus when the key was pressed.

RoutedEventArgs Class:

• Source indicates what object raised the event.
• OriginalSource indicates what object originally raised the event. Usually the OriginalSource is the same a the Source. But in some cases they could be different. For example, if you click close to the border of a window, you will get a Window object for the Source but a Border object for the OriginalSource.
• RoutedEvent provides the RoutedEvent object for the event triggered by your event handler.
• Handled allows you to halt the event bubbling or tunneling process.

Here is a simple example of when you might use a bubbling event:

<StackPanel Hyperlink.Click="StackPanel_Click">

    <TextBlock>

        <Hyperlink NavigateUri="http://www.yahoo.com">Yahoo!</Hyperlink>

   </TextBlock>

   <TextBlock>

       <Hyperlink NavigateUri="http://www.google.com">Google</Hyperlink>

   </TextBlock>

   <TextBlock>

       <Hyperlink NavigateUri="http://www.msn.com">MSN</Hyperlink>

   </TextBlock>

</StackPanel>

private void StackPanel_Click(object sender, RoutedEventArgs e)

{

    Process.Start(((Hyperlink)e.Source).NavigateUri.ToString());

}

So instead of having to create an event handler for each hyperlink, or creating a single event handler and pointing each hyperlink to the same event handler, I can use one event handler on the parent element.

Download the Presentation Source. This contains all the examples that I covered during the presentation.

Download the WPF ReorderableListBox. This is the custom WPF ListBox control that allows you to drag and drop items within the same ListBox to reorder or rearrange their order/position. The code is very unpolished right now and is not documented yet, but I wanted to go ahead and throw it out here so you could start playing with it. I plan on cleaning it up, documenting it, giving props to the blogs that helped, and writing a more detailed post on the ReorderableListBox control in the future, but for now play with it, modify it, and give me feedback. Maybe we should make it a CodePlex project.

Useful links:

• The WPF Toolkit is a collection of free WPF features and components.
• The WPF Ribbon is Microsoft's  free ribbon control for use in WPF applications. The CodePlex site for the ribbon is located here.
• Family.Show is a open source WPF application that allows you to build extensive family trees.
• Billy Hollis on Getting Started with WPF video

If anyone has any questions that were not asked during the presentation or would like me to elaborate on a certain aspect of the presentation, please feel free to drop me a comment and I will get right back to you.

• Bind to a property of a UI element
• Bind a property of a UI element to itself
• Bind to objects
• Bind to an enumeration

After the presentation I will post any sample code on my blog for download. For more information about NETDUG or to become a registered member, you can visit NETDUG’s website. Hope to see you there.