Source code checked in, #d559c91279cb92c43724bfbe8212a00ede8988cf
add missing xml comments and some code formatting
View ArticleNew Post: Win 8.1 ArgumentException in Caliburn.Micro.DLL
[SOLVED] I figured it out what was going wrong. The problem was an uninitialized BindableCollection<T> property in the CurrentSezioneViewModel... In Windows RT and Windows 8 this has never been a...
View ArticleNew Post: When will the DisplayName virtual fixes be available?
I just updated to 1.5.2 and was surprised to see that Screen.DisplayName was no longer virtual; I was overriding it all over the place. I also noticed this is fixed in the current master branch. Any...
View ArticleCreated Unassigned: 1.5.2 removed `virtual` Screen.DisplayName [349]
I just brought down 1.5.2 and noticed a bunch of compile errors; apparently Screen.DisplayName is no longer virtual. This is fixed in 2.0.x but it would be nice to provide a fix to 1.x users.
View ArticleNew Post: When will the DisplayName virtual fixes be available?
This is available in 2.0.0.-alpha2 release already. You can get it on Nuget.
View ArticleCommented Unassigned: Partial unsubscription (and subscription) [347]
Sometimes a subscriber may no longer be interested in receiving messages of a certain type, however in its present form, if you unsubcribe from the event aggregator, you do so for all message types.So...
View ArticleClosed Unassigned: Partial unsubscription (and subscription) [347]
Sometimes a subscriber may no longer be interested in receiving messages of a certain type, however in its present form, if you unsubcribe from the event aggregator, you do so for all message types.So...
View ArticleClosed Feature: [Win81] Add conventions for Flyouts and Hubs [339]
Flyouts and Hubs have changed between Win 8 and Win 8.1, so the conventions currently don't work.Comments: Flyouts work for Hubs there will be some documentation describing how to use it with CM.
View ArticleNew Post: Upgrading project to 2.0 alpha
hi first CM is just great. I've spent the last 2 weeks trying to understand it and convert my badly written wp8 vb.net app to use the this framework. I will release my app.v2 in January, one of the...
View ArticleCommented Unassigned: 1.5.2 removed `virtual` Screen.DisplayName [349]
I just brought down 1.5.2 and noticed a bunch of compile errors; apparently Screen.DisplayName is no longer virtual. This is fixed in 2.0.x but it would be nice to provide a fix to 1.x users.Comments:...
View ArticleClosed Unassigned: 1.5.2 removed `virtual` Screen.DisplayName [349]
I just brought down 1.5.2 and noticed a bunch of compile errors; apparently Screen.DisplayName is no longer virtual. This is fixed in 2.0.x but it would be nice to provide a fix to 1.x users.
View ArticleNew Post: Upgrading project to 2.0 alpha
We would really appreciate if more people test the 2.0 per-release to find the last outstanding issues. If you don't use any 3rd-party caliburn.micro extensions, the upgrade should be straight forward...
View ArticleCommented Unassigned: 1.5.2 removed `virtual` Screen.DisplayName [349]
I just brought down 1.5.2 and noticed a bunch of compile errors; apparently Screen.DisplayName is no longer virtual. This is fixed in 2.0.x but it would be nice to provide a fix to 1.x users.Comments:...
View ArticleNew Post: Methods for providing view model dependencies
I've been doing some reading on the "correct" method of resolving view model dependencies throughout my CM application. Having read an article [1] on Stack Overflow regarding this, I was not convinced...
View ArticleNew Post: Upgrading project to 2.0 alpha
ok upgraded to v.2; pretty straight forward, remove the old version first. Upgrade. need to modify bootstrapper which is straight forward and add references to C.M.Platform in xaml so far so good
View ArticleNew Post: Upgrading project to 2.0 alpha
@Tibel been using 2.0 alpha in 3 projects, haven't seen anyone glaring issues thus far. I am actually using it in 1 of each type atm... Windows 8.1 (will be a calculator for pilots with respect to FAR...
View ArticleCreated Unassigned: DefaultCloseStrategy fails with null ref exception [350]
Consider the following simplified scenario.A Conductor<>.Collection.OneActive has two children.For whatever reason some action asks for these children to be closed one after the other. This will...
View ArticleCommented Unassigned: DefaultCloseStrategy fails with null ref exception [350]
Consider the following simplified scenario.A Conductor<>.Collection.OneActive has two children.For whatever reason some action asks for these children to be closed one after the other. This will...
View Article