http://blogs.microsoft.co.il/blogs/bursteg/archive/2009/03/20/download-mix09-sessions-and-watch-offline.aspx
Namoskar!!!
Are available at http://sessions.visitmix.com/MIX09/
Please find it http://go.microsoft.com/fwlink/?LinkId=144444
Hurray!!! We have it finally!!!!
We have added 50 new features. It can run Silverlight video in non-browser environment. 60+ new highly customizable controls with source code are available.
Rich Internet Application is just a matter of choice. Be smart and have Silverlight 3.
Tools For You
For more watch out www.silverlight.net or http://silverlight.net/getstarted/silverlight3/default.aspx
I have seen the Key Note through http://live.visitmix.com/
Watch it out now at http://live.visitmix.com/
I have been getting a continuous request on what we should be using? LINQ to SQL or ADO.NET Entity Framework? I have posted few articles on that, please feel free to visit
Choosing between ADO.NET Entity Framework and LINQ to SQL
Choosing between LINQ to SQL and Entity Framework
ADO.NET Entity Framework Resources
ADO.NET Data Services (Astoria) Resources
Introducing the Azure™ Services Platform
Using computers in the cloud can make lots of sense. Rather than buying and maintaining your own machines, why not exploit the acres of Internet-accessible servers on offer today? Get an early look into the Azure Services Platform in this White Paper by David Chappell.
An Introduction to Microsoft .NET Services for Developers
This overview paper introduces Microsoft® .NET Services, each of its building block services, and how they fit together.
A Developer’s Guide to the Microsoft® .NET Access Control Service
This whitepaper shows developers how to use a claims-based identity model and the Microsoft® .NET Access Control Service – part of the Microsoft® .NET Services family – to implement single sign-on, federated identity, and role based access control in Web applications and services.
A Developer’s Guide to the Microsoft® .NET Service Bus
This whitepaper shows developers how to use the .NET Service Bus – part of the Microsoft® .NET Services family – to provide a secure, standards-based messaging fabric to connect applications across the Internet.
A Developer’s Guide to the Microsoft® .NET Workflow Service
This whitepaper provides details about the Microsoft® .NET Workflow Service, its relation to Windows Workflow Foundation, and what developers need to know to begin building workflows for the cloud. It not only explains the current tools and capabilities but also outlines the vision for future releases.
Windows Azure Table – Programming Table Storage
Windows Azure Table provides scalable, available, and durable structured storage in the form of tables. The tables contain entities, and the entities contain properties. The tables are scalable to billions of entities and terabytes of data, and may be partitioned across thousands of servers. The tables support ACID transactions over single entities and rich queries over the entire table. Simple and familiar .NET and REST programming interfaces are provided via ADO.NET Data Services. This paper describes these concepts and the advanced features of Windows Azure Table.
Windows Azure Blob – Programming Blob Storage
Windows Azure Storage provides durable, scalable, available, secure, and performance-efficient storage services for the cloud, and it does this through familiar and easy-to-use programming interfaces. Windows Azure Blob provides a simple interface for storing named files along with metadata for a file. This paper describes the Windows Azure Blob programming interface and the advanced blob concepts.
Windows Azure Queue - Programming Queue Storage
Windows Azure Storage provides durable, scalable, available, secure, and performance-efficient storage services for the cloud, and it does this through familiar and easy-to-use programming interfaces. Windows Azure Queue provides reliable storage and delivery of messages for an application. This paper describes the Windows Azure Queue programming interface and the advanced queue concepts.
Compiled Resources
http://www.renaissance.co.il/downloads/Entity%20Framework%20Essential%20Resources.pdf
Articles
Next-Generation Data Access: Making the Conceptual Level Real
http://msdn.microsoft.com/en-us/library/aa730866(VS.80).aspx
The ADO.NET Entity Framework Overview
http://msdn.microsoft.com/en-us/library/aa697427(VS.80).aspx
ADO.NET Tech Preview: Entity Data Model
http://msdn.microsoft.com/en-us/library/aa697428(VS.80).aspx
ADO.NET Entity Framework Overview
http://blogs.msdn.com/adonet/archive/2008/03/27/ado-net-entity-framework-performance-comparison.aspx
Channel9 Videos
ADO.NET Entity Framework on Channel 9
Pablo Castro, Mike Pizzo, and Britt Johnston
http://blogs.msdn.com/adonet/archive/2006/07/19/671805.aspx
Pablo Castro, Britt Johnston, Michael Pizzo: ADO.NET Entity Framework - One Year Later
http://channel9.msdn.com/Showpost.aspx?postid=338257
Other related videos
http://channel9.msdn.com/tags/Entity+Framework/
“How Do I?” Videos — Data Platform Development
http://msdn.microsoft.com/hi-in/data/cc300162(en-us).aspx
MSDN Webcast
Programming LINQ and the ADO.NET Entity Framework (Level 200)
Language Integrated Query (LINQ) introduces an exciting new way for applications to build strongly typed queries that are deeply integrated into the programming language. The ADO.NET Entity Framework allows applications and services to work in terms of an application-oriented Entity Data Model, decoupling the application's data model from the storage considerations of the relational schema. Join this webcast to see how these two technologies work together to change the way applications work with data.
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032364889&culture=en-US
24 Hours of SQL Server 2008: Using the Microsoft Data Platform for Easy Data Access with SQL Server 2008 (Level 100)
Join this series as we look at Microsoft SQL Server 2008 as a productive data platform. Throughout this series, we use Contoso (Container Overseas Shipping Operation) LTD as our scenario customer while we explore the features that make SQL Server 2008 this platform.
MSDN geekSpeak: Julie Lerman on ADO.NET (Level 200)
MSDN geekSpeak is a new kind of webcast series, hosted by Glen Gordon and Susan Wisowaty from the MSDN Events team, that provides a "talk-radio" format where industry experts share their knowledge of and experience with a particular developer technology. In this installment of geekSpeak, Julia Lerman, a Microsoft Most Valuable Professional (MVP), discusses the next version of ADO.NET, which presents a host of new ways to interact with data in your Microsoft .NET applications. Learn how the ADO.NET Entity Framework provides for abstracted access to your data, client views and schemas, and mapping of data to objects. See how you can build queries on the client against your own views and schemas using Entity SQL and Language-Integrated Query (LINQ).
Entity Framework for Database Administrators (Level 200)
The Entity Framework is a new data technology from Microsoft that may particularly interest database administrators (DBAs). Join this webcast to see how this technology can radically change the development of applications from a DBA perspective, and also change access patterns on servers. We discuss these changes and their impact on DBAs and data developers.
Framework Masterclass: LINQ to Entities (Level 200)
In other sessions, we explored how Microsoft .NET Language Integrated Query (LINQ) is used for Structured Query Language (SQL) databases and working with XML. In this webcast, we connect to the data access layer, the business objects that provide the functionality of working with enterprise data. Join us to learn how you can make your LINQ applications really sing when working with entities.
Samples
Entity Framework Beta 3 Samples
http://www.codeplex.com/adonetsamples/Release/ProjectReleases.aspx?ReleaseId=8858
Samples at code.msdn.com
ADO.NET Entity Framework & LINQ to Relational Data
http://code.msdn.microsoft.com/adonetefx
MSDN Forum
ADO.NET Entity Framework and LINQ to Entities
http://forums.microsoft.com/msdn/showforum.aspx?forumid=533&siteid=1
BLOGS
http://blogs.msdn.com/adonet/
As part of my day to job I come across a very common question from the developer community that one should be using LINQ to SQL (L2S) or ADO.NET Entity Framework (EF).
Earlier I have posted a blog containing the features http://blogs.msdn.com/wriju/archive/2009/01/05/choosing-between-linq-to-sql-and-entity-framework.aspx.
To me I feel very excited about EF as it has got more power and capability than L2S. L2S was important for us to understand the new era of Object Relational Model (ORM) with native programming language querying (LINQ) capabilities. But going forward EF is the technology you should be focusing on.
There has been another concern comes from dev community is that is LINQ to SQL going to retire? Answer to that is no. Microsoft will continue to support L2S and enhance based on customer feedback. Tim Mallalieu clearly have mentioned in his Post that Microsoft will heavily invest into EF and the most wanted features like POCO will be with .NET 4.0.
EF is the recommended data access solution while accessing data using LINQ. LINQ to SQL will also be there.
So when the question arises what to choose? Go ahead and plan for Entity Framework. I would like to share some of my thoughts around it,
Why I should use Entity Framework?
Ø It simplifies the data access and allows me to create conceptual model required for my business.
Ø EF allows you to handle Many to Many relationship without extra join.
Ø Map related tables into single entity to reduce code complexity.
Ø Strong inheritance supports for (Table per hierarchy, subclass and concrete type)
Ø Consolidation for complex object is very easy.
Ø It has powerful query mechanism through EntitySQL. For them who do not like LINQ you can use EntityClient provider with EntitySQL.
Ø You can expose your modeled data through ADO.NET Data Services (Astoria).
Ø Database independent and based on standard ADO.NET Providers.
Ø There are many third party providers currently available.
o Devart offers provider for Oracle, MySQL and PostgreSQL
o Phoenix Software Solution offers EF provider for SQLite.
o Npgsql offers another provider for PostgreSQL.
o OpenLink Software offers a very wide range of support for Oracle (versions 7.x to 11.x), Microsoft SQL Server (6.x to 2005), IBM DB2 , Sybase (4.2 to 12.x+), IBM Informix (5.x to 11.x), Ingres (6.4 to 9.x), Progress (7.x to 10.x), MySQL, PostgreSQL, and Firebird
o Sybase SQL Anywhere provides support for SQL Anywhere.
o IBM natively supports databases like DB2, Informix and U2.
Ø <TODO: will add few more as and when come across>
Closing
At the end of the story I still feel good about LINQ to SQL when it comes to smaller applications with less complexity. Entity Framework is capable of handling large enterprise applications and will have more power in v2 (in .NET 4.0). So if you are targeting your application for multiple databases the L2S is not the right choice for you.
My vote is for ADO.NET Entity Framework. You will enjoy with the conceptual model and Astoria.
As you all know Astoria (Data Services) supports anything as backend. Not necessarily you need to have a Relational database to access data.
So if you talk about offline data like collection of an Object which may or may not come from an external entity (like XML) can also be exposed via Astoria.
I was trying to figure it out and a very uncommon error was occurring. Then Phani from Astoria product team helped me to resolve the issue. Thanks Phani.
namespace DataService_Blog
{
/// <summary>
/// Entity Structure
/// </summary>
[DataServiceKey("Id")]
public class Person
//Important that you need to have a property called "ID"
//Or you need to specify the column for DataAccessKey like, [DataServiceKey("Id")]
public int Id { get; set; }
public string Name { get; set; }
public DateTime DOB { get; set; }
}
/// Now you need to get IQueryable
public class FamilyData
List<Person> family = new List<Person>();
public FamilyData()
family = new List<Person>
new Person(){Id = 1, Name = "Debajyoti Ghosh", DOB = new DateTime(1946,1, 1)},
new Person(){Id = 2, Name = "Sumitra Ghosh", DOB = new DateTime(1952,1, 1)},
new Person(){Id = 3, Name = "Wriju Ghosh", DOB = new DateTime(1978,1, 1)},
new Person(){Id = 4, Name = "Writam Ghosh", DOB = new DateTime(1985,1, 1)},
new Person(){Id = 5, Name = "Sasyati Sanyal", DOB = new DateTime(1981,1, 1)},
};
public IQueryable<Person> Family
get
return family.AsQueryable<Person>();
/// Here is your Service
public class DataS : DataService<FamilyData>
public static void InitializeService(IDataServiceConfiguration config)
config.SetEntitySetAccessRule("Family", EntitySetRights.All);
http://msdn.microsoft.com/en-us/library/cc907912.aspx
Overview: ADO.NET Data Services
http://msdn.microsoft.com/en-us/library/cc956153.aspx
ADO.NET Data Services Team Blog
http://blogs.msdn.com/astoriateam/
Phani Raj’s Blog
http://blogs.msdn.com/phaniraj/
Mike’s Podcast
Data Services Forum
http://social.msdn.microsoft.com/forums/en-US/adodotnetdataservices/threads/
How Do I do Videos
How Do I: Getting Started with ADO.NET Data Services over a Relational Database
How Do I: Getting Started with ADO.NET Data Services over a Non-Relational Data Source
How Do I: Consuming an ADO.NET Data Service in a Silverlight Application
How Do I: Consume an ADO.NET Data Service in a .NET Application
MSDN Home Page
http://msdn.microsoft.com/en-us/data/bb931106.aspx
Data services API reference documentation on MSDN
Data Services Futures
Offline-Enabled Data Services and Desktop ApplicationsLearn how to create offline-capable applications that have a local replica of their data, how to synchronize that replica with an online data service when a network connection becomes available, and how replicas can be used with the ADO.NET Entity Framework.
Other MSDN Documention
Simple Addressing Scheme for Data with Uniform URIs (ADO.NET Data Services Framework)
Data Transport Format (ADO.NET Data Services Framework)
Storage Independence (ADO.NET Data Services Framework)
Extensions to Data Services (ADO.NET Data Services Framework)
REST Services and Semantics (ADO.NET Data Services Framework)
Data Service Quick Start (ADO.NET Data Services Framework)
Data Model (ADO.NET Data Services Framework)
Data Service Host (ADO.NET Data Services Framework)
Service Operations and Interceptors (ADO.NET Data Services Framework)
HttpWebRequest GET (ADO.NET Data Services Framework)
HttpWebRequest MERGE (ADO.NET Data Services Framework)
HttpWebRequest POST (ADO.NET Data Services Framework)
HttpWebRequest DELETE (ADO.NET Data Services Framework)
Batch Requests (ADO.NET Data Services Framework)