New things in ASP.NET 4.0

AJAX Functionality in ASP.NET 4.0

The AJAX functionality in ASP.NET 4.0 enables new client data scenarios for page and component developers that allow JSON data from the server to be rendered as HTML in a highly manageable and efficient way. To enable these scenarios, ASP.NET 4.0 includes the following major features:

• Client-side template rendering.
• Declarative instantiation of client-side behaviors and controls.
• Live data binding.
• Use of the observer pattern with JavaScript types.
• An AdoNetServiceProxy class for client-side interaction with ADO.NET Data Services.
• A client-side DataView control for data-bound UI in the browser.
• DataContext and AdoNetDataContext classes for interaction with Web services.
• Refactored ASP.NET AJAX framework libraries.

Client Template Rendering

In client-based development, templates are the most manageable way of creating UI from data. ASP.NET 4.0 includes a new template engine for client development that meets the following requirements:

• Performance — The engine must be able to render a typical number of items using a reasonably complex template before users perceive an interruption in their interaction with the application.
• Simplicity — The template syntax must be very readable and must be optimized for the most common scenario, namely one-way/one-time binding.
• Expression language — Templates must support an expression language to go beyond the simplest cases. The expression language should use familiar syntax, ideally JavaScript syntax.
• Interspersed code and markup — It must be possible to perform conditional rendering or to loop over markup by using code that surrounds HTML.
• XHTML compliance — The template should be able to render XHTML-compliant markup.
• Components — When using the template syntax, the developer must be able to instantiate client-side controls and behaviors that attach to HTML elements in the page or within templates.

Application Server (Dublin)

Provide standard host for WF and WCF applications

- First CTP will be provided on PDC. The community feedback will influence the RTM.

- Application Server “Dublin” will first become available after the release of the .NET Framework 4.0 and Visual Studio “10”.

- Application Server “Dublin” will initially be made available for download and use by Windows Server customers; later, “Dublin” will be included in future releases of Windows Server.

- Application Server “Dublin” will extend Internet Information Services (IIS) to provide a standard host for applications that use workflow or communications.

- It will provide support for Oslo modeling platform.

- It will support existing .NET apps.

- It will support integration with BizTalk Server (in this context called "Integration Server").

Pre-built developer services

· Message-based correlation

· Message forwarding service

· Content-based message routing

· Compensation service for long-running transactions

Greater scalability and easier manageability

· Enable scale-out of stateful workflow applications

· Persisting and rehydrating state for high scalability

· Enhanced management and monitoring functions

· Tracking store for workflow events

Supports “Oslo” modeling platform

- More about this at PDC :)