It starts good with a presentation of Scott Guthrie about the new stuff in ASP.NET 2.0. Nothing really new for me because I am testing the product since some times now. But interesting new details. Then I followed with soemthing that I have not that deep knowhow: Winforms, a presentation from Joe Stegman. Really, really impresive. The next one was about ADO.NET and guess what that also have made some great development in that field. I can't tell you more cause I am under NDA, but stay tuned they are doing a great job.

Then we made some shopping, a visit to the Microsoft museum and went back to the presentation of Don Box.

What a long trip to Seattle - Washington. Richard Clark had some beers !!!! Hey Richard take care in Denmark (place where we stopped) the beer are 75 cl.

Thats a summary of the article from Dare Obasanjo on MSDN. <h4>Classes with Fields or Properties that Hold XML</h4>If a class has a field or property that is an XML document or fragment, it should provide mechanisms for manipulating the property as both a string and as an <b>XmlReader</b>. <h4>Methods that Accept XML Input or Return XML as Output</h4>Methods that accept or return XML should favor returning <b>XmlReader</b> or <b>XPathNavigator</b> unless the user is expected to be able to edit the XML data, in which case <b>XmlDocument</b> should be used. <h4>Converting an Object to XML</h4>If an object wants to provide an XML representation of itself for serialization purposes, then it should use the <b>XmlWriter</b> if it needs more control of the XML serialization process than is provided by the <b>XmlSerializer</b>. If the object wants to provide an XML representation of itself that enables it to participate fully as a member of the XML world, such as allow XPath queries or XSLT transformations over the object, then it should implement the <b>IXPathNavigable</b> interface.