KasperSK

@vb2ae I think current behavior should be the default. I was thinking about making a global flag to opt in for all action messages and a local flag to overwrite...

I believe that I still need to make it so that you can change between the old and the new behavior. Might look at it this week. Then we should...

@inforithmics I have been busy trying to test on iOS and macOS and that is working now, so the next step would be to get this working and then merging...

I wish thinking we might should prepend CAL_ to the other defines so that we can control them the issue was the MSBuild.sdk.extras defined NETCORE for UAP and that was...

I have a bugfix we need to do before merging this.

@vb2ae I don't have any more changes for this branch would why disagree to merging this PR?

I think it would be a good idea to have a sample program that could be used as a reference on how to use Caliburn.Micro. The features sample already does...

It is not meant to force you to use all platforms, the individual project are to be templates so that a user can choose the one that is right for...

@lorinkundert I am not sure `WinForms` is fit for `MVVM`, which is what `Caliburn.Micro` provides a framework for. I know it can be done but I would choose another technology...

That's great but I think `ReactiveUI` uses their own bindings, to my knowledge there is not a binding engine in WinForms like there are in the other UI frameworks.