Microsoft has answered what they call “Top Ten Questions on Data”, explaining what has happened or it is going to happen to Oslo, ADO.NET Data Services, WCF, LINQ to SQL, T-SQL and other technologies.
LLBLGen Pro is an ORM tool which supports multiple persistence frameworks: LLBLGen Pro Runtime, Entity Framework, NHibernate and LINQ to SQL. Other new features are: support for .NET 4.0, model-first or database-first development mode, model view, project validation.
A new version of the Spring.NET framework, version 1.3, was recently released. InfoQ spoke with Mark Pollack, founder and lead of the Spring.NET project, to learn more about this release and what new capabilities it brings, and also to learn more about the new Spring Integration.NET project.
Recently, a post by Oren Eini (a.k.a. Ayende Raheim) touched off a debate around the respective merits and capabilities of NHibernate and Entity Framework 4.0, two .NET-based Object/Relational Maping frameworks. InfoQ explored this debate in more detail to understand some of the perspectives which were given.
Sadly the terms “ORM” and “performance problems” often travel together. By hiding the underlying SQL from the developers, ORMs can offer a huge productivity boost. Unfortunately they also make it easy to generate ridiculously bad queries without realizing it. And without stored procedures to cross reference, finding the offending code without an ORM-specific profiler can be quite tricky.
Microsoft’s vision for .NET is a wide one. In addition to support for all programming languages, MS wants to bring together all communication frameworks and data storage engines. While WCF is making headway for standardizing communication APIs, their universal data access model Entity Framework is lagging behind. Much is this is due to lack of direct vendor support from companies like Oracle.
Not everything planned for Visual Studio 2010 made it in beta 1. This includes some important features for ORM fans. Entity Framework CTP 1 includes support for Self Tracking Entities, POCO Templates, and support for EDMX-free coding.
Microsoft announced System.Data.OracleClient will be marked obsolete in .NET 4.0 and removed from future releases. OracleClient is the ADO.NET provider for Oracle developed by Microsoft and shipped as part of the .NET FCL. Its absence will be an impediment to future upgrades for the many small projects using this provider for Oracle data access.
The .NET RIA Services team has published their release plan starting with a CTP in July and ending with RTW during the first part of 2010. These dates are not set in concrete since changes may appear due to user feedback.
Entity Framework 4.0 Beta 1 – aka EF V2 - delivered with .NET 4.0 Beta 1 contains a list of important improvements: Customization of Code Generation, Lazy Loading, N-tier Support, POCO Support, DDL Generation, Query Customization and others.
Nigel Ellis, Architect at Microsoft, presented today a detailed overview of the new relational model of Azure SQL Data Service, which was announced a couple of weeks ago on the team's blog. Nigel also demonstrated how SDS could be used by WordPress (a PHP application) via an ODBC driver.
Yesterday, Microsoft released .Net RIA Services which was mostly in stealth mode until now. In his presentation at MIX 09, Nikhil Kothari, explained "n-tier development and architecture is hard and un-natural. Our goal is to bring ASP.NET / RAD style productivity to RIA developmend"
The first version ADO.NET Data Services was originally slipped into a service pack for .NET 3.5. Finding that it did not quite meet customer expectations, another version is on its way.
OpenLink and Firebird have been added to the list of supporters of the Entity Framework by releasing their ADO.NET 3.5 providers.
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.