IronPython Integration Sample and the WPF Designer

If you've had the opportunity to work with WPF/.NET 3.0 yet, you've likely run into the x:Class attribute in XAML. If you specify a x:Class on a XAML page, during compilation the XAML compiler creates a class in code using the registered CodeDomProvider for the given language that you're compiling. This presented some challenges for getting the IronPython sample to work with the new designer.
There were two major problems:

1) The IronPython CodeDomProvider is not registered globally on the machine.
2)IronPython 1.1 does not support compiling to .NET-consumable types.

Read the rest here: http://blogs.msdn.com/aaronmar/archive/2007/08/01/ironpython-integration-sample-and-the-wpf-designer.aspx