WPF

<StackPanel ...>
	<ItemsControl  ItemsSource="{Binding RungSurface}"

using System.IO;
using System.Xml;
using System.Xml.Schema;

private void LoadXmlData()
{
    XmlValidatingReader reader    = null;
    XmlTextReader       txtReader = null;
    string              filename  = "myfilename.xml";
    try 
    {
        // Create the validating reader and specify DTD validation.
        txtReader = new XmlTextReader(filename);
        reader = new XmlValidatingReader(txtReader);
        reader.ValidationType = ValidationType.DTD;

        // Set a handler to handle validation errors.
        reader.ValidationEventHandler += eventHandler;

        // Pass the validating reader to the XML document.
        // Validation fails due to an undefined attribute, but the 
        // data is still loaded into the document.
        XmlDocument doc = new XmlDocument();
        doc.Load(reader);

        // do something with doc.OuterXml
    }
    finally 
    {
        if (reader != null) 
        {
            reader.Close();
        }
    }
}

void ValidationCallback(object sender, ValidationEventArgs args ) 
{
    // report the validation error
}

IngoVals wrote:

4) Can you use LINQ entity items with any good results, like perhaps populating the viewmodel with them? It's not proper to keep the context open but having the object itself might help with saving back to database. What happens to a LINQ object when the Context is closed. Do I still have access to it's relative tables an such.

IngoVals wrote:

4) Can you use LINQ entity items with any good results, like perhaps populating the viewmodel with them? It's not proper to keep the context open but having the object itself might help with saving back to database. What happens to a LINQ object when the Context is closed. Do I still have access to it's relative tables an such.

IngoVals wrote:

Would you rather have the child inside the parents viewmodel or seperate but linked?

IngoVals wrote:

3) If many apps are getting the data from the same place, and they can change that data. How do you keep the data current. Do you reload it regulary, use ActiveRecord pattern. I guess this has nothing to do with MVVM but I'm fishing out what people have used alongwith MVVM with good results.

IngoVals wrote:

4) Can you use LINQ entity items with any good results, like perhaps populating the viewmodel with them? It's not proper to keep the context open but having the object itself might help with saving back to database. What happens to a LINQ object when the Context is closed. Do I still have access to it's relative tables an such.

IngoVals wrote:

very often showing objects as lists+details for the selected object (master detail view). However the details between objects can be somewhat different. I guess I could make a abstract ViewModel for their common functionality but what about the Views themselves. It will have the same buttons, the same format showing the list and then the details. Basicly the only difference will be the fields in the detail. I can't make a abstract UserControl (except without the XAML). How to solve this? Using styles, ControlTemplates? Again any examples out there I could check out?