ADO.NET vNext: The Entity Framework, LINQ and more

re: ADO.NET vNext: The Entity Framework, LINQ and more

Bill — Tue, 20 Jun 2006 15:04:50 GMT

Excellent - Got some fun stuff to work on tonight I guess ;-)

re: ADO.NET vNext: The Entity Framework, LINQ and more

Jonathan Bruce — Tue, 20 Jun 2006 16:30:14 GMT

Pablo - great to see this material up after what was an excellent Tech Ed. I expect your posting and those documents to spawn discussions across the blogosphere :)

re: ADO.NET vNext: The Entity Framework, LINQ and more

NickMalik — Tue, 20 Jun 2006 17:35:05 GMT

One thing that I saw recently in a discussion group that was dealing with the issue: should data sets be used to communicate over a web service... was an argument that went like this: do not use data sets over your web service because there are implied operations that can occur when the dataset gets back to the DAL. A web service should share contract, not class, so implied operations effectively share class.

In the document you link to, you are embedding even more capability in the data objects. Personally, I think this is a plus. However, how would you answer the argument that one should not communicate structures composed by these objects over a web service for fear of breaking a cardinal rule of SOA?

re: ADO.NET vNext: The Entity Framework, LINQ and more

Mike Prilliman — Tue, 20 Jun 2006 20:15:37 GMT

Glad to see that the veil has been lifted (and hope these links stay valid longer than the last ones) ;-)

ADO.NET Entity Framework - It's not just O/R mapping

Andres Aguiar's Weblog — Tue, 20 Jun 2006 21:57:59 GMT

Pablo Castro re-announced the Entity Framework. The white papers are up again.
A lot of people have...

re: ADO.NET vNext: The Entity Framework, LINQ and more

Diego Vega — Wed, 21 Jun 2006 11:48:02 GMT

Pablo, I hope the first video that showed you and your mates will be back soon in Channel 9, so I will be able to see the part that I missed.
Regarding the documentation, I already finished with the overview document. It was a very good read and I think the Entity framework is excellent. Actually, I wish the bits were available so I could use them on a project I am starting right now. Instead we will resort to a clumsy mix of typed datasets and custom entity classes.
Because I cannot play with the bits I can only infer some feedback, mostly from pitfalls of previous technology that would be important to avoid in mapping file of the ADO.NET Entity Framework:
- Current typed datasets don’t scale very well at least at design time. It is about the tools included in Visual Studio. They are not very usable beyond a few datatables.
- Datasets are difficult to share: if you include all your tables in a single xsd file, it and the derivative files become difficult to share among developers of the same team, who need to modify the file very often but usually find it is checked – out but others. If you decide to partition the tables in multiple datasets, then the difficulty is what criteria to use for the partition.
- Very simple schema changes lead to crashes.
- There is no way to logically combine datasets that are distributed in multiple files.
- There is virtually no database engine independence story in typed datasets.
- The formats used in datasets are not open standards.

re: ADO.NET vNext: The Entity Framework, LINQ and more

Justin Magaram — Wed, 21 Jun 2006 19:12:35 GMT

I'm wondering how this new modeling approach compares to Object Role Modeling, of which I am a big fan.

Some hot releases

B# .NET Blog — Thu, 22 Jun 2006 03:44:06 GMT

Rather calm on my blog lately due to a high workload. So, let's give a little overview of some recent...

ADO.NET vNext screencast

Data Access blog — Thu, 22 Jun 2006 05:37:12 GMT

Hi - I'm Shyam Pather, Development Lead&nbsp;on ADO.NET vNext team.
I’m incredibly excited to share...

re: ADO.NET vNext: The Entity Framework, LINQ and more

timmall — Thu, 22 Jun 2006 06:14:12 GMT

On the question of LINQ-Entities and Services...

We are working on infrastructure that allows you to still share schema and contract and have consumer-side generative solutions or forward deployment scenarios if you so desire.

We have a construct known as a changeset which is an interoperable contract for expressing changes to instances of types (which may or may not be entities). We also have plans for attaching and dettaching to an ObjectContext so that we can facilitate conversational interaction with stateless services built on top of our stack.

The current planned work around services will not be in our first CTP but we want to make sure that we have a meaningful, interoperable story for both EDM aware and heterogeneous consumers of services from our stack when we release. We will make more details on this effort available in due course.

Tim Mallalieu
Program Manager
Data Programmability Team
blogs.msdn.com/timmall

LINQ, ADO.NET and Entities

Alex Barnett blog — Thu, 22 Jun 2006 07:49:39 GMT

In case you missed it, Somasegar (Microsoft's VP of Developer Division) blogged today about some of the...

Round up of some post TechEd links I've found

the roarty blog — Thu, 22 Jun 2006 09:08:25 GMT

Just some stuff I've noticed floating about and I think is worthy of note:

Pablo Castro points to...

ADO.NET, LINQ, and the Entity Framework Oh My!

Federal Developer Weblog — Thu, 22 Jun 2006 18:31:36 GMT

If you write database applications using ADO.NET (which means almost everyone is still reading this),...

re: ADO.NET vNext: The Entity Framework, LINQ and more

Dennis — Fri, 23 Jun 2006 12:48:54 GMT

I really like the automatic joins. And i also like the EDM.
But how is this different from Typed DataSets? Are we going to get yet more generated files that we can't change?
Can we only map to tables and not Stored Procedures?
Will mapping be supported only by XML-files, of maybe also by Custom Attributes?

re: ADO.NET vNext: The Entity Framework, LINQ and more

bill xie — Fri, 23 Jun 2006 20:45:36 GMT

Seems that Microsoft is attempting to introduce several new query languages to resolve impedance between SQL and Object. But I really doubt that it will become success.

1. Can these new query languages fully replace T-SQL? Otherwise, developers have to use T-SQL, so why they bother to learn a new language? I suggest that incorporate more support in design tools to fully enable T-SQL for developers.

2. Entity modeling could fully replace relational modeling? Describing relationship could bring developers additional efforts. For simple applications they will not choose such complex method. For complex application they would choose to stay with relational modeling.

3. Enterprise application would exptect more disciplinary than languge-level flexibility.

ADO.NET vNext - feedback so far

Data Access blog — Sat, 24 Jun 2006 07:50:10 GMT

Since announcing our ADO.NET vNext plans at TechEd last week, the team has been on the lookout for your...

ADO.NET vNext: The Entity Framework, LINQ and more

ADO.NET team blog — Tue, 11 Jul 2006 20:31:12 GMT

(this post&nbsp;was originally posted here)
Once you are done with shipping large products such as SQL...

ADO.NET vNext - feedback so far

ADO.NET team blog — Tue, 11 Jul 2006 20:34:14 GMT

(this post&nbsp;was originally posted here)

Since announcing our ADO.NET vNext plans at TechEd
...

ADO.NET vNext CTP available

Klaus Aschenbrenner - A life between bits & bytes — Wed, 16 Aug 2006 23:30:26 GMT

Today Microsoft has released the first CTP of ADO.NET vNext, which is an important milestone in the data...

the ‘bee log » Blog Archive » LINQ & ADO.NET Entities

the ‘bee log » Blog Archive » LINQ & ADO.NET Entities — Thu, 14 Sep 2006 18:52:35 GMT

PingBack from http://laribee.com/blog/2006/09/14/linq-adonet-entities/

Links to LINQ

Charlie Calvert's Community Blog — Thu, 05 Oct 2006 04:38:32 GMT

Here are some useful links to LINQ information. Core Microsoft LINQ Sites · Try it yourself: download

Links to LINQ

Charlie Calvert's Community Blog — Sat, 20 Sep 2008 03:34:45 GMT

Here are some useful links to LINQ information. Use the comments or write me if you want to add to this

Fernando Alencar | LINQ - Refer??ncias

Fernando Alencar | LINQ - Refer??ncias — Thu, 26 Mar 2009 06:13:40 GMT

PingBack from http://www.fernandoalencar.eti.br/archives/105

Data Access blog ADO NET vNext The Entity Framework LINQ and more | Outdoor Ceiling Fans

Sun, 31 May 2009 16:04:23 GMT

PingBack from http://outdoorceilingfansite.info/story.php?id=5151