WPF Application Lob The search for patterns and procedures (
patterns and practices , mm reminds me of something) to develop rapid and robust
data-oriented applications with WPF
.
- L 'architecture : MV- VM
answer: We must stem the proliferation code through the layers. - Data Access: Entity Framework
- DTO
use the data transfer object only communication between components located between the services or even for communication between a layer and the other?
Dto flat or structured? Little or DTO? - OF: Unity
to start, perhaps easier MEF (the resolution is not required runtime dependencies) - Patterns & Practices ? reads as at first glance looks like a wagon than a lot of code difficult to attack, we'll see ...
Where to start?
The tutorial is available as extension of VS2010, code and tutorials integrated into a single project VisualStudio. In four iterations of the same project changing from a ' WPF application addressed as it was with windows forms ( ModelViewPresenter , still useful to understand how to use the simply DataContext). And then integrate MVVM , databinding , command, unity , tests, mock .
A bellyful surface of all but an idea of \u200b\u200bform to give to their application .
Some things to watch:
- use Relay Command
- chiamre the messagebox through a service.
You realize then that the key ideas of
tutorial (and almost all the code
infrastructure) are all present in
MVVM Litght Toolkit in Codeplex ( I would say this will
framework of reference for the rest)
's event aggregation is explained perhaps too summarily :
[the following post answers the question of how pass messages from one view to another ]
Composition and Validation of IU?
What I still lack?
- Validation (l ' application is data-oriented)
- Navigation between the "pages" (or window ?)
- Composition of IU (given that Prism is 'goal to strive for a simpler approach / pragmatic approach could solve the issue entirely)
level of complexity as you go back a bit 'behind the examples we've seen before (besides this article of 2009). Interesting to we see the use of IDataErrorInfo for validation and a simple solution to load / replace the UI different view.
On Hold Fluent Validation
an eye!
Sigh. . . because too much snow that slowed us down after Montebello, we had to give up half Torre Bonini, but soon going to try again S. Jacques Mortano 
