Linked Resource Dictionaries in Loose XAML

Something cool that I didn’t know “just worked” – linked resource dictionaries in Loose XAML! In this sample: dictionary.xaml contains a ResourceDictionary page.xaml just links to dictionary.xaml. See how it looks when you navigate to page.xaml. (And don’t forget to click on the fishies!) Page.xaml: <Page   xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/presentation”   xmlns:x=”http://schemas.microsoft.com/winfx/2006/xaml”>    <Page.Resources>        <ResourceDictionary Source=”dictionary.xaml”/>    </Page.Resources>        <Button Style=”{StaticResource BigFish}”>            <Button Style=”{StaticResource SmallFish}”/>        </Button> </Page> BTW, you might have seen these styles before… They come from the WPF Feature Montage originally given by Fil Fortes at Mix06 & updated by Rob Relyea for TechEd

Updated Samples for June CTP

FYI: I’ve posted June CTP versions of most of my samples: Woodgrove XBAP XBAP: On Demand & ClickOnce Cube Animation XBAP using VS Flexible Template Photostore: Standalone & XBAP. (TechEd Chalktalk demo) Get the June CTP drops here: .NET Framework 3.0 Windows SDK Orcas Tools for .NET 3.0

Mount Si

On Saturday went hiking to Mount Si, one of the quintessential Seattle hikes. It was a beautiful day, with a clear view of Mount Rainer from the top.

XBAPs: OnDemand & ClickOnce

If your XBAP has some “heft” to it (large resource files, large assemblies, etc), it may make sense to architect your app to use ClickOnce’s OnDemand APIs. OnDemand APIs enable developers to delay download parts of the application. This can result in a friendlier end-user UX. Note: OnDemand files can be traditional resource files (e.g. images, xml files, etc) or assemblies. Architecture Tips & Tricks Got satellite assemblies or large resource files? Slim down your primary EXE to the bare minimum needed to start the app. Then, when the XBAP is launched, only the application manifest, deployment manifest, and primary …

Caching & XBAPs

When relying on resources living on a server, you can increase client app perf & decrease network traffic by storing local versions. When trying to build a sandboxed XBAP, however, you cannot create your own local cache store in the file system beyond the space available in isolated storage (512KB). Fortunately, WPF resource loading uses System.NET’s HttpWebRequest and its “Default” caching policy. In addition, depending on your resources’ sizes and your scenario, it may make sense to use a non-default caching policy when issuing your own HttpWebRequest. This post aims to give you a little bit of caching context, an …

New York City

Had a fun quick trip to New York City. Spent several hours at the Museum of Modern Art. The MOMA is just amazing… it makes the SF MOMA just look so small and modest in comparison. I’m jealous of new yorkers who have such a rich collection in such a beautiful building so close to them.

Woodgrove Demo

At the TechEd chalktalk that Ashish and I tag teamed earlier this week, I demo-ed the Woodgrove Financial Application as an XBAP. I also showed loose XAML and an embedded FlowDocument inside of an HTML. loose XAML with vector graphics (link) Woodgrove financial app w/ 3D chart as xbap (link) html page with FlowDocument in IFRAME (link) Try try out the app. The last scenario (FlowDocument in HTML) is particularly compelling: You can leverage your existing site. If you have your article content in XML, it’s easy to create another XSLT transform to XAML. Your content continues to be viewable …