MSDN Radio follow-up answers: Prism for Silverlight, DomainServices and relationships| Comments
- | Posted in
This morning I was on a weekly (new) radio show from MSDN, hosted by Mike Benkovich. The show, MSDN Radio, features live call-in questions that you can ask. It was a better format than the typical live meeting text-based QA I thought. I think hearing questions gives you a better chance of articulating your inquiry more. Thanks to all those who listened and asked questions. I know it seemed short and there were a few more questions in the queue – feel free to send me questions you may have.
UPDATE: The audio from the show was just posted here.
There were a few that I wanted to follow-up on and get some more answers from other team members. Here are 3 items I wanted to provide a bit more follow-up to (I’m paraphrasing the questions).
Vince asked a question around Prism and part of that was what are the plans for Prism moving forward? I didn’t know a concrete answer, so I quickly asked around. Take a look at the team’s post on Prism, A Look Ahead. The team talks about the next release (v4) to be around the September 2010 timeframe. They also comment on using Prism today with Silverlight 4. As to what will be in Prism 4? They offer some insight:
- Managed Extensibility Framework (MEF) – “In particular, we’ll be looking at leveraging MEF for Component Composition (for hooking up Views and ViewModels, and other types of components), for Modularity (for the discovery, download, and instantiation of functionality packaged in a module), and for UI Composition (for mapping Views to Regions).”
- Model-View-ViewModel (MVVM) Pattern – “…we’re looking to expand our current guidance and to include more re-usable code assets to support various MVVM scenarios. In particular, we’re looking to support common patterns for View/ViewModel interaction, hierarchical ViewModel composition, and ViewModel-based navigation. In addition, we’re also looking to provide more support for application-level structural patterns, layout management, the use of Ribbon/Popup/Dialog controls, and user state management.”
- Data Access and Application Services (i.e., WCF RIA Services) – “…we are looking to provide guidance on using these technologies in the context of MVVM, and on patterns for data validation and caching. This area also includes the use of other services for user preferences, authentication and authorization. This latter aspect brings in the possibility of providing guidance for role-driven (or claims-driven) applications and user experience.”
I’d encourage you to subscribe to their blog and be a part of their conversation over there as well.
Scott asked a question about how to best define DomainServices (contexts) in your application – is it better to have 1:1 for entity:DomainService or other methods. I asked the RIA Services team for some additional input to my answer.
DomainService should be based on a set of related tasks that you expect the end-user to perform in [your application]. Typically such tasks involve a small group of closely related entities; e.g. in an Expense reporting app, Expense Report, Line Items and Details would be a good set of entities to cover in a single DomainService while covering accounts and payments in a separate DomainService type.
Additionally Jane asked about many-to-many relationships with regard to RIA Services.
Currently RIA Services require the “class in the middle” containing FK values in a many-to-many. In a POCO model, you can add it yourself while in an EF-generated model, you would have to change the model (edmx) to add such a class in the middle.
Hopefully these provide some additional clarity on top of my opinions. There sure seems to be a lot of interest in the RIA Services space!
Hope this helps!
Please enjoy some of these other recent posts...