C# Soup To Nuts: C# and Windows Presentation Foundation

Well... after a little break, I'm back with the C# Soup To Nuts webcast series.  This time, with a new webcast about Windows Presentation Foundation.  This will be a quick introduction to what WPF brings to the table for C# developers, preparing you for my next webcast series called WPF Soup To Nuts.  Still finalizing the details, but stay tuned.

As we wind down this series, today, we're going to look at what WPF allows us to do.  I will introduce you to XAML and show you how it ties in with C# very nicely.  We'll then take a look at how XAML and WPF allow us to build web pages and desktop apps using the same language.  We'll explore the types of controls that WPF has and see how easy it is to modify them to suit your own look and feel requirements.

As always, demo code is attached.

See you there!



Comments (2)

  1. dgk02 says:

    Thanks for the presentation, there aren’t many webcasts on WPF. I’m confused about the online access of an XBap. I thought I had read that they only have access to the originating URL (or fileshare if on a network). But you pulled the image from your website.

    Also, XBap, and WPF in general, doesn’t seem to have any data controls, nor the ReportViewer, to which I’ve become addicted.

    Am I missing something here? How can I tie into Northwind?

  2. zainnab says:

    Actually, every control and/or property can be bound to anything, so the concept of a Data Control like the Grid is easy to reproduce with a couple of the standard controls.

    Anand Iyer will be doing a little series on WPF in May and one of his sessions covers binding.  Check it out on http://www.microsoft.com/webcasts.  I will also be doing a series starting in July called WPF Soup To Nuts.  I have several sessions dedicated to binding.  It’s a very powerful concept in WPF.

    As for the image… it’s just a standard image – like one in HTML.  Even javascript can pull the images from other sites with ease.  It’s only the services like web services, etc, where the sandbox would step in and block it.  (By the way, the ReportViewer control will work just fine in a WPF window… in fact, all of the standard "Classic ActiveX" controls will work in WPF.


Skip to main content