Ben & Ward, I totally agree with both of you on this.

The current ModelExplorer (ME) sample is a great introduction to DF Silverlight capabilities, without addressing some of the more application specific issues we face once we've rolled our sleeves up.  It's a good appetite wetter, got me hooked, and then the fun begins.

I agree that more detailed examples are required.  I've been racking my brains for the last week trying to determine what I want to say here while continuing to consume all available  information available from IdeaBlade web site and WPF and Silverlight books to supplement.  I am a novice in this subject currently, so am offering suggestions that will help other like individuals trying to fathom RIA and the DevForce framework concurrently.

I think though that Ward is right, keep the ME example basically how it is, and construct a Sample2 "real world" silverlight app that is more formalised in its object handling for certain situations.  Ben, the Customer, Order, Orderdetails master detail view handling is one example that could be included.   My additions/agreements to your great start include:

------------------------------------------------------------------

The whole shebang!   (or at least for Admin CRUD)

------------------------------------------------------------------

Recently I produced an ASP.NET app using NetTiers for a small job.  Works a treat, albeit basically two tier, and not RIA, but it works.  The community and CodeSmith have done a reasonable job in allowing a developer to point it at a database and produce a working ASP.NET app that renders a  working web site for all objects, linked navigation paths, and leaves the developer wondering how to massage it for use cases.  All the CRUD is done, even to the UI for Admin functions at least.  Not good documentation though as to what to do next.  Have to figure that out, and well, not RIA is it, nor has it got all the DF persistence and caching  goodies.

1. Now I've contemplated using ME as a template for Admin type functions, but even better would be an extension to the object mapper to nominate objects that are basically Admin (reference types) so that the Admin SL pages could be generated along with their objects and an SL UI that handles that.  I realise this is a simplistic notion to a complex issue but templates that handle 90% of application types yet allow the real punch (your framework) for those difficult apps would certainly help programmers like me.
    

   -----------------------------------

   Some more details please!

   -----------------------------------

2. This brings me to navigation properties.  Seems ME displays simple properties only (autopopulate = true), navigation properties are not exposed, yet they are very available as I discovered in some other  DF tutorials I worked with.  A Client business object may reference Region and when we expose Client on UI we need a bindable dropdown list of available Regions, with current selected item bound to FK property of Client.   "antalakas" post is relevant I think http://www.ideablade.com/forum/forum_posts.asp?TID=1199  An exmaple along this path would be great.
   
3. Security.  Hmmm.  2 samples please. 
1. Show how to collect a user's username password (forms) and globally keep the logged-in user for that session so any referenced xaml view page can identify security role and objects to display.  I say this under the impression (maybe false) that ASP.NET security is not used, and we need to construct our own methods using IEntityLoginManager.  Ben's post exposes this, KimJ answers eloquently, and I am left wondering "how?"  http://www.ideablade.com/forum/forum_posts.asp?TID=1169  An example app doing this would be great.
2. An simple example of how to manage role based security through SQL would be beneficial.  Identify a logged on user as either Admin or Standard and selectively hide menu items and challenge on each xaml page load.  From there we could expand on that using our own SQL security models depending on the granularity required
   
4. XAML user controls - or View controllers.  All IB examples (even WinForms) generally deal with a single form/view.  ME does expose a child dataform very sweetly rendered over the top of the parent, which is nice (really nice - RIA nice), but still really a single parent form.  I have found no explanation of how to handle one model and possible multiple Views and Model Views.  I may be completely misunderstanding how M-V-MV works properly, but should the M-V-MV (not forgetting persistence managers as well) be expanded to M - V(n) - MV(n)????  Please forgive me if I didn't explain myself properly there ( I am a novice on this, and live in the driest state in the driest continent in the world so brain dehydration is an issue).  Perhaps this post by DocScooter also questions this http://www.ideablade.com/forum/forum_posts.asp?TID=1178 but something in an example app would be great.
    
5. WPF in WinClient - While not strictly to do with DFSilverlight  build, I've noticed through your developer manuals that you discuss WPF but there are no examples.  I imagine the WinForms wizard does not work to drop bound controls onto the canvas.

I appreciate in all of the above that it's not IB role to explain SL or WPF in any depth, but some examples of multi-form (2-3 max) , role-based security apps that handles navigation between forms, and shows related entities via bindable drop down lists would be extremely helpful.  If IB could even generate the Admin objects UI pages that would be super stella.!!!

Apologies that this post contains too many points, and is long.  It is a summary of all I've found with current information and issues I'm tackling about how to do what next.  Happy to provide more explanation if needed.