DotNet Framework 3.5 Beta 1 is released

Hi All,

The Microsoft .NET Framework 3.5 Beta 1 is a preview release of the latest version of the .NET Framework. The .NET Framework 3.5 which is cent percent backward compatible, adds many new exciting features in several major technology areas;  

For more detail about the features being introduced in .NET Framework 3.5 and Visual Studio code name “Orcas”, click herehttp://msdn2.microsoft.com/en-us/vstudio/aa700830.aspx

Managing Browser History and Back Button Support in ASP.NET AJAX

ASP.NET Futures (July 2007): Managing Browser History and Back Button Support in ASP.NET AJAX

This section provides information about the following features::

• History and book marking. You can manage history points in your application, which lets users click the browser's Back and Forward buttons to navigate logically through your application instead of browsing to other pages.
• The History server control. This control lets you manage application history and use the Navigate event in the server and client.
• The client Sys.Application object. This object lets you set history points. It also calls the pageNavigate function.

ASP.NET Futures (July 2007) release The following changes and additions have been introduced:

• History is now supported for the Apple Safari browser.
• Any state that is provided through the server is encoded and can be encrypted.
• You can define titles for individual history entries to be able to specify the page title used in the browser's history list.
• You can use history support entirely in the client, without the need for a server control.

History Management with Server Controls:

Server-based history management is provided by the History Web server control. This control enables you to handle server events as you normally do in postback scenarios and to set a history point on the control. At the history point you define an object or data (that is, state) that will be used to recreate your page when a navigation event is raised. When you create history points, the page's URL is appended with the serialized and encrypted data that is required to recreate the state of the page. This also creates an entry in the browser's history stack.

When users click the browser's Back button, the browser navigates through previously-viewed URLs, which will include URLs that contain history-point data. A Navigate event is raised for the History control; the event data includes the data appended to the URL. This enables you to handle the event and recreate the page state as required in your application.

The following example uses the UpdatePanel control for asynchronous postbacks. The History control is used to add history points during the Click event handler of the buttons that trigger the asynchronous postbacks. As a result, when you click the browser's Back button, you do not leave the Web page, but instead navigate through the previous UpdatePanel postbacks.

Enabling Permalinks to Page State

You can enable users to set a permalink to a specific state of the page. This means that they can bookmark a particular point in your application and then set the page with that state as a favorite or email the permalink URL so that the specific page state can be recreated.

To enable users to create a permalink, you can get the current state by using the Sys.Application.get_history().get_stateString() in client script, and History.getStateString() in server code. The following example shows how to create a permalink for a specific state through client-side JavaScript code.

Managing the Title of a History Entry

Typically, entries in the browser's history stack are identified by the title of the page for that entry. (To see an example of this, use the browser's recent-pages drop-down list to view the titles.) By default, when you create history entries in your application as described previously, the page's title is used to identify a history-state entry. However, you can provide meaningful titles for individual history entries. The following sample shows how to perform this task. In the client, add a title parameter when you call the Sys.Application.get_history().addHistoryPoint( ) method. In server code, you can add a title when you call the History.AddHistoryPoint( ) method.

ASP.NET in the .NET Framework 3.5 Service Pack 1 release includes numerous bug fixes

ASP.NET in the .NET Framework 3.5 Service Pack 1 release includes numerous bug fixes. In addition, it includes features for the following:

·          Enabling high-productivity data scenarios by using ASP.NET Dynamic Data.

·          Supporting the browser navigation in ASP.NET AJAX applications by using ASP.NET AJAX browser history.

·          Increasing the download speed for ASP.NET applications by using ASP.NET AJAX script combining.

 

New Futures:

1)      ASP.NET Dynamic Data

2)      ASP.NET AJAX browser History

3)      ASP.NET AJAX script combining

4)      ADO.NET Data Service

5)      ADO.NET Entity Framework

 

ASP.NET Dynamic Data:

ASP.NET Dynamic Data brings major usability and RAD development changes to the existing ASP.NET data controls. RAD development is significantly increased by the use of a rich scaffolding framework. After you add a LINQ to SQL or Entity Framework data model to a project, you can simply register it with Dynamic Data. The result is a fully functional Web site. Full CRUD (create, read, update, and delete) operations are supported. The site includes filtering by foreign keys and Boolean fields; foreign keys are automatically converted to their friendly names. Smart validation is automatically available, which provides validation based on database constraints for nullable fields, data type, and field length.

The DetailsView and GridView controls have been extended to display fields by using templates instead of by using hard-coded rules that are programmed in the controls. These templates are part of the project, and you can customize them to change their appearance or to specify which controls they use for rendering. This makes it very easy to make a change in one place in your site that specifies how to present dates for editing, as one example. FormView and ListView controls can implement similar behavior by using a DynamicControl object in their templates and by specifying which field in the row to display. Dynamic Data will then automatically build the UI for these controls based on the templates that you specify. 

Validation is significantly improved in the controls as well. The controls read metadata for a LINQ to SQL or Entity Framework data model and provide automatic validation based on the model. For example, if a column in the database is limited to 50 characters, and if a column is marked as not nullable, a RequiredFieldValidatorcontrol is automatically enabled for the column. (The controls also automatically support data-model-level validation.) You can apply other metadata to take further control over display and validation. 

The RTM version of Dynamic Data and Entity Framework have a naming mismatch that can cause some errors with some types of data relationships. A workaround is available which provides a fix for 1->0..1 and *->1 relationships which may generate error messages similar to "'System.Web.UI.WebControls.EntityDataSourceWrapper' does not contain a property with the name 'Orders.OrderID'". This fix replaces the default Entity Framwork Data Model provider for Dynamic Data with a new data model provider that works around these issues.

For More information Please click on following link:

http://www.asp.net/downloads/3.5-SP1/default.aspx