WinForms Port

Topics: Extensibility
Nov 25, 2011 at 1:38 PM

Hi Guys,

I just created a fork with very limited port to WinForms. So far I've ported the Screens/Conductors classes and I'm actually using them in a pet project.  I also developed a ModelBinder for WinForms which I'm planning to integrate into this fork. Please feel free to contribute and discuss.



Nov 28, 2011 at 6:45 PM

Have you got a link to where the project is?

Nov 29, 2011 at 8:40 AM




May 20, 2012 at 10:12 PM

Hi Juan,

I was trying to port only Screens and Conductors part. Thanks for your work. I had a look at but that's a different kind of port.

Did you make any progress in the ModelBinder port?


Tiago Freitas Leal

May 21, 2012 at 7:56 AM


unfortunately I didn't make any progress porting my model binder to caliburn micro. Note however that I have a working sample at 



May 24, 2012 at 12:16 AM

Hi Juan,

Adapting CM to Windows Forms is so hard mostly (but not exclusively) because of DependencyProperty. I found Truss at

Truss is a binding library for POCOs in .NET. Unlike binding infrastructure that ships with the .NET framework, it is not tied to any particular UI technology.

It overcomes most limitations of WinForms databing and sounds interesting. Full documentation is included in the sources and the license is MS-PL.

I'll give it a try and report back if I made some progress.

May 24, 2012 at 2:17 PM

Hi Tiago,

Truss looks promising, moreover considering it's developed by Kent Boogaart