Microsoft’s Data Access Strategy

re: Microsoft’s Data Access Strategy

David — Sun, 29 Apr 2007 11:40:20 GMT

Again, you post a loooong blog article that clearly breaks the news that the entity framework is cut from Orcas. And yet, where is it written in the post? You attempt to hide that news in lots of talk about strategy and then mention in a half sentence that ADO.NET Entity Framework will ship as an add on in 2008. Not ONE sentence in the whole piece that the news that made you write this article is that the feature is cut from Orcas.

This hopeless attempt to spin the story reminds me all over about WinFS. There were lots of time shifts with WinFS. Every single one was painted as "strategic", and all the blog articles attempted to paint a rosy picture about these shifts. Why do you try that?!? I am just lost, just put up an honest blog article saying "Sorry, we couldn't finish the UI for the entity mapping, therefore ADO.NET Entity Framework is cut from Orcas. We are not happy about that ourselve, but that is how things go." That would SOOO much better resonate with us out here and would not bring back these images of a group trying to paint a pritty picture when in reality their schedule was falling apart. Trying to spin gives outsiders the impression that there is more bad news than what is really anounced. In this case, I get the impression that there is more bad news than the not-finishing-of-the-mapping-UI that you actually anounced today, given the track record of the WinFS anouncements.

Data Access Strategy

Paul Mooney — Sun, 29 Apr 2007 15:40:28 GMT

ADO.NET Entity Framework UpdateRight on the heals of the .NET Framework 3.5 Beta 1 release comes...

re: Microsoft’s Data Access Strategy

Douglas — Sun, 29 Apr 2007 15:50:40 GMT

Or better yet. just state that Entity spaces ship vehicle has changed from Orcas to Katmai.

Douglas

ADO.NET Entity Framework not in Orcas

Linq in Action News — Sun, 29 Apr 2007 16:24:16 GMT

Microsoft has just announced that the ADO.NET Entity Framework will not be shipped with Orcas (Visual

ADO.NET Entity Framework not in Orcas

Fabrice's weblog — Sun, 29 Apr 2007 16:25:31 GMT

Microsoft has just announced that the ADO.NET Entity Framework will not be shipped with Orcas (Visual

ADO.NET Entity Framework Delayed

Paul Gielens:ThoughtsService — Sun, 29 Apr 2007 16:46:32 GMT

Today the ADO.NET team announced that the ADO.NET Entity Framework will not ship with Visual Studio Orcas

re: Microsoft’s Data Access Strategy

Udi Dahan - The Software Simplist — Sun, 29 Apr 2007 17:33:36 GMT

Now that you've got some time until the official release, any chance that you can better support the Domain Model pattern (http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/) without requiring us to do our own change-tracking, etc?

re: Microsoft’s Data Access Strategy

David — Sun, 29 Apr 2007 18:22:57 GMT

Frankly no one cares about the entity framework bs. Linq is the big deal.

del Linq2Entities.*

Claudio Brotto — Sun, 29 Apr 2007 18:32:34 GMT

Così si dice ... TheEntityFramework® non sarà riasciato con Orcas. Il titolo di questo post è volutamente

"LINQ to Entity" and "ADO.NET Entity Framework"

Mehran Nikoo's Notes — Mon, 30 Apr 2007 11:16:07 GMT

If you are interested in the Entity Data Model and want to know more about Microsoft's Data Access

LINQ and the Entity Framework - Announcement

Mike Taulty's Blog — Mon, 30 Apr 2007 11:31:12 GMT

There's an announcement over on the Data Access Team's blog about the ADO.NET Entity Framework. In a...

re: Microsoft’s Data Access Strategy

David Hearn — Mon, 30 Apr 2007 12:00:26 GMT

So this appears to confirm the expected but not widely stated assumption that Orcas will ship in late 2007 as "A few months after the shipment of Orcas, and within the first half of 2008, Microsoft will release the ADO.NET Entity Framework as an extension to the Orcas version of the .NET Framework."

re: Microsoft’s Data Access Strategy

wph101larrya — Mon, 30 Apr 2007 21:01:21 GMT

I am the chief cook and bottler washer at my company. I really don’t care who takes credit for what. I am interested only in how to best make money and provide the best product I can. Furthermore I don’t care about what other companies are doing because we are a Microsoft only house. That said, I need to know NOW the coupling (if any is or is planned) between eSQL, Linq, and WCF/SOA. I have not seen a word where these technologies espoused by Microsoft/Windows and Microsoft/SQL Server mesh. Will they? Do they? Please some one at least comment how Linq/eSQL is going to reach across the great WCF divide to understand database hidden on the other side.

If that is not possible then eSQL seems to be a waste of my time. Even eSQL is woven into VS 200X I see little advantage because I am still having to build all the coupling in the backend. Where is the gain? This is not a rant it is a real request for some simple guidance. Right now our company has a code generator built on the Enterprise Library that models our databases and generates the classes on both sides of WCF all the way up to some specialized custom controls. We are looking at the next version being a WPF/WCF model and trying to lessen the cost of maintenance/new product development.

So where is the gain? Make some sense of all this.

Larry Aultman

re: Microsoft’s Data Access Strategy

Dumbfounded Customer — Mon, 30 Apr 2007 23:25:13 GMT

I have faithfully followed Microsofts efforts to tackle the ORM problem for quit some time now (downloaded the original ObjectSpaces "beta"). This is a very important\expensive problem for your customers. I have never seen a company falter so badly in one area as you guys have. I will certainly hear from folks within my own company bringing this up as I've been preaching for folks to wait for Orcas on some of our data related arch decisions. After ObjectSpaces, WinFS, dropping Linq from VS 2005, and now this...Let's just say that you guys are losing alot of creditability with alot of folks in the industry who have supported you for a while. Sorry, no other way to put this.

re: Microsoft’s Data Access Strategy

Frans Bouma — Tue, 01 May 2007 11:16:48 GMT

@ dumbfounded: if you wait for Orcas to use O/R mapping, I don't understand you. There are several mature O/R mappers out there for .NET for quite some time now, systems which can give you the benefits TODAY, without waiting yet another year.

But of course, it's your time and money :)

re: Microsoft’s Data Access Strategy

Dumbfounded Customer — Tue, 01 May 2007 17:34:15 GMT

Frans,

I think you have something there. Sometimes it's hard to get your company to deviate from what comes out of the MSDN subscription. Mine is a bit reluctant to buy into yet another vendor. We're starting to discuss the possibility now though.

Travis

re: Microsoft’s Data Access Strategy

Velu Sankaralingam — Tue, 01 May 2007 21:46:06 GMT

BEA Aqualogic Data Services Platform has already all of these 'Universal Data Access' features. I think Microsoft is still lagging behind BEA at least couple of years in this area.

re: Microsoft’s Data Access Strategy

courtney — Tue, 01 May 2007 21:46:42 GMT

Frans is right. There are many mature products on the market today and MS would be better off purchasing or licensing such a product to get in the game.

re: Microsoft’s Data Access Strategy

Colin Jack — Wed, 02 May 2007 12:04:27 GMT

I agree with Udi Dahan, its vital that we can apply the domain model pattern.

re: Microsoft’s Data Access Strategy

boris — Wed, 02 May 2007 16:10:48 GMT

Microsoft's "data strategy" has been nothing than a big joke for many years now... or... wait! It has been more than a joke, I must admit - it's been an antipattern.

re: Microsoft’s Data Access Strategy

Ross — Wed, 02 May 2007 21:17:07 GMT

Dumbfounded,

Frans is obviously too polite (or modest) to say, but he has a solution that is well worth spending some of your time reviewing (http://www.llblgen.com/defaultgeneric.aspx). There is a demo at that page, and it has very wide support for various DB vendors. Don't wait for Microsoft to give you half of what others are offering today. There should be a definite business case for buying something that will make you more productive today rather than in 12 months time.

Better still it isn't really even that expensive ....

-Ross.

re: Microsoft’s Data Access Strategy

bmk — Thu, 03 May 2007 16:02:21 GMT

what a pity for you .net developer and microsoft follower i have been doing for years till i realize that i am loosing my time and money on the microsft platform. come to the java world you will get them all now for free. stop paying so much MS$. you will see they will take you seriously

ADO.NET Entity Framework 將不內建於 .NET Framework 3.5 中

Tom Lee's blog — Fri, 04 May 2007 08:56:36 GMT

2007年2月28日，Microsoft 負責資料處理技術之架構師 Mike Pizzo 於他的 blog 中透露了目前 ADO.NET Entity Framework 最新現況。Mike Pizzo

re: Microsoft’s Data Access Strategy

Alex — Sun, 06 May 2007 15:48:03 GMT

This is not surprising. I develop database-driven solutions for so many years in my country, Hungary. I used Borland tools for these applications and they gave me THE feeling of freedom, speed, simplicity in all the way. After these years I tried the Microsoft way, 'cause it is the future, that was said. I dig into the deep of their solutions, tried them so many ways - of course the appropriate solution for every tasks, recommended by the gurus, and MS itself - , but I returned to Borland so happily. MS didn't give me speed, independence, freedom, simplicity. I need them, sorry. I am obsessed of speed.

I think Microsoft has fallen into its own pit. Tried so hard to be the best of IT's all areas, but it is very hard. Their APIs change with speed of light. No one can follow these changes. Clients want rock solid solutions with amazing speed, reliability, consistence, and performance with stability for a long time. These are the cornerstones of all successful enterprises. .Net cannot provide these requirements. I think MS doesn't have Data Access Strategy. This is all about money and business. This is my and so many disappointed developers' opinion based on negative experiences.

re: Microsoft’s Data Access Strategy

Jacky Lee — Tue, 08 May 2007 02:45:43 GMT

What's the difference between LINQ and Jasper?

They're more or less the same, aren't they?

ADO.NET Entity Framework Update

Wriju's BLOG — Fri, 11 May 2007 17:24:59 GMT

Microsoft decided to launch ADO.NET Entity Framework and Tools during the first half of 2008 as an update

Where are the Microsoft fanboys?

CodeClimber — Sun, 20 May 2007 06:57:57 GMT

Where are the Microsoft fanboys?

re: Microsoft’s Data Access Strategy

oagostinho — Tue, 22 May 2007 18:23:06 GMT

Strategy? or Anti-strategy...!!

What does it means, anyway? I know that strategy give you some kind of differentation from rest of us, but in this case. I don't think so!

May be, Michael Potter, give you some hand! ;-)

Anyway, for me, The really Microsoft’s Data Access Strategy will be integrated framework that are in the internet, inside of .net CLR (Nhibernate, ibatis .net, etc) and, that, it's really powerful.

This strategy, work like some kind of extension of .net framework.

Why Not? Think about it? Imagine, any Data Access Framework that implements, some interfaces of .net framework could integrated with .net.

Thinks like .net provider but with the eyes of Data Access.

Orlando Agostinho

Lisbon/Portugal

re: Microsoft’s Data Access Strategy

wlagraba — Wed, 30 May 2007 12:24:17 GMT

I have a feature request for LINQ to Entities. Please add composability of ObjectQuery upon ObjectQuery, just like IQueryable upon IQueryable. I need to be able to extend the final query (that goes to the database) using LINQ to Entities.

Following is an example of what I'm talking about.

If I have the following tables:

Orders and OrderDetails

I can define a LINQ to SQL query like this

var qry = from r1 in db.Orders

from r2 in db.OrderDetails

where r1.orderid == r2.orderid

select r1.orderid;

But also can define the following extension query in a partial class

that has the same name as the DataContext. This way this new method becomes an extension to the model and looks just as natural as the other tables with the exception that is a method and not a property:

public partial class Northwind

{

public IQueryable<Orders> ValidOrders( System.DateTime pFrom, System.DateTime pThrough )

{

return from row in this.Orders

where orderdate >= pFrom

&& orderdate <= pThrough

select row;

}

and I can use it as a table in a query:

var qry = from r1 in db.ValidOrders( DateTime.Parse("1/1/2006"), DateTime.Parse("12/31/2006") )

from r2 in db.OrderDetails

where r1.orderid == r2.orderid

select r1.orderid;

I can NOT do that with Entities and I really think this is necessary to create tables that enforce business logic and simplify programming like Views, but that are not subjected to the same restrictions (i.e. View of a join of multiple tables that accepts INSERT).

ADO.NET Entity Framework 將不內建於 .NET Framework 3.5 正式版中

外部部落格 — Fri, 20 Jul 2007 05:32:27 GMT

2007年4月28日，Microsoft 負責資料處理技術之架構師 Mike Pizzo 於他的 blog 中透露了目前 ADO.NET Entity Framework 最新現況。Mike Pizzo

Did I fail to answer your question during my VS2008 for Web Developers webcast?

Public Sector Developer Weblog — Thu, 26 Jul 2007 19:28:42 GMT

I just reviewed the questions log from the webcast. It appears that some of the questions that were in

re: Microsoft’s Data Access Strategy

pcsql — Fri, 07 Sep 2007 01:06:40 GMT

I'm interested to know more about the migration plan mentioned in this paragraph:

Microsoft is defining a migration plan for customers that start with LINQ to SQL and require additional functionality, such as richer mapping capabilities or access to other stores, to migrate to the ADO.NET Entity Framework.

Where can I find more information about it?

Next-Generation Data Access

Cristian's Blog — Wed, 03 Oct 2007 11:08:23 GMT

SQL Server 2008 is at the door and the same stands for Visual Studio 2008. The data access strategy is

Что будет дальше

Nodir Turakulov — Thu, 25 Oct 2007 12:38:39 GMT

И так до конца февраля (намеченная дата релиза) мы планируем сделать следующее:

LINQ Resources

Ahmed Salijee — Mon, 05 Nov 2007 12:44:41 GMT

At TechED, I promised to post a set of resources at my LINQ session. This post is a bit overdue due to

re: Microsoft’s Data Access Strategy

Pablo — Thu, 08 Nov 2007 04:21:04 GMT

Mike, I really appreciate your post and honestity. Also, it clarified me as I was confused between Linq to Sql and Entity Framework. I also appreciate if you have some link which shows what you are saying in a comparison chart.

Also, I appreciate if you could confirm when Entity Framework will be released as well as the tools for VS 2008. I also understand that it will support Sql2008, wont it? thanks

Pablo.

re: Microsoft’s Data Access Strategy

Mark Gordon — Thu, 10 Jan 2008 23:56:44 GMT

Your data access strategy in .BLOAT sucks ... He is a thought implement a language that does a great job accessing data into .BLOAT .... It is called Visual FoxPro ... Wait a minute that would make sense ... You guys are trying to reinvent a wheel you already own the source code to. Are you guys at Microsoft really that brain dead !!!

Prove it yourself write a .BLOAT database application and a VFP database application then determine which has the fewest lines of code and performs better... VFP will win hands down....

I WISH THERE WAS AN INDUSTRY ACCEPTED ALTERNATIVE TO MICROSOFT. Monopolies SUCK!

ADO.NET Entity Framework dropped from "Orcas"/.NET 3.5

dave^2=-1 — Fri, 01 Feb 2008 13:53:59 GMT

Microsoft has dropped the Entity Framework , which includes LINQ for Entities, from the .NET 3.5 and

ADO.NET Entity Framework Tutorials

Sameh Samir — Sun, 18 May 2008 02:11:25 GMT

These days I'm so concerned about ADO.NET Entity Framework and ADO.NET Data Services (Project Astoria

re: Microsoft’s Data Access Strategy

david — Mon, 16 Jun 2008 23:28:59 GMT

We Need "CHANGE WE CAN BELIEVE IN".

LINQ To SQL: More Useful Than You'd Think

All Your Base Are Belong To Us — Tue, 01 Jul 2008 20:57:09 GMT

Concurrently with the finalization of the initial LINQ release bits, community previews of complementary

Showing some support for LINQ to SQL

Ian Cooper [MVP] — Wed, 02 Jul 2008 16:01:54 GMT

While I have finished my series on LINQ to SQL I wanted to talk about some of the reaction. In his summary

Showing some support for LINQ to SQL

Community Blogs — Wed, 02 Jul 2008 22:39:27 GMT

While I have finished my series on LINQ to SQL I wanted to talk about some of the reaction. In his summary

re: Microsoft’s Data Access Strategy

Donna — Mon, 14 Jul 2008 08:52:57 GMT

Are we "within the first half of 2008" yet?

In which "first half of 2008" will the Entity Framework be released?

re: Microsoft’s Data Access Strategy

Donna — Sun, 17 Aug 2008 03:46:54 GMT

Just read "the petition". I thought I was confused before in which direction to turn for data access in my n-layer apps, now the EF appears to have a pretty negative light on it.

What's Microsoft's standpoint on this? I haven't found a response to this petition.

re: Microsoft’s Data Access Strategy

efactor — Sat, 10 Jan 2009 12:03:33 GMT

Is MS Strategic vision are so dependent on customers? Though I am sure it might give a lot benefits to customers but what about developers? Don't you guys think that you are making a developer's life more miserable by coming up with new framework revision every six months or so and some new buzzwords like LINQ and ADO.NET Entiti Framework? What are your take on this? Huh, like I had made the biggest mistake of my life by choosing Microsoft Platform. Now unfortunately MS didn't left any option for me other than saying that Java is far more superior, simpler and sustainable platform than MS.NET Framework. At least it is much much more stable than .NET Framework.

re: Microsoft’s Data Access Strategy

John — Tue, 13 Jan 2009 19:24:30 GMT

Software development is a very young field and evolution is part of this. Things change quickly and improvements are being made everyday. If you can't understand this, you can't be a successful developer.

Java is write once and debug everywhere.

Horribly Slow.

Has no development environment that matches Visual Studio.

ADO.NET Entity Framework vs. LINQ to SQL

Sun, 25 Jan 2009 23:48:59 GMT

Lately I have been hearing some junior developers saying “LINQ to SQL is gone and ADO.NET Entity Framework

re: Microsoft’s Data Access Strategy

Anita — Tue, 14 Jul 2009 12:10:59 GMT

Thanks for the post.

it clearly explains the need of using Enity Framework !