NHibernate Linq 1.0 has been released. Based on the stable provider from NHibernate Contrib, NHibernate Linq 1.0 is a LINQ provider that supports most operations available through the NHibernate criteria query API.
LINQ to XSD is the long awaited follow-up to LINQ to XML. Its primary purpose is to produce LINQ-compatible object models from XSD files, giving developers some measure of static type checking while accessing XML data.
Damien Guard of Microsoft’s Data Programmability has posted a rather long list of the changes to LINQ to SQL. While they are still committed to Entity Framework over the long run, this will do much to alleviate the fear LINQ to SQL will be completely neglected in the mean time.
Ed Essey, a Program Manager on the Microsoft Parallel Computing team, wrote on the latest enhancements to PLINQ that are to appear in .NET 4.0 Beta 1 that is to be released soon. Some of them are: “With” Operators Pattern, Execution Mode, Cancellation, Refactoring, Performance Improvements.
Mehfuz Hossain, a Microsoft MVP, has created a LINQ-to-Twitter provider. This is yet another example demonstrating that LINQ is not a framework to access just data in a database but it can be used with all sorts of objects, including tweets.
In this interview made during QCon SF 2008, Erik Meijer talks about less known LINQ features, like the ability to do meta programming or the fact that LINQ works against any data collection that implements the sequence operators. Meijer also talks about the differences between functional languages and objectual ones, asynchronous computation, and the evolution of languages.
LINQPad is a free standalone LINQ interpreter and code snippet IDE. In addition to being a great LINQ learning tool, LINQPad also provides interactive querying of SQL databases using LINQ expressions in C# or VB.NET, allowing developers to use LINQ expertise to perform ad-hoc database queries.
IBM has released the production version of its Data Server Provider for .NET including support for Microsoft’s Entity Framework allowing its users to create EDM schemas, and to execute EntitySQL and LINQ statements.
The biggest feature of C# 3 was LINQ technology. With C# 4, it looks like dynamic typing is going to steal the show. But can you use them together?
Back in July we reported that LINQ to SQL was transferred to the SQL Data Programmability team. This event raised a lot of concern in the developer community, who worried that work on LINQ to SQL would halt in favor of ADO.NET Entity Framework. A recent announcement by Tim Mallalieu, Program Manager of both LINQ to SQL and Entity Framework, has exacerbated those concerns.
Microsoft is planning on releasing a wide variety of parallel programming libraries with .NET 4. These include Parallel LINQ (PLINQ), Structured Parallelism (Parallel.For), the Task Parallel Library, and the Coordination Data Structures.
NHibernate 2.0 was made official with the announcement of its general availability by Ayende Rahien. The announcement follows months of alphas and release candidates and now matches the features of Hibernate 3.2.
Recently we announced that Mono achieved full C# 3 support. Along with that comes support for Parallel LINQ. Parallel LINQ, part of Microsoft’s Parallel Extensions library, allows developers to quickly make queries execute across multiple threads.
More and more, LINQ to SQL is being seen as a temporary solution. With the impending release of ADO.NET Entity Framework, a lot of people are worried that development on LINQ to SQL will fall by the wayside. With Microsoft's long history of developing and discarding database access technologies, these concerns are not without merit. So this raises the question, "Should LINQ to SQL Go Open Source?"