InfoQ Homepage ADO.NET Content on InfoQ
-
MIX 09: Nigel Ellis on Azure SQL Data Services
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.
-
Microsoft Introduces .Net RIA Services
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"
-
Introducing ADO.NET Data Services 1.5
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.
-
New Entity Framework Providers: OpenLink and Firebird
OpenLink and Firebird have been added to the list of supporters of the Entity Framework by releasing their ADO.NET 3.5 providers.
-
IBM’s Data Server Provider for .NET Supports the Entity Framework
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.
-
LINQ to SQL, The Next Step
Despite the numerous problems with Microsoft ORMs and the plethora of alternatives such as LLBLGen, nHibernate, and OpenAccess, many developers are forced to use Microsoft tech because that is why their company or customer wants. And between the two offerings, it seems most developers believe that Entity Framework is not a viable option. So what are they do to?
-
Does LINQ-to-Entities really return different results depending on previous queries?
In a recent blog post Stu Smith claimed that “LINQ-to-Entities will return different results depending on what previous queries you’ve executed!”. If true, this would make using Entity Framework much harder than necessary to use. We talked to Elisa Flasko of the ADO.NET Team to find out what’s really going on.
-
Working Around Entity Framework's Large Data Model Issues
The Entity Framework doesn't support data models with much more than 50 to 100 entities. But since companies typically run everything from one central database, several hundred tables are the norm. Microsoft's ADO.NET team is presenting an article on Working With Large Models In Entity Framework, a list of issues and work-arounds for EF users.
-
Meta-data Synchronization Tools for LINQ to SQL and ADO.NET Entity Framework
The designers in both LINQ to SQL and ADO.NET Entity Framework have a number of limitations. In order to work around these limitations, products such as Huagati DBML/EDMX Tools have been developed. There is no bloat here, everything is a must have for many shops.
-
No Change Tracking for ADO.NET Entity Framework 2010
One of the biggest complaints about ADO.NET Entity Framework was that it did not support change tracking. Despite everything from ADO.NET DataSets to every single non-Microsoft ORM having support for this out of the box, Microsoft has no intention of fixing this in the .NET 4.0/VS 2010 timeframe.
-
ADO.NET Data Services Is About to Go Offline
ADO.NET Data Services, previously known as Project Astoria, will receive offline capabilities in the near future. That means applications could be developed to synchronize their data, then use it in an offline fashion.
-
Is LINQ to SQL Truly Dead?
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.
-
Table-Valued Parameters in SQL Server
Table-valued parameters are a new feature introduced in SQL Server 2008. They provide a built-in way to send multiple rows of data from a client application to SQL Server in a single parameterized SQL statement.
-
Is Database-as-a-Service a Bad Idea?
Data Management represents a strategic asset for Cloud Platforms as the most popular Data Services will likely command the largest platform market share. In a post this week, Arnon Rotem-gal-Oz argues that "Database-as-a-Service" is a bad idea. Would you trust your enterprise data to DaaS?
-
Occasionally Connected Client Support With VS 2008 SP1
Visual Studio 2008 SP1 provides increased support for occasionally connected clients through an enhanced DataSet designer, integrating ADO.NET Sync Services and SQL Server 2008 Change Data Capture.