Comment on Coproject - a RIA Caliburn.Micro demo, part 8 by Augustin Šulc

2012-05-15T13:52:47

Hi, I'd try to debug the application and see if there aren't any exceptions in the C.M stack. Usually, if nothing happens when an action should be called, it is because of C.M silently failing with an exception. Otherwise, from your description, I am not able to guess where the problem is :-( Also, don't you have problems with component lifetime in Autofac? The original solution uses NonShared CreationPolicy so a new instance is created everytime MEF is asked for a component (ie. no singleton).

Comment on Coproject - a RIA Caliburn.Micro demo, part 1 by Augustin Šulc

2012-05-15T13:44:07

You can get source code from Codeplex: http://coproject.codeplex.com/SourceControl/list/changesets but for this tutorial, you simply start with New Silverlight project from VS.

Comment on Coproject - a RIA Caliburn.Micro demo, part 2 by Augustin Šulc

2012-05-15T13:40:33

To use it for EF4.3, we just had to update XML headers in the template to match the EDMX file. No other problems.

Comment on Coproject - a RIA Caliburn.Micro demo, part 1 by TimNape

2012-05-15T10:08:35

Where do I download the initial project

Comment on Coproject - a RIA Caliburn.Micro demo, part 2 by Leo

2012-05-14T06:20:56

Is it stable for EF 4.1/4.3? I had my own T4 template generator.

Comment on Coproject - a RIA Caliburn.Micro demo, part 8 by Leo

2012-05-14T06:08:51

Hi, I modified your solution to switch to DbDomainService and use EF 4.1. I have a problem now with selection changed event fired by Caliburn Micro. At first, the items are called but once I switch an item and go back to the previous item that was loaded, then the SelectionChanged Action won't be triggered. The OpenItemDetails method does not fire again. I don't know why. It is kind of odd though.I am also using Autofac instead of MEF. I don't see the reason why, I tried making a simple listbox inside it instead of binding to ToDoItems. The method is properly working fine, even if I switch back and forth. But if I binded it to the ToDoItems its no longer being called again. Just once. Note: I know your solution works cause I tried everything from part 1 to part 14. Although I don't see the main reason why what would cause this behavior. Regards,

Comment on Coproject - a RIA Caliburn.Micro demo, part 14 by Augustin Šulc

2012-05-07T14:14:32

When closing a child of a LazyConductor, it only calls Reset() function on the child LazyScreen. So the main logic is in LazyScreen. When you open the child again, the LazyScreen's view model gets recreated so you should see the original values (provided you use NonShared CreationPolicy so that MEF creates a new instance for you).

Comment on Coproject - a RIA Caliburn.Micro demo, part 2 by Augustin Šulc

2012-05-07T14:02:15

We use T4RIA templates to generate services, metadata and resources. The template also supports separation of custom and generated code. You can find it here: http://riaservicescontrib.codeplex.com/wikipage?title=T4RIA Moreover, it is quite easy to customize the code generation to suite your needs.

Comment on Coproject - a RIA Caliburn.Micro demo, part 2 by Leo

2012-05-06T16:05:26

Hey, is there a way if I updated my model from the database and I want to refresh the service class is it possible? or do I have to always setup or manually add those functions in the service class

Comment on Coproject - a RIA Caliburn.Micro demo, part 14 by Leo

2012-05-05T17:47:44

Hey, Just a quick question with your implementation of LazyConductor, does this solve the problem when resetting a view model that has a backing properties mapped to a Model and a simple backing properties? So If I try to close an active item, edit changes, hit close and open again the item will it reset the Model and the normal backing properties to its original values not with the updated one like I did not click save but the view still shows the updated value. So it is not yet persisted. Thanks!

Comment on Fast switching between ViewModels in Caliburn.Micro by Augustin Šulc

2012-03-28T08:26:40

Both samples work on my machine. What error and where do you get?

Comment on Fast switching between ViewModels in Caliburn.Micro by Bruno Samardzic

2012-03-27T15:26:22

Hey, great work, but the contentControl example is not working for some reason

Comment on Coproject - a RIA Caliburn.Micro demo, part 8 by Augustin Šulc

2012-03-24T10:57:24

If editor variable is not null, no result would be returned so we have to yield break. I guess it would not even build without it.

Comment on Coproject - a RIA Caliburn.Micro demo, part 8 by vmlf

2012-03-23T11:35:49

Hello, insignificant detail but in the OpenItemDetail method, why is there a "yield break;" at the end? Can't come up with a reason for it. Thanks

Comment on Coproject - a RIA Caliburn.Micro demo, part 11 by Augustin Šulc

2012-02-13T18:28:54

@Albert It is mentioned in the last sentence before code exaple with "public void Handle..." - the sentence starting with "Let the view model implement IHandle..." I'll make it bold to be more emphasised.

Comment on Coproject - a RIA Caliburn.Micro demo, part 11 by Albert van Peppen

2012-02-13T09:46:39

When I found myself on this page of the tutorial I found that the eventhandling didn't work as descruibed, but gave it no notion since I wanted to run through the entire tutorial first. After doing the entire tutorial I came back to this point to figure out what it was that I was doing wrong. I found that you don't describe that you should derive the ToDoListsViewModel from IHandle as well; that was the trigger why it didn't work. Is this correct or did I missed something else? My class definition now looks like: (Note that I already did the rest of the tutorial) public class ToDoListsViewModel : Conductor.Collection.OneActive, IModule, IHandle Instead of: public class ToDoListsViewModel : Conductor.Collection.OneActive, IModule Albert

Comment on Coproject - a RIA Caliburn.Micro demo, part 10.5 by Augustin Šulc

2012-02-10T21:35:26

@Albert: Thank you for the tip about Caliburn tag. It should be fixed now. No problem about your other question - it happens to all of us ;-) I hope that despite this misunderstanding, the tutorial helped or at least inspired you...

Comment on Coproject - a RIA Caliburn.Micro demo, part 10.5 by Albert van Peppen

2012-02-10T16:11:29

Please ignore the second point in my previous post; I was still not awake and the coffee was still in the cup... Ofcourse the coloring is there; you have turned on some debugging features that just do that to indicate what's happening.. Sorry for the stupid question :(

Comment on Coproject - a RIA Caliburn.Micro demo, part 10.5 by Albert van Peppen

2012-02-10T12:05:39

Hi, first of all: great articles! Next I have some remarks/questions; Firstly, can you Tag this tutorial episode 10.5 on CaliBurn as well; I totally missed the 10.5 because I have been walking the tutorial on the Caliburn Tag :) Secondly, I don't see how your given solution makes everything fine; When I apply your changes, the ShellView seems ok now, but when you hover the 'menu'-list you'll see the colors appearing on the list items. When selecting the ToDoListsView you also see that this view is totally sick ( :) ) as well.. Can you explain why this is? Keep up the great work!

Comment on Coproject - a RIA Caliburn.Micro demo, part 14 by Jitendra

2012-01-23T15:50:35

I have just started with Caliburn Micro and Silverlight and this article is really useful.