Note: This post is updated daily or more frequently, depending on the availability of new articles.
Danny Simmons describes associations between Room and Exit entities in his D3: Modeling Part 1 – Real-World Relationships post of 2/18/2009 for his DPMud multi-user dungeon application that uses an EDM as its data source.
Julie Lerman’s Logging Entity Framework Queries to Look for Perf Improvement Opportunities post of 2/16/2009 discusses using ObjectQuery.ToTraceString, SQL Profiler, and the eSqlBlast tool on Code Gallery to validate the T-SQL that EF sends to SQL Server.
She also offers a copy of The Acknowledgements from her book.
Doug Purdy’s “M”ix09 (Using “M” to write REST services and clients) post of 2/11/2009 includes the following diagram of “Oslo” Development Domains, which includes the Entity Editor and MEntity textual DSL (empahsis added):
See the entry for Doug’s post in the ADO.NET Data Services (Astoria) section for more details about the MIX09 session named DEVELOPING RESTFUL SERVICES AND CLIENTS WITH “M”.
David Hayden’s updated LINQ To SQL and Executing ADO.NET Commands - O/R Mappers post of 2/16/2009 compares using LINQ to SQL with SqlClient.SqlConnection and .ExecuteNonClient for parameterized INSERT operations and concludes: “Using LINQ To SQL is much simpler by far.”
Rhys Parry’s LINQ and Deferred Execution post of 2/17/2009 is yet another exposé of issues with LINQ well-known deferred execution feature. Rhys’s earlier LINQ-related posts are LINQ and Extension methods (2/15/2009) and Getting Started with LINQ (2/13/2009).
Eric White explores The Composability Thought Process for LINQ on 2/17/2009 with a pointer to his earlier Finding Paragraphs by Style Name or Content in an Open XML Word Processing Document post that incrementally develops the subject query.
Dmitry Robsman’s Channel 9 Interview: ASP.NET MVC using Visual Basic XML Literals shows how he implemented ASP.NET MVC views using Visual Basic's XML Literals instead of .aspx pages. (2/16/2009, Thanks to Beth Massi.)
Doug Purdy’s “M”ix09 (Using “M” to write REST services and clients) post of 2/11/2009 announces that the “Oslo” team will use MIX09 to:
[U]nveil how “Oslo”/”M” can be used to build RESTful client and services using domain specific models and languages.
The net result is that RESTful clients and services are much easier to write, understand, maintain, etc.
Doug describes what appears to be a session named DEVELOPING RESTFUL SERVICES AND CLIENTS WITH “M”:
Learn how Web developers can use “M”, a new language for describing data, metadata and domain specific languages to enhance RESTful services like HTTP, JSON, RSS/Atom, and more. Also see how “M” can be used on premise or in the cloud to achieve greater development productivity and to create more compelling customer experiences. [Emphasis added.]
I’m surprised that Doug didn’t mention Astoria in his post.
This topic moved on 1/3/2009 to Windows Azure and Cloud Computing Posts for 1/5/2009+.
This topic was dropped as of 1/3/2009.
Shawn Wildermuth announces that Prism Now Supports Silverlight 2! on 2/18/2009. Prism is a codename for new WPF guidance for the patterns&practices group’s Composite Application Block.
Steve Martin’s Higher Standards for Web Standards post of 2/16/2009 discusses Microsoft’s reluctance to join the IBM-sponsored Web Services Test Forum. Steve writes:]
In many cases, the right answer isn’t necessarily to define something new, but to instead carefully consider whether technology or initiatives already exist to solve the problem. In the end, we should judge the strength of standards on industry and customer adoption alone. As an example, IBM recently announced a consortium called “WSTF”: Web Services Test Forum which leaves us a tad puzzled.
As of today, the WS-* standards are largely complete within W3C, OASIS, WS-I, DMTF, etc. and are widely implemented in infrastructure products and used by organizations all over the world. We were thrilled to participate in the Oasis announcement just last week on WS-RX, WS-TX and WS-SX. With regard to testing, we think it is critical that customers be able to propose scenarios that match their real-world interoperability needs. Equally important - both successes and failures must be made public. This is why we’re still evaluating our participation in WSTF.
Steve mentions the Web Services Interoperability (WS-I) organization, which has been very quiet lately, but mentions:
Greg Leake runs one of the largest interoperability labs in the world and publishes results and guidance on WS* / WebSpehere / .NET interop. Stay tuned for more here – Greg is just completing his work on WebSphere 7.