Browse by Tags
All Tags »
Orcas (RSS)
The sample code that ScottGu showed for LinQDataSource made it look like it should be called LinQToSqlDataSource. After installing Beta2 I took a look at it. It only has design time support for LinQ To SQL, but you can bind it to any LinQ query in the...
I was going to write a blog post on Astoria but Pablo's post says almost everything I was going to say. I fully agree with him, in that there are multiple scenarios where the default implementation will be good enough, and it's much more productive...
Udi replied to my post , I was going to answer in his blog but it was too long. This is not about using DataSets. It's about knowing what happened with an entity. Suppose you want to edit an 'Aggregated Entity', like an Order, with header...
David Simmons explained how the 'disconnected mode' works today in Entity Framework (and as far as I know, that's the way it will work in the Orcas release). Basically, there is no disconnected mode. You can create a context and attach objects...
At last, the ADO.NET v.next bits are public! Read the announcement here . Keep an eye in the ado.net team blog for more information about it. It includes an ASP.NET build provider, so you can drop a xml file with the model definition in App_Code and you...
Pablo Castro re-announced the Entity Framework . The white papers are up again. A lot of people have been referring to the ADO.NET EF as an O/R mapper. And it is. But it's much more than that. The EF lets you design your conceptual model based on updateable...
The new VS for DB Professionals supports generating test data for your data model. For each column, you can specify the Generator you want to use, and you have a bunch of predefined ones (numbers in a range, strings that comply with a regular expression...
It was a good session. I totally buy MS's Data Vision. The most interesting stuff for me is the Entity Framework. At last there will be a conceptual data model that all MS products will share (Reporting, Replication, Analysis Services, ADO.NET). This...
OK, it actually happened. We'll have two mapping technologies in .NET v.next. LinQ for SQL, previously known as DLinQ is the 'simple' mapping technology. LinQ for Entities, will be on top of the new ADO.NET Entity Framework, and will be the 'complex'...
If you are interested in ADO.NET Entity Framework , make sure you attend to the following sessions: DAT101 Microsoft's Data Platform Vision, Dave Campbell (I'm not actually not sure if he'll talk about it in this one, but I guess so). DAT304 Next Generation...
More Posts
Next page »