Published on


Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Talking Points: .NET 3.5 SP1 contains four major feature additions (listed). These new features are aimed at enriching the web development and data programmability spaces. Let’s take a moment to examine each of these new features individually…
  • Talking Points: When we talk about the Entity Framework, we’re actually talking about two things: The Entity Data Model (EDM) The Entity Framework It’s important to delineate the two as separate, but complementing technologies The Entity Framework is a set of services that allow you to consume an EDM from within your applications. Object services is a set of classes that allow you to query an EDM and retrieve your results in the form of strongly-typed CLR objects. Entity Client allows you to query an EDM using a traditional ADO.NET paradigm (EntityConnection, EntityDataReader, etc.) Provides a smooth migration path for developers that are new to the Entity Framework Offers performances benefits due to the lack of object materialization Entity SQL is a SQL-like language that let’s you query your EDM with full control. Unlike SQL, Entity SQL queries the conceptual model, so your queries can be expressed in terms of the way your application sees your model, not how your database is actually shaped. LINQ To Entities sits on top of Object Services and allows you to retrieve strongly-typed objects from your EDM, expressed through familiar LINQ query syntax.The Entity Framework is RDMS agnostic, and numerous database vendors are currently developing providers: Oracle, DB2, MySQL, PostgreSQL, VistaDB, SQLite, Sybase, Informix, etc.
  • Estimated Time: 6 minutesTalking Points: When we talk about the Entity Framework, we’re actually talking about two things: The Entity Data Model (EDM) The Entity Framework It’s important to delineate the two as separate, but complementing technologies The EDM is a set of layers that make up your application’s model, as well as it’s mapping to an underlying data store. Made up of three files: CSDL (Conceptual Schema Definition Language) MSL (Mapping Specification Language) SSDL (Storage Schema Definition Language) This separation of concerns allows great flexibility: Model your application the way you want regardless of the state/structure of its underlying data store Normalize your database as much as you need without worrying about affecting the interface of the application’s object model The EDM represents a re-useable application model that can be leveraged from within many applications/environments and persisted across numerous databases. The Entity Data Model is RDMS agnostic, and numerous database vendors are currently developing providers: Oracle, DB2, MySQL, PostgreSQL, VistaDB, SQLite, Sybase, Informix, etc. The Entity Data Model primarily of three main concepts: Entities, which represent your domain objects. Associations, which represent a relationship between two entities. Functions, which represent stored procedures or UDFs in your database that can be mapped to model-level functionality. Because there will be plenty of situations where you’ll need to use stored procedures, the Entity Data Model allows you to map functions in your model to a store procedure in your database. This is useful because you can leverage a stored procedure without having to write ADO.NET code to call it, you can simply call a function on your model. EDM functions are represented as methods on your ObjectContext class.
  • EFConsoleDemoTO DO:Add EDM for Northwind Customers and Orders
  • Estimated Time: 1 minuteTalking Points: Now that we’ve seen the Entity Data Model, let’s see how to work with it using the Entity Framework. The Entity Framework is a set of services that allow you to consume an EDM from within your applications:Entity Client Entity SQL Object Services Entity SQL LINQ To Entities We’ll take a look at the 3 different flavors on consumption in detail, and discuss why and when you would use each one.
  • Estimated Time: 4 minutesTalking Points: The Entity Client is an Entity Framework “port” of the familiar object model of classes used in traditional ADO.NET programming, including:EntityCommandEntityConnectionEntityConnectionStringBuilderEntityDataReaderEntityParameterEntityTransaction Because of this fact it makes it a prime choice for developers migrating to the Entity Framework from ADO.NET. Just like traditional ADO.NET, your queries are returned as sequential text-based data that can iterated over using an EntityDataReader. This is great for performance, but lacks the rich object model that was created as part of your EDM. Entity Client gives you read-only access to your EDM. If data modification is required, you’ll have to use Object Services, which we’ll talk about in a bit. When using Entity Client, your queries are written using Entity SQL, which we’ll talk about in the next slide.
  • Estimated Time: 4 minutesTalking Points: Entity SQL is a query language that is syntactically very similar to SQL, but serves the sole-purpose of querying an EDM. Because it is meant for querying your EDM, this means your queries are written against your conceptual model, not your underlying data store. This higher-level abstraction allows you to write a textual query that is database agnostic. The translation from Entity SQL to T-SQL or PL/SQL (or whatever flavor your underlying data uses), is done by the selected ADO.NET Provider. Here we see a simple example that shows the same query written in T-SQL as well as Entity SQL. Notice that in Entity SQL we don’t have to do any joins, because the notion of relationships are first-class in our conceptual model. As a result, our query is half the size as the T-SQL version. Notice the use of the “Length” function in our Entity SQL example. This is called a “Canonical Function”, which is a high-level abstraction of a database function that will be translated into it’s respective database-specific flavor by your underlying provider
  • Estimated Time: 10 minutesDescription:At this point show some demos that consume the EDM we created in the last demo using Entity Client. Show a few simple queries highlighting some basic Entity SQL.
  • Estimated Time: 5 minutesTalking Points: While the Entity Client API is great and performant, it lacks the use of our created object model, as well as the ability to update data in our model. The Object Services API sits on top of Entity Client, and provides object materialization on top of our queries. This means that instead of getting text-based results, we get back a collection of CLR objects that we can easily work with. The two mains components of the Object Services taxonomy are: ObjectContext, and ObjectQuery<T>ObjectContext is equivalent to an EntityConnection, and is what manages our connection to the EDM as well as provides crucial services for working with our data.ObjectQuery is equivalent to an EntityCommand and represents a single query executed against our EDM, that is manifested back as strongly-typed objects. Object Services allows you to write queries using two flavors: Entity SQL LINQ To Entities The same Entity SQL queries you would write using Entity Client can be leveraged with Object Services, but with the added benefits you get with the higher abstraction level (i.e. object materialization). While Entity SQL is great for scenarios that require a dynamic query, or greater control over your query’s shape, you’re still working with a string that is error-prone. In addition to Entity SQL, Object Services allows you to write your queries against it in LINQ which provides you with strong-typing, error-checking, and a higher level of abstraction from Entity SQL. If you are already familiar with LINQ, then you don’t have to master Entity SQL in order to query an EDM, because LINQ To Entities will make the translation for you. In addition to object materialization, object services provides you with other benefits/services: Unit of work Your Object Context represents your unit of work, which aggregates all changes made to all entities attached/contained in it, so that when you want to push those changes back to the server, you can do so in a single batch. Identity tracking The ObjectContext keeps track of the entities you’ve queried for by key, so that if you later request the same entity (by key), using the same ObjectContext instance, it will return you the instance it already has instead of re-hitting the database. Eager/explicit loading The Entity Framework doesn’t pre-load any relationship properties for you. If you want to query an entity as well as some of it’s related entities, you’ll need to explicitly request that by performing a “span” using the Include method of the ObjectQuery<T> class. Alternatively you can call the Load method on your entity’s relationship property.
  • Estimated Time: 10 minutesDescription: Building upon where we left off at the last demo, show how to make Entity SQL queries using Object Services, retrieving back objects instead of text-based results. Then show how using LINQ To Entities can make querying your EDM even simpler and more intuitive. Show an example of identity tracking, eager loading, and explicit loading. Show some simple examples of modifying data and then saving it back to the database.
  • Estimated Time: 3 minutesTalking Points: This diagram helps to illustrate how each of the Entity Framework’s query options relate to each other. At the core of it all is the database-specific provider. This layer is what translates the query into the SQL flavor required for the underlying data source. Above that is the Entity Client API, which takes the Entity Framework query and passes in down to the database specific provider. If you want to use the Entity Client API directly, you see that you’re only query option is Entity SQL, and because it sits below Object Services, you don’t get any of its benefits. If you want to materialize your queries as objects, and get things like change tracking, identity mapping, relationship loading, etc. then you would use object services, that delegates its queries down to the Entity Client layer. When using Object Services you can leverage both Entity SQL and LINQ to make your queries.
  • Table per type – classic inheritance where separate table contains additional propertiesTable per hierarchy – many types contained in one table and used an indicator flag to indicate the type, table may contain null columns when they have no relevance to type. Situation may occur when table had been de-normalized. Can create many sub-types based on table.Table per concrete type – all information for sub-type in a separate table, e.g. discontinued product information used for reference
  • Estimated Time: 4 minutesTalking Points: Let’s briefly take a look at some common scenarios that services apply. If you develop an AJAX application, the client requests a page and the server returns HTML and JavaScript. At that point all communication happens between the client (JavaScript) and the server. This situation will typically call for a set of services on the server that the client can call using AJAX. In this scenario, the service required for client-server communication is largely data centric, and could look similar to the example we saw in the previous slide [Advance Animation] In a Silverlight application, the server returns the compiled Silverlight app, which then runs on the client’s machine. At that point any client-server communication is done with services. A lot of the services required by the client might be data-centric, at which point we’re in the same situation as we saw in the previous slide [Advance Animation] If you’re creating an online service that is meant to provide data over the cloud, then you’re creating nothing but data access logic, so we’re looking at the same scenario as before [Advance Animation] Finally if you’re creating a mashup, your server returns the UI of the mashup itself, which in turn contains logic for communicating with the data feeds that you’re mashing up. There are many other scenarios that require the use of services, but these exemplify enough the need for services that are largely data-centric. Keep in mind, that there are plenty of scenarios where service functionality that is operational in nature and not data-centric, is also typically required. But in many cases in these scenarios, the common need is data.
  • Estimated Time: 4 minutesTalking Points: Today is we wanted to make a web service using the .NET stack, we could use ASMX or WCF. Both options are great and provide there own level of flexibility and ease-of-use, based on your own familiarity. Imagine we create a service, and initially our service’s purpose is to return a specific customer from a data store [Advance Animation] We simply create a GetCustomer method on our service, and we’re good to go. We later realize that we need to be able to retrieve a list of all customers as well [Advance Animation] We add a GetCustomers method that retrieves all customers, easy enough. We realize that we’ll also have a need to retrieve customers, sorted by a specific field [Advance Animation] We add an overloaded version of GetCustomers that takes an order column. While our service’s functionality is increasing, so is its size. Now we realize that we need to be able to specify the sort direction of the ordered customers we retrieve [Advance Animation] Yet another overloaded version of our GetCustomers method is created. While being able to retrieve all customers is great, the amount of data being transported is too much, so we need to implement a paging mechanism [Advance Animation] Great, now we have paging, and another GetCustomers overloaded. Then we realize we need to be able to apply an arbitrary filter criteria to the method, so we add yet another overload [Advance Animation] So now we have created six methods on our service just to retrieve customer data with ordering, paging, and filtering. What if we later needed address data, and orders made by customers, etc. The amount of code needed to write data access code grows exponentially. Even further, we have only discussed the read operations. What if we later need to have insert, update, and delete methods for customers on our service? Yet more methods added, and more boilerplate code written.
  • Representational State Transfer (REST) is an architectural pattern used in the design of services. REST is about the way in which you expose and make available to callers the contract of the service. REST, therefore, is opposed to SOAP. ADO.NET Data Services’ RESTful interface uses a common URL syntax that clients can learn and leverage across all data services This makes it easy to consume new data services once you’re familiar with the syntax
  • It’s important to note that the “Data” in “Data Services” isn’t referring to a database. A data service is meant to expose data, of any kind over the web, in a standard, and easily consumable fashion. A data service is capable of exposing any object model that contains public properties of type IQueryable<T>. This criteria matches LINQ To SQL, and the Entity Framework, but can just as easily fit a custom object model. Data services implements the Atom Publishing Protocol (AtomPub or APP): Maps HTTP verbs to CRUD operations: GET = Read POST = Create PUT = UpdateDELETE = Delete Exposes the data in the form of Atom feeds and entries
  • http://localhost/AWDataServices/WebDataService.svc/$metadatahttp://localhost/AWDataServices/WebDataService.svc/Producthttp://localhost/AWDataServices/WebDataService.svc/Product(324)http://localhost/AWDataServices/WebDataService.svc/Product(324)/Namehttp://localhost/AWDataServices/WebDataService.svc/Product(324)/Name/$valuehttp://localhost/AWDataServices/WebDataService.svc/ProductSubcategory(2)/Producthttp://localhost/AWDataServices/WebDataService.svc/ProductSubcategory(2)/Product(789)/Namehttp://localhost/AWDataServices/WebDataService.svc/Product?$orderby=Namehttp://localhost/AWDataServices/WebDataService.svc/Product?$filter=Color%20eq%20'Black’http://localhost/AWDataServices/WebDataService.svc/Product?$top=10&$skip=30http://localhost/AWDataServices/WebDataService.svc/ProductSubcategory?$expand=Product
  • Estimated Time: 2 minutesTalking Points: While working with a data service in a browser is great, that doesn’t exactly help accent a client application very much. Because data services have a RESTful interface, you could program against use them using any HTTP stack, such as the HttpWebRequest class in .NET.HttpWebRequest doesn’t offer the rich data platform client functionality that developers might expect, which is why ADO.NET Data Services provides a set of client APIs for working with data services in a more intuitive way: There is a client API for .NET applications as well as Silverlight applications. These allow you to consume a data service from within managed code. There is a new data source control that allows the consumption of a data service using the familiar data source paradigm with an ASP.NET application, that can be easily connected to a GridView, ListView, FormView, or DetailsView. Finally there is a client-side API that allows data service consumption using the ASP.NET AJAX library. With these four client options, you are able to consume a data service from within any .NET application, regardless of the environment.
  • Estimated Time: 3 minutesTalking Points: When using the .NET client API, the DataServiceContext class represents your connection to the data service. The DataServiceContext class provides a lot of functionality around consuming a data service. The arguable two most notable features it provides are: An abstraction layer over the HTTP requests made to the service Object materialization Writing the code required to communicate with a data service using the HttpWebRequest class wouldn’t be that hard, but it would quickly get pretty verbose and time-consuming. Being able to use the DataServiceContext class saves you the effort of working at the HTTP-level completely (there are hooks that let you peer into it if you need to) and allows you to simply request the data you want and let the API handle the plumbing for you. As we saw in our previous examples, the data service returns data in AtomPub format by default, which is great, but would be a pain to have to manually parse in our client application. Fortunately the DataServiceContext class provides full object materialization which translates the returned AtomPub content into CLR objects that we can easily use. The best part about the DataServiceContext’s object materialization is that is doesn’t require the client-side model to match the service-side model at all. As the diagram illustrates, the two-models are completely independent and can to a large degree evolve independently.
  • Talking Points: ASP.NET Routing allows you to define a set of routes that dictate the URL templates your application can respond to, and map them to a handler that can direct the request at the proper resource (i.e. page, controller action method, etc) You can define your routes using both static URLs (/Products/Edit/23) as well as parameterized (/Blog/{year}/{month} /{day}) It is the route handler that is responsible for translating the requested route into an actionable resource than can respond to the request Once you’ve defined your custom route table, you can essentially use it to generate your application’s sitemap. If you know the resource you want, and the parameters it needs, then the ASP.NET Routing engine can generate the proper URL for you based on your route definitions Both ASP.NET MVC and ASP.NET Dynamic Data leverage ASP.NET Routing to enable their custom URL schemes
  • Talking Points: ASP.NET Dynamic Data allows you to specify a data model (EDM, LINQ To SQL, etc) and have an entirely scaffolded web application generated Complete with pages for viewing, adding, editing, and deleting records from each scaffolded entity in your underlying model Each page in the generated application is AJAX-enabled to provide a rich user-experience Each list page provides filtering based on the entity’s foreign-key relationships Your data model can be extended with the new data annotation attributes to add more semantic value to it Add validation to properties within your entity objects: regex, range, required, string length Add metadata to your entities: display column, sort column, display format Define custom data types and associate custom UI templates to entity properties When you create a Dynamic Data application, you get a collection of page templates and field templates, that are used to display your application. Each of these templates can be modified to suit your needs. New templates can also be created. Aside from creating a full-blown dynamic data web application, you can also leverage the dynamic behavior in an existing ASP.NET application, using the standard GridView, ListView, FormView controls you’re already familiar with.
  • Dynamic Data Entities Web ApplicationAdd EDM for Northwind databaseCategoriesProductsSuppliersAdd Data Field Templates
  • Add Dynamic Data Field to Field Templates – IntegerSliderDelete ReadOnly templateAdd UIHint to DataFieldTemplate
  • Estimated Time: 1 minuteTalking Points: In addition to brand new functionality, .NET 3.5 SP1 adds a lot of feature enhancements to existing technologies (listed).
  • As the .NET framework grows and matures, its file size also increases. This large download requirement often poses a problem for clients that don’t have the framework installed. The .NET Framework Client Profile is a new subset of the entire .NET Framework that includes only client-specific assemblies (i.e. WinForms, WPF) and doesn’t contain any of the server-specific assemblies (i.e. LINQ To SQL, Windows Workflow Foundation). The result is a reduced download footprint requirement for client applications that aren’t going to need the extra assemblies anyways. When an application is specifically targetting the .NET Framework Client Profile, Visual Studio will provide compile errors when the application’s code is attempting to use a type that isn’t within an included assembly. The size of the .NET Framework Client Profile is 26mb. A client machine that has the .NET Framework Client Profile can later upgrade to the full version of the .NET Framework if needed.
  • ASP.NET 3.5 SP1

    1. 1. .NET 3.5 Enhancements (SP1)<br />Dave Allen<br />ISV Application Architect<br />Developer and Platform Group<br />Microsoft UK<br />
    2. 2. Agenda<br />ADO.NET Entity Framework<br />ADO.NET Data Services<br />ASP.NET Routing<br />ASP.NET Dynamic Data<br />
    3. 3. ADO.NET Entity Framework<br />Another data access technology!?!<br />Not designed to replace what has gone before<br />Addresses the OOP versus Relational problem<br />OOP very well established<br />Relational have been around even longer<br />Bridging the gap has mostly been a manual task<br />Some 3rd party solutions, core problem remains<br />Objects != Relational Data<br />Fundamental problem is that relational data and objects in a programming language are NOT the same!<br />They have different semantics, languages, etc.<br />But both are still needed in most applications<br />
    4. 4. ADO.NET Entity Framework<br />Entity Data Model<br />Models Entities and relationships between those Entities<br />How does it bridge the gap between OOP and Relational<br />Common type system<br />Inheritance<br />Complex types<br />EDM is scoped to just modeling design of application data<br />Entity Framework<br />Provides services for consuming an EDM<br />Object Services<br />Entity Client (EntityConnection, EntityDataReader, etc.)<br />Entity SQL<br />LINQ To Entities<br />Provider model for 3rd party databases<br />
    5. 5. Entity Data Model<br />Application model<br />Mapped to a persistence store<br />Comprised of three layers:<br />Conceptual (CSDL)<br />Mapping (MSL)<br />Storage (SSDL)<br />Database agnostic<br />Not compiled<br />Embed as a resource<br />Store externally<br />Entity Data Model<br />Conceptual<br />Mapping<br />Storage<br />
    6. 6. Demo<br />Entity Data Model <br />
    7. 7. Entity Framework<br />EDM consumption options:<br />Entity Client<br />Entity SQL<br />Object Services<br />Entity SQL<br />LINQ To Entities<br />
    8. 8. Entity Client<br />Familiar ADO.NET object model:<br />EntityCommand<br />EntityConnection<br />EntityDataReader<br />Entity Parameter<br />EntityTransaction<br />Text-based results<br />Read-only<br />Uses Entity SQL<br />
    9. 9. Entity SQL<br /><ul><li>SQL-like query language
    10. 10. Targets conceptual model
    11. 11. Database agnostic</li></ul>T-SQL<br />Entity SQL<br />
    12. 12. Demo<br />Entity Client<br />
    13. 13. Object Services<br />Object materialized queries<br />ObjectContext<br />ObjectQuery<T><br />Built on top of Entity Client<br />Two query options:<br />Entity SQL<br />LINQ<br />Runtime services:<br />Unit of work<br />Identity tracking<br />Eager/explicit loading<br />
    14. 14. Demo<br />Object Services<br />
    15. 15. Entity Framework – Service Stack<br />LINQ To Entities<br />Entity SQL<br />Object Services<br />Entity Client<br />ADO.NET Provider<br />
    16. 16. Entity Framework features<br />Many to many relationships<br />Join tables ignored by designer in EDM<br />Side-effect, relationships cannot contain data<br />LINQ supports this via the aggregate functions<br />Inheritance<br />Allows Entities to be specialized<br />Maps to CLR inheritance<br />Fully supported in queries<br />3 types of inheritance<br />Table per type<br />Table per hierarchy<br />Table per concrete type<br />
    17. 17. Entity Framework features (2)<br />Entity splitting<br />Single entity split across multiple tables, something you may do with very large tables<br />Stored procedures<br />Most asked question about EF<br />Fully supported for CUD, map CUD functions to SPs<br />Mainly supported for queries, but doesn’t support composable queries, dynamic SQL within SPs<br />No metadata available at design-time<br />Working against principles of EF<br />Don’t use EF if you do this<br />Consider using TVF instead of SPs<br />
    18. 18. LINQ to SQL or Entity Framework<br />The case for LINQ to SQL<br />Use an ORM solution where database is 1:1 with Object Model<br />Use an ORM solution with inheritance hierarchies that are stored in a single table<br />Use POCO instead of using generated classes or deriving from a base class or implementing an interface<br />Leverage LINQ as the way to write queries<br />Use an ORM solution, but want something that is very performant and where optimization can be achieved, where necessary, through stored procedures<br />
    19. 19. LINQ to SQL or Entity Framework (2)<br />The case for LINQ to Entities<br />Write applications that can target different database engines in addition to SQL Server<br />Define domain models for applications and use them as the basis for the persistence layer<br />Use an ORM solution where classes may be 1:1 with the database or may have a different structure from the database schema<br />Use an ORM solution with inheritance that may have alternative storage schemes (single table for the hierarchy, single table for each class, single table for all data related to specific type)<br />Leverage LINQ as the way to write queries and have the query work in a database vendor agnostic manner<br />Use an ORM solution, but want something that is very performant and where optimization can be achieved, where necessary, through stored procedures<br />
    20. 20. Data Service over HTTP<br />HTML + JavaScript<br />DLL + XAML<br />Mashup UI<br />Data (XML, etc)<br />Data (XML, etc)<br />Data (XML, etc)<br />Data Feeds<br />AJAX Applications<br />Silverlight Applications<br />Online Services<br />Mashups<br />
    21. 21. Data Services today<br />Web Service (ASMX, WCF)<br />1) GetCustomer(int id)<br />2) GetCustomers()<br />3) GetCustomers(string orderBy)<br />4) GetCustomers(string orderBy, string sortDirection)<br />5) GetCustomers(string orderBy, string sortDirection,<br />int offset, int count)<br />6) GetCustomers(string orderBy, string sortDirection,<br />int offset, int count,<br /> string filter, string filterValue)<br />
    22. 22. ADO.NET Data Services<br />Data publishing service using a RESTful interface<br />Just uses HTTP<br />Therefore is able to use existing authentication mechanisms, and other infrastructure components such as caching and proxies<br />Uniform URL Syntax<br />Every piece of information is addressable<br />Predictable and flexible URL syntax<br />Multiple representations<br />ATOM<br />JSON<br />POX<br />
    23. 23. ADO.NET Data Services (2)<br />Exposes an object model (not a database) over the web<br />Entity Data Model – ADO.NET DS designed to work with EDM<br />LINQ To SQL model, read-only<br />Custom IQueryable<T> provider<br />Operation semantics, mapping of HTTP verbs for CRUD operations<br />GET – retrieve resource<br />POST – create a resource<br />PUT – update a resource<br />DELETE – delete a resource<br />
    24. 24. URL Conventions<br />Addressing entities and sets<br />Presentation options<br />
    25. 25. Filters<br />Logical operators<br />and, or , asc, desc, eq, ne, true, false, gt, ge, lt, le, not, null<br />Arithmetic operators<br />add, sub, div, mul, mod<br />String functions<br />endswith, indexof, replace, startswith, tolower, toupper, trim, substring, substringof, concat, length<br />Date functions<br />year, month, day, hour, minute, second<br />Math functions<br />round, floor, ceiling<br />Type functions<br />Is, Cast<br />
    26. 26. Demo<br />ADO.NET Data Services – Adventure Works<br />
    27. 27. Securing and Customizing Data Services<br />Visibility<br />Control visibility per container<br />Read, Query, and Write options<br />Authentication<br />Integrates with the hosting environment<br />ASP.NET, WCF, or Custom authentication module<br />Interceptors<br />Execute before HTTP GET/PUT/POST/DELETE<br />Enable validation, custom row-level security<br />Maintain the REST interface<br />Service operations<br />Allow you to inject methods into URI if you need to<br />
    28. 28. Clients<br />Data Service<br />
    29. 29. ASP.NET AJAX Client<br />Server<br />Client<br />Data<br />Service<br />Sys.Data.<br />DataService<br />HTTP<br />Data<br />Model<br />JSON<br />
    30. 30. ASP.NET AJAX Client<br />Sys.Data.ActionSequence<br />Sys.Data.DataService<br />Sys.Data.QueryBuilder<br />
    31. 31. .NET Client<br />Server<br />Client<br />Data<br />Service<br />Data<br />Service<br />Context<br />HTTP<br />Data<br />Model<br />Object<br />Model<br />
    32. 32. Demo<br />Silverlight 2.0 Client - Northwind<br />
    33. 33. Operation Batching<br />Without batching<br />Data<br />Service<br />Context<br />Data<br />Service<br />POST<br />PUT<br />POST<br />DELETE<br />DELETE<br />5 server hits<br />Operations:<br />Add Entity #1<br />Update Entity<br />Add Entity #2<br />Delete Entity #1<br />Delete Entity #2<br />
    34. 34. Operation Batching<br />With batching<br />Data<br />Service<br />Context<br />Data<br />Service<br />POST /$batch<br />1 server hit<br />Operations:<br />Add Entity<br />Update Entity<br />Add Entity #2<br />Delete Entity<br />Delete Entity #2<br />
    35. 35. Operation Batching<br />Without batching<br />Data<br />Service<br />Context<br />Data<br />Service<br />GET<br />GET<br />GET<br />3 server hits<br />Operations:<br />Get Entity #1<br />Get Entity #2<br />Get Entity #3<br />
    36. 36. Operation Batching<br />With batching<br />Data<br />Service<br />Context<br />Data<br />Service<br />GET /$batch<br />1 server hit<br />Operations:<br />Get Entity #1<br />Get Entity #2<br />Get Entity #3<br />
    37. 37. Demo<br />Operation Batching<br />
    38. 38. ASP.NET Routing<br />Define your application’s URL entry points<br />Static (/Products/Edit/23)<br />Parameterized (/Blog/{year}/{month} /{day})<br />Map these URL templates to route handlers<br />Generate URLs based off your defined route table<br />Can be leveraged by ASP.NET…<br />WebForms<br />MVC (using)<br />Dynamic Data (using)<br />
    39. 39. Demo<br />ASP.NET Routing<br />
    40. 40. ASP.NET Dynamic Data<br />RAD approach to building data driven web apps<br />Based on top of object model<br />LINQ To SQL<br />Entity Data Model<br />Data-driven web application ‘scaffolding’<br />Uses the power of the underlying schema<br />Customizable through templates<br />Full CRUD operations<br />AJAX-enabled<br />Extend the model<br />Metadata<br />Validation<br />
    41. 41. ASP.NET – traditional approach<br />Create a data access layer<br />ADO.NET (Datasets, Custom Objects, XML, etc.)<br />LINQ to SQL<br />Created ASP.NET pages<br />Add Data Source controls<br />Add controls that bind to Data Source controls<br />Add validation logic to page<br />Issues<br />Lots of work up front<br />Duplication of validation logic<br />DB schema ignored – data validation ends up in UI<br />Reuse needs to be thought about – not intuitive<br />
    42. 42. ASP.NET – dynamic data approach<br />Create a data model<br />Entity Framework<br />LINQ to SQL<br />Generate a Dynamic Data application<br />Customize the application<br />Model <br />Fields<br />Pages<br />Routes<br />
    43. 43. Annotating the model<br />Metadata on model controls behavior<br />Default metadata inferred from schema<br />Data types and relationships<br />Required fields, field type, string length, etc.<br />Generate a Dynamic Data application<br />Add additional metadata<br />Validation <br />Field labels and descriptions<br />Partial methods<br />
    44. 44. Demo<br />ASP.NET Dynamic Data<br />
    45. 45. Field templates<br />Fields are rendered using templates<br />Implemented as a user control .ascx<br />Controls the rendering, data binding, and validation<br />Based on the field data type, integer, bool, string, etc.<br />Default selection can be overridden<br />Default field templates ‘out-of-the-box’<br />These can be customized – they are just user controls<br />Create new field templates<br />
    46. 46. Dynamic Data Controls<br />DynamicDataManager<br />GridView, DetailsView<br />DynamicDataField<br />ListView, FormView<br />DynamicControl<br />LinqDataSource, EntitiesDataSource<br />DynamicControlParameter<br />DynamicQueryStringParameter<br />DynamicValidator<br />DynamicFilter, FilterRepeater<br />
    47. 47. Demo<br />ASP.NET Dynamic Data – Field Templates<br />
    48. 48. .NET 3.5 SP1 – What’s been improved<br />ASP.NET AJAX<br />WCF<br />WPF<br />WinForms<br />
    49. 49. Visual Studio 2008 SP1 – What’s else?<br />SQL 2008<br />JavaScript formatting and code preferences<br />Improved JavaScript Intellisense<br />Classic ASP Intellisense/Debugging<br />WCF refactoring support (svc/config files)<br />.NET Framework Client Profile<br />26mb download<br />