New Post: ViewModels are not attached automatically
Good day. Some of my ViewModels are not attached to views automatically. I use proper naming convention and declare those VMs using PerRequest, so, the usual stuff. But they are not attached to...
View ArticleNew Post: ViewModels are not attached automatically
can you give us an idea what you are seeing? Code / ScreenShot etc...
View ArticleNew Post: ViewModels are not attached automatically
File tree looks like this: ViewModels/ -- MainPageViewModel.cs -- News/ ---- NewsDetailsPageViewModel.cs -- Machines/ ---- MachineSearchPageViewModel.cs Views/ -- MainPage.xaml -- News/ ----...
View ArticleNew Post: IEventAggregator in View
Same problem... Maybe just pump resolved view instance through IoC.BuildUp (after InitializeComponents()) ? At least it helps implement property injection and dispense with service locator.
View ArticleNew Post: ViewModels are not attached automatically
I managed to make Machine Search Page work by recreating it within Views|ViewModels/ instead of Views|ViewModels/Machines.
View ArticleNew Post: IEventAggregator in View
in the Constructor of your viewpublicclass SomeView(){ IEventAggregator _events; public SomeViewConstructor(){ Bootstrapper bootstrapper = Application.Current.Resources["Bootstrapper"] as Bootstrapper;...
View ArticleNew Post: IEventAggregator in View
2 mvermef: For service locator approach i'm better will do so: IoC.Get<IEventAggregator>(null). But my desire is do without it.
View ArticleNew Post: IEventAggregator in View
CompositionBatch batch = new CompositionBatch(); batch.AddExportedValue<IEventAggregator>("Test", new EventAggregator()); IoC.Get<CompositionContainer>().Compose(batch);...
View ArticleNew Post: No support for Windows XP in Caliburn.Micro 2+?
@BladeWise: I'm looking forward to your patch. I just had to downgrade my client app from .NET 4.5 to 4 to support Windows XP. Fortunatelly Microsoft decided to support async/await in .NET 4 with the...
View ArticleNew Post: ViewLocator Issues..
OK, now I'm trying to repeat the experiment - only with separate projects in the same solution. Everything seems in order except at the point where CM is trying to find my view. I start with: protected...
View ArticleNew Post: async void verses asnyc Task
I am having issues with exceptions being swallowed. I have a single member which is bound to via Caliburn.Micro conventions. If this method is an 'async void' then the exception triggers the...
View ArticleNew Post: ViewLocator Issues..
The default convention is <BaseName><NameSuffix> (e.g. SomethingViewModel). Compare that to your example. If you want to change the way names are composed, you need to set an additional...
View ArticleNew Post: [WP8] Panorama control does not work with data-binding
Tutorial of Panorama control for Windows Forms
View ArticleSource code checked in, #48957dd61b53b2332216f222845f9837f93643f5
add IResult decorators
View ArticleCreated Unassigned: EventAggregator Issue in 2.0.2-aplha [353]
Hi,I recently migrated to Caliburn.Micro 2.0.2-aplha from v1.5.2.I have noticed that the default value for 2nd parameter (Action<System.Action> marshal) of EventAggregator.Publish method has been...
View ArticleCommented Unassigned: EventAggregator Issue in 2.0.2-aplha [353]
Hi,I recently migrated to Caliburn.Micro 2.0.2-aplha from v1.5.2.I have noticed that the default value for 2nd parameter (Action<System.Action> marshal) of EventAggregator.Publish method has been...
View ArticleClosed Unassigned: EventAggregator Issue in 2.0.2-aplha [353]
Hi,I recently migrated to Caliburn.Micro 2.0.2-aplha from v1.5.2.I have noticed that the default value for 2nd parameter (Action<System.Action> marshal) of EventAggregator.Publish method has been...
View ArticleNew Post: Conflicts on mscorlib with Reactive UI
Hi, I have recently updated a project that use both Caliburn.Micro and ReactiveUI to v2.0. Unfortunately, after that, I am no longer able to build my project as I get a conflict on...
View Article