Can't run MahApps 1.5.0 Caliburn Demos on VS2015

[oschwab]

Hello,

I can't run Caliburn demo projects (4.0 and 4.5) from my VS2015 workstation.
Both fails on AppBootstrapper GetInstance method , finding no contract for settings

Environment

• MahApps.Metro 1.5.0
• Windows 10
• Visual Studio 2015
• .NET Framework 4.0 && 4.5

[punker76]

@oschwab Saw this too after 1.5.0 release, but I'm not a good Caliburn user

[oschwab]

@punker76 I had an issue on my own project with flyouts after mahapps update ; as I used Caliburn sample as a basis, I tried to see how it was done in it, and boom !

[Eternal21]

Looks like caliburn can't locate views for the flyout viewmodels. I got the project to run by commenting out all fly-outs inside OnInitialize() function. Kind of defeats the purpose, since fly-outs are all there is to the demo. I will look into actually fixing the problem when I get some spare time.

[oschwab]

I think it might be linked to this change :

Change Flyout from ContentControl to HeaderedContentControl which has the correct properties for headers.

2874108

[Eternal21]

There's a related stackoverflow question, with no answers so far: http://stackoverflow.com/questions/43735278/wpf-mahapps-metro-caliburn-micro-flyout-headeredcontentcontrol

I've gotten the flyouts to work by commenting out 'this.Header = "' inside each Flyout constructor:

Obviously, that still doesn't help with locating and binding to their views, as you just end up with this:

[oschwab]

@Eternal21 We're both exactly at the same point ...

[oschwab]

@Eternal21 @punker76 Commenting the Binding to Header in ShellView.xaml makes the demo work again

[Eternal21]

Yes it does. The only problem now is, it displays the path to viewmodel now instead of the header title:

[seb30]

There's a related stackoverflow question, with no answers so far

Hey guys, it's me.

[seb30]

This works, but only if 1 Flyout is opened. If you're going to open another one, only the Header of the old one will be visible.

[punker76]

It seems it is a generally problem of Caliburn and HeaderedContentControl and/or the sample must be rewritten to work correctly.

[jamithiran]

@seb30 , your suggestion (setting the content) finally brought the agony of many hours to an end but as you mentioned the second one has problems. It shows only the header.

The one that shows the content is usually the first flyout added in viewmodel. I'm referring to my development project in VS2017. Did you have any success in resolving this situation? I chose to use CM only because I could not open/close flyout from viewmodel.

Thanks