Note: This post is updated with a frequency that depends on the availability of new articles.
Danny Simmons continues his DPMud series with D3: Building Great Software is a Battle, Don’t Leave Any Assets on the Sidelines of 6/30/2009. His list of assets is:
- Analysis Tools
- Check Constraints in the DB
- Unit Testing Your Brains Out
Matthieu Mezil says T4 for View Generation is “easier to use than EdmGen” and “it allows you to use embedded metadata artifacts” in this 6/29/2009 post, which includes extensive source code.
Julie Lerman reports Oracle Woos Microsoft OracleClient users in this 6/29/2009 post:
Although Oracle has long had an area of it’s website dedicated to it’s .NET provider, ODP.NET, they have recently added a page specifically for users of Microsoft’s soon-to-be deprecated System.Data.OracleClient: ODP.NET for Microsoft OracleClient
I reported in my Entity Framework Beta 3 Available for Download post of 12/6/2007 that:
Christian Shay, Product Manager in the .NET and Windows group at Oracle left this comment to my Future LINQ to SQL Support for Multiple Databases? post on May 31, 2007:
I think Oracle is keeping their level of support secret. But, a clue has just been revealed and apparently, more will be known at TechEd. Oracle is co-presenting a talk called "ADO.NET Entity Framework: Provider Model and Integration with Third-Party Databases" Check it out: http://cshay.blogspot.com/2007_05_01_archive.html.
EF support by Oracle appears to have died immediately after Christian posted his comment.
See also my Entity Framework Updates post of 6/2/2007.
Elisa Flasko’s Entity Framework Provider for Synergy DBMS post of 7/1/2009 links to Synergy.de’s announcement page about the release: Synergex Announces the Release of the Synergy/DE Data Provider for .NET of 6/19/2009.
Rob Conery announced SubSonic 3.0 is Released on 7/3/2009. What’s new in v3.0:
- A nice Linq engine which parses IQueryable “stuff” into SQL (thanks to Matt Warren’s excellent work with the IQToolkit, which we stole mercilessly).
- A templating system which allows you to use ActiveRecord, good old Linq in Linq to SQL style, or whatever floats your boat.
- A SimpleRepository which is just about zero-drag and even builds your database for you
- A brand-new project site that will hopefully answer the question “is SubSonic dead”? Or probably not
- A new docs site that has permanently crushed my ability to type. It’s a wiki so if you feel like being helpful and like SubSonic and want to help… nudge… nudge
LinqMaster shows you How to Create T-SQL CASE Statements With LINQ To SQL in this 6/29/2009 post.
Deborah Kurata attacks the VB’s line continuation character in VS1008 with LINQ to XML literals in the XML Literals: Simplifying Strings post of 7/3/2009 to her new Deborah’s Developer MindScape blog.
Her LINQ: Defining a List of Integers post of the same date simplifies the process with, for instance, Enumerable.Range(1, 9).ToList(). XML Literals: Creating an XML File of 7/2/2009 explains how to do it.
Jim Wooley’s Iterators OR Excuse me waiter theres a goto in my C sharp post of 6/29/2009 begins:
At Codestock '09, I gave my LINQ Internals talk and had a number of people express shock when I showed the underlying implementation of their beloved iterators when looking at the code through Reflector. Let's look first at the C# that we wrote. This is similar to the implementation of LINQ to Object's Where method as shown in the sequence.cs file that's part of the C# Samples.
Eric White’s Querying LINQ to XML Nodes in Reverse Document Order with Better Performance post of 6/24/2009 begins:
Occasionally I need to query LINQ to XML nodes in reverse document order. I’m currently writing some LINQ to XML queries over Open XML documents where I need to select paragraph nodes based on content in the immediately preceding paragraph. However, nodes in LINQ to XML are forward-linked only. We can see evidence of this in the XNode.NodesBeforeSelf and XElement.ElementsBeforeSelf methods – these methods return collections of nodes in document order, not reverse document order. This was by design – LINQ to XML was designed to provide great performance for the vast majority of scenarios with the minimum memory footprint possible. The need to process nodes in reverse document order is rare, so the designers of LINQ to XML decided that it was more important to reduce memory footprint than to allow for good performance in the few scenarios that require processing in reverse document order, and of course it was a good decision. But the need does exist.
No significant new Astoria posts as of 7/4/2009.
Peter Blum’s How Dynamic Data changes how you build web forms detailed post of 7/1/2009 describes how DD enables Separation of Concerns:
ASP.NET Dynamic Data emphasizes “separation of concerns” where business logic is separated from the web form. In addition, the web controls showing and validating data are shared by all web forms, providing a consistent user interface. It internally handles database interaction, so you don’t have to write code to create, read, update, or delete records (often known as “CRUD”).
Scott Hanselman called Peter’s post “fantastic” in a recent Tweet.
David Ebbo’s T4MVC 2.2 update: Routing, Forms, DI container, fixes post of 6/30/2009 is a continuation of these previous MVC with T4 Templates posts: