From what I gather about your application your plan seems the right thing to start with.
1. MVVM is the way to go. IMO it is important to distinguish the code that is purely View-related and not part of the business logic or the ViewModel. Often this code is hard to include in the ViewModel and should be left in the code-behind of the View.
2. MEF can compose almost anything but the granularity of composition is important. IMO parts of the application should not be composed unless necessary. Composing large parts of the application seems like a good start.
- We are currently working for the DomainService support for OpenAccess. Indeed it is not available yet but it is expected with one of the coming Service Packs. Unfortunately I cannot pinpoint an exact date about the release.
Yes, I agree that IoC may be unnecessary in many cases and it depends on the size of the application as well. Can you link to the article where you read this about IoC and MVVM? It will be interesting to see the points made there.
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items.