Nigel Sampson

It looks interesting, I'm not sure what the effort would be required to fully implement Caliburn.Micro in Avalonia. In terms of doing the bare minimum in order get your view...

I'm not sure off the top of head what's going wrong here, if you can provide a small sample that illustrates the problem I'll dig into it in more detail.

I can't see anything obviously wrong with that code, do any of the CM conventions work inside that view or is it just the buttons that aren't having conventions applied?

Can I confirm the buttons are located in the view? It sounds a silly question, but often there's a content control representing the dialog that ends up containing the view...

If you set the x:Name of the TextBlock to Title (and remove the binding) is the convention being applied?

Can you add the following to your bootstrapper to enable logging for the view model binder. ``` csharp var baseGetLog = LogManager.GetLog; LogManager.GetLog = t => t == typeof (ViewModelBinder)...

Most of the time there's no problem creating the UI bits and binding them before showing them on screen. However it does appear that this is the problem there. Until...

Sorry I don't follow what you mean by "do a binding to an ItemsSource and try to link the data context's button to a code-behind click event".

Don't think anything here has been resolved. I've left it open to come back to when I have time.

This looks a lot like PrismLibrary/Prism#140 . Adding the `Bindable` attribute in to your repro gets the unit test running. ``` csharp [Bindable] public sealed partial class App ``` Not...