Are there any pitfalls in writing WPF apps with IronRuby?

Using IronRuby/IronPython, you should technically be able to do anything you could do in C#/VB .Net. I'm curious if there is anything that would keep a serious rubyist from writing a WPF app for Windows/Silverlight if they were inclined. A post here mentions problems with Silverlight and bindings, but I think there are ways around that.

I'm working on an MVVM library that makes heavy use of dynamic, and I wanted to try it o开发者_如何学Gout with some examples using dynamic languages.

IronRuby doesn't include a WPF project template, and the link above is a workaround to force WPF to work, but it is not optimal. There isn't an option to setup App.xaml/App.xaml.cs (oops I mean App.xaml.rb), etc. This is the location where WPF application startup is performed, and it is needed for setting up Application-level static resources, etc.

IronPython, however, has a WPF project template and seems to set up WPF projects appropriately.

IronRuby seems a little behind IronPython for now (just IMO), so I think I'm going to stick with testing my MVVM framework for WPF in IronPython for now.