caliburn.micro

I think I am missing something obvious. But since the main window of my Application is a UserControl that is being launched by protected override void OnStartup(object sender, StartupEventArgs e) { DisplayRootViewFor<MainWindowViewModel>(); } in my bootstrapper how do I set the Icon of the window itself and of the application in the toolbar? XAML based solution : Change your MainWindowView base class from UserControl to Window (both in .xaml and in .xaml.cs), then set your Icon property or any other window-specific properties right in xaml. Code based solution : DisplayRootViewFor<T> takes an

With Caliburn.Micro I'd like to know the pros and cons of exposing an EF4 Entity as a property of the ViewModel (a technique discussed here and here ). This allows me to avoid writing getters and setters for every field (see OneCustomer below). The drawback is I need to write all of the binding statements in XAML (below LastName is not in the ViewModel but does require XAML binding). If I stick to the prescribed technique of filling my ViewModel with properties for each field (as FirstName below) I'll ultimately have to write a ton of extra code just so NotifyOfProperyChange will get called.

I'm quite new to Caliburn.Micro, so I guess this has a simple answer (or at least I hope it has :)) I have a ViewModel with a property called ConnectedSystem that has a sub-property called Name . In my View, I have the following XAML (excerpt): <StackPanel Orientation="Horizontal"> <Label Content="Name:" /> <TextBlock x:Name="ConnectedSystem_Name" /> </StackPanel> This works just fine, and the name is shown in the TextBlock as expected. However, ConnectedSystem has around 10 properties that should be displayed, and I don't want to copy-paste the XAML above 10 times inside my view. Instead I

I am currently experimenting with view composition in Caliburn.Micro. I have a working example where I have multiple user control based views injected into my main shell via the "View.Model" attached property route. So far so good. In my application proper I am working with a mixed environment of mainly WinForms, with some WPF, so there is no WPF "shell" for Caliburn to manage. I'd like to be able to create my views on demand and add them to placeholders in my WinForms app. I would like to know how I go about creating a view (which will be a user control containing sub user controls)

I'm following this tutorial on Screen and ScreenConductors in Caliburn.Micro Framework. I'm using WPF, not Silverlight, and I have made the corresponding changes in App.xaml (using MergedDictionary for the Bootstrapper). The original Simple Navigation example has a shell with two buttons, and a content area where two possible screens are displayed, conducted by the ShellViewModel . Then I tried to move each button to its counterpart View, so that PageOne would have a button to take to PageTwo, and vice-versa. I did it because I don't want the home shell continuously "showing its entrails"

How is it possible to re-use and compose parts in CM managed windows? I have found posts regarding using two UserControls to bind to the same ViewModel, but not so much if I want to have multiple views and viewmodels all composed in the same window. (a viewmodel for each view composed into a "master view") The first part of my question would be how to break up components for re-use? If I have two areas of a window where one is a datagrid and another is a details view with labels and text boxes should these be in separate usercontrols, customcontrols or windows? Each one would ideally be stand