I'm a newbie in WPF 4 + Silverlight 4 and MVVM
I already read several books for an intro about all above, so i can get a concept.
And at first actually i have a plan to develop an app without a framework at all. ( because i want to learn a lot about how those are work together )
but i have awared that it's a lot of works that i must to do.
And now , i decide to use a framework CSLA.NET 4 as a business layer ( as roc has explained on his book ), currently I'm reading CSLA.NET 4 series.
And then I'm thinking about a UI layer ?
Am I must do all of this without a framework ? ( because, at first i want to learn about MVVM concept and implemented ).
or I have to choose or look for a framework for this layer ?
Could anyone give me a suggestion about my decision path here ? ( thanks a lot before ).
If i use a framework before i have ever tried to do a work without it, Am i can get an understanding about what is going on ?? like MVVM pattern, and another design pattern concept ??
thanks a lot for your responses before
God Bless You all
There's huge value in learning frameworks like CSLA - it certainly makes you very productive and from a business viewpoint you can deliver solutions quickly. There's also value in doing things without frameworks if you want to understand the nuts and bolts of .Net and the value of using frameworks in the first place, although reading the CSLA ebook series should explain the many benefits that a framwork provides and save you the pain of discovering these things yourself.
For MVVM you could try Rocky's Bxf framework at first - that way you can get up-to-speed on CSLA and your business layer and Data Portal options and create somthing using a very simple MVVM framework.
Then maybe try another UI framework. There seem to be many MVVM frameworks knocking about.
MVVM Light Toolkit is one. Caliburn is another. I've no experience here, but MVVM Light Toolkit seems to be light enough that it might be quick to learn it and has enough functionality.
StackOverflow has some postings with people asking the same question.
Thanks to richardb for your StacksOverflow link.
Our project also achieved good succes, when we started to use (commercial) UI components. For a LOB application, a commercial toolkit has already solved many of the daily problems, we were facing at a low level with WPF from .NET plus the WPF toolkit.
(We have choosen DevExpress, but the key factor has been the reporting part of the vendor - and the choice depends on your needs)
I believe, the remaining part - further functionality of the view model, common user controls or contol behaviour, application frame - depends a lot of a specific UI concept or philosophy. And that's why I doubt you can find something existing.
In short: I strongly recommend using
CslaContrib includes glue code that makes it easier to use Csla with Caliburn.Micro.
Copyright (c) Marimer LLC