ASP.NET AJAX in .NET 3.5 and VS 2008 - Orcas New Features

Hi,

This blog post summarizes the new features of ASP.Net 3.5 and VS 2008 IDE.

Below are the new features been introduced.

§ VS 2008 Multi-Targeting Support

§ VS 2008 JavaScript Intellisense

§ VS 2008 JavaScript Debugging

§ VS 2008 Code Editing Improvements

§ VS 2008 Nested Master Page Support - - Nothing to add. Read Post.

§ VS 2008 Web Designer and CSS Improvements

§ VS 2008 Vertical Split View Support - Nothing to add. Read Post.

§ VS 2008 ASP.NET AJAX Control Extenders

§ ASP.NET ListView Control (Part 1: Building a Product Listing Page with Pure CSS)

§ ASP.NET AJAX in .NET 3.5 and VS 2008

Before we go further let’s have a quick view.

Compatibility - From VS 2005 to VS 2008 and .NET Framework 2.0 to 3.5?

Though .NET Framework 3.5 is a super compatible upgrade from .NET 2.0, it does not require you to change any code in order to target the new framework version. Only non-breaking modifications to existing .NET assemblies have been made in the .NET 3.5 release, and wherever possible added new features in separate assemblies to minimize the chance of breaking changes.

Also no project model or build changes have been made with VS 2008. Both the "web site" and "web application project" models will be fully supported going forward.

ASP.NET AJAX in .NET 3.5 and VS 2008

Here I have been putting major points only. For other details, how it works please folow the below link.

Reference: http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

AJAX included in ASP.NET 3.5 – New Features

· In ASP.NET 2.0, AJAX 1.0 shipped as a separate download to install.

· But with the .NET Framework 3.5 release, all of these features are built-in with ASP.NET - Which means you no separate download and installation.

· When you create a new ASP.NET application or web-site in VS 2008 that targets the .NET 3.5 framework, VS will Automatically Add The Appropriate Ajax Registrations in your web.config file and the core ASP.NET AJAX server controls will show up in your toolbox.

· The version of ASP.NET AJAX that ships with .NET 3.5 has a number of nice improvements to it - including

o Support for using UpdatePanels with WebParts,

o Support for WCF based JSON end-points,

o Support for using the ASP.NET Profile, Role and Login Application Services using JavaScript, and

o A number of bug fixes and performance improvements.

Side By Side Versioning

· In ASP.NET 2.0 – The implmentation of ASP.NET AJAX 1.0 lives in V1.0 of the System.Web.Extensions.dll assembly.

· In ASP.NET 3.5 – The implmentation of ASP.NET AJAX lives in V3.5 of the System.Web.Extensions.dll assembly.

<configSections>

<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0,

Culture=neutral, PublicKeyToken=31BF3856AD364E35">

</sectionGroup>

</configSection>

In ASP.Net 2.0 - Version= 1.0.61025.0

In ASP.Net 3.5 - Version= 3.5.0.0

· ASP.NET AJAX 1.0 and .NET 3.5 can both be installed side-by-side on the same machine.

· The V3.5 of System.Web.Extensions.dll is a fully compatible super-set of the 1.0 implementation (which means you don't need to change any code in order to use it).

· Each ASP.NET application on a machine can choose which version of ASP.NET AJAX they want to build and run against.

· You will be able to use VS 2008 to target ASP.NET AJAX 3.5 applications, as well as to use the new VS 2008 multi-targeting support to build ASP.NET 2.0 applications that use ASP.NET AJAX 1.0

Upgrading ASP.NET AJAX 1.0 Applications to use ASP.NET AJAX 3.5

· As such nothing is required except to open the Web Site Project in VS 2008.

· However, if any problem then check the post.

· To work with AJAX Control Toolkit in ASP.Net 3.5, required is to install the toolkit for 3.5 from here.

Note: When you use VS 2008 to open an existing ASP.NET 2.0 application that uses ASP.NET AJAX 1.0, you can alternatively choose not to upgrade it to .NET 3.5, and instead use the new multi-targeting features of VS 2008 to build it using ASP.NET 2.0 and ASP.NET AJAX 1.0.

Hope this helps.

Thanks & Regards,

Arun Manglick || Tech Lead

ASP.NET ListView Control - Orcas New Features

Hi,

This blog post summarizes the new features of ASP.Net 3.5 and VS 2008 IDE.

Below are the new features been introduced.

§ VS 2008 Multi-Targeting Support

§ VS 2008 JavaScript Intellisense

§ VS 2008 JavaScript Debugging

§ VS 2008 Code Editing Improvements

§ VS 2008 Nested Master Page Support - - Nothing to add. Read Post.

§ VS 2008 Web Designer and CSS Improvements

§ VS 2008 Vertical Split View Support - Nothing to add. Read Post.

§ VS 2008 ASP.NET AJAX Control Extenders

§ ASP.NET ListView Control (Part 1: Building a Product Listing Page with Pure CSS)

§ ASP.NET AJAX in .NET 3.5 and VS 2008

Before we go further let’s have a quick view.

Compatibility - From VS 2005 to VS 2008 and .NET Framework 2.0 to 3.5?

Though .NET Framework 3.5 is a super compatible upgrade from .NET 2.0, it does not require you to change any code in order to target the new framework version. Only non-breaking modifications to existing .NET assemblies have been made in the .NET 3.5 release, and wherever possible added new features in separate assemblies to minimize the chance of breaking changes.

Also no project model or build changes have been made with VS 2008. Both the "web site" and "web application project" models will be fully supported going forward.

ASP.NET ListView Control

Here I have been putting major points only. For other details, how it works please folow the below link.

Reference: http://weblogs.asp.net/scottgu/archive/2007/08/10/the-asp-listview-control-part-1-building-a-product-listing-page-with-clean-css-ui.aspx

· This is one of the new controls in ASP.NET 3.5.

· The ListView control supports the data editing, insertion, deleting, paging and sorting semantics of higher-level controls like the GridView.

· But - unlike the GridView - it provides you with complete control over the html markup generated.

· The <asp:listview> control is a Template-Driven Control and supports below templates:

o LayoutTemplate

o ItemTemplate

o AlternatingItemTemplate

o SelectedItemTemplate

o EditItemTemplate

o InsertItemTemplate

o EmptyItemTemplate

o EmptyDataTemplate

o ItemSeparatorTemplate

o GroupTemplate

o GroupSeparatorTemplate

o The LayoutTemplate and ItemTemplate - are the most common ones to use.

o <LayoutTemplate> template - Allows you to define the outer container/wrapper of your data UI.

o <ItemTemplate> template - Then allows you to define what each item in the list should look like.

o "ItemContainer" - Within the <LayoutTemplate> you then define an "ItemContainer" control that indicates where you want the <asp:ListView> control to dynamically add the <ItemTemplate> items into the output markup.

Note: <asp:placeholder> control is used instead of some other control as the itemContainer. Reason being- It will prevent any id values or extra markup being generated

Hope this helps.

Thanks & Regards,

Arun Manglick || Tech Lead

ASP.NET AJAX Control Extenders - Orcas New Features

Hi,

This blog post summarizes the new features of ASP.Net 3.5 and VS 2008 IDE.

Below are the new features been introduced.

§ VS 2008 Multi-Targeting Support

§ VS 2008 JavaScript Intellisense

§ VS 2008 JavaScript Debugging

§ VS 2008 Code Editing Improvements

§ VS 2008 Nested Master Page Support - - Nothing to add. Read Post.

§ VS 2008 Web Designer and CSS Improvements

§ VS 2008 Vertical Split View Support - Nothing to add. Read Post.

§ VS 2008 ASP.NET AJAX Control Extenders

§ ASP.NET ListView Control (Part 1: Building a Product Listing Page with Pure CSS)

§ ASP.NET AJAX in .NET 3.5 and VS 2008

Before we go further let’s have a quick view.

Compatibility - From VS 2005 to VS 2008 and .NET Framework 2.0 to 3.5?

Though .NET Framework 3.5 is a super compatible upgrade from .NET 2.0, it does not require you to change any code in order to target the new framework version. Only non-breaking modifications to existing .NET assemblies have been made in the .NET 3.5 release, and wherever possible added new features in separate assemblies to minimize the chance of breaking changes.

Also no project model or build changes have been made with VS 2008. Both the "web site" and "web application project" models will be fully supported going forward.

ASP.NET AJAX Control Extenders

Here I have been putting major points only. For other details, how it works please folow the below link.

Reference: http://weblogs.asp.net/scottgu/archive/2007/08/19/using-asp-net-ajax-control-extenders-in-vs-2008.aspx

What are ASP.NET Control Extenders?

ASP.NET Control Extenders are controls that derive from the System.Web.UI.ExtenderControl base class, and which can be used to add additional functionality (usually AJAX or JavaScript support) to existing controls already declared on a page. They enable developers to nicely encapsulate UI behavior, and make it really easy to add richer functionality to an application.

The ASP.NET AJAX Control Toolkit is a great example of a project that takes advantage of this control extender functionality. It includes more than 40+ free control extenders that you can easily download and use to add AJAX functionality to your applications.

Note: To use such extenders, either in VS 2005 / VS 2008, required is drag and drop the AJAXControlToolkit.dll assembly into the VS 2008 Toolbox to have its control extenders show up as controls that you can add to any ASP.NET web site or project.

How it is different using ASP.NET AJAX Control Extenders in VS 2008 than VS 2005:

· Manual efforts – Drag & Drop AJAXControlToolkit.dll assembly – is required to put the extender controls in toolbox – In both VS 2005 & VS 2008.

· With VS 2005 – Manual efforts required to wire-up control extenders yourself (either via source-view or via the property grid).

· VS 2008 makes it even easier to discover and attach control extenders to your controls.

· Once we add control extenders to the VS 2008 toolbox, we’ll find that a new "Add Extender..." smart task option appears when you select controls within the VS 2008 designer.

· Also when control extender is attached to a control in VS 2008, the property grid of the original control is extended to show both its original properties as well as the properties of the control extender attached to it.

Hope this helps.

Thanks & Regards,

Arun Manglick || Tech Lead

Web Designer and CSS Improvements - Orcas New Features

Hi,

This blog post summarizes the new features of ASP.Net 3.5 and VS 2008 IDE.

Below are the new features been introduced.

§ VS 2008 Multi-Targeting Support

§ VS 2008 JavaScript Intellisense

§ VS 2008 JavaScript Debugging

§ VS 2008 Code Editing Improvements

§ VS 2008 Nested Master Page Support - - Nothing to add. Read Post.

§ VS 2008 Web Designer and CSS Improvements

§ VS 2008 Vertical Split View Support - Nothing to add. Read Post.

§ VS 2008 ASP.NET AJAX Control Extenders

§ ASP.NET ListView Control (Part 1: Building a Product Listing Page with Pure CSS)

§ ASP.NET AJAX in .NET 3.5 and VS 2008

Before we go further let’s have a quick view.

Compatibility - From VS 2005 to VS 2008 and .NET Framework 2.0 to 3.5?

Though .NET Framework 3.5 is a super compatible upgrade from .NET 2.0, it does not require you to change any code in order to target the new framework version. Only non-breaking modifications to existing .NET assemblies have been made in the .NET 3.5 release, and wherever possible added new features in separate assemblies to minimize the chance of breaking changes.

Also no project model or build changes have been made with VS 2008. Both the "web site" and "web application project" models will be fully supported going forward.

Web Designer and CSS Improvements

Here I have been putting major points only. For other details, how it works please folow the below link.

Reference: http://weblogs.asp.net/scottgu/archive/2007/07/25/vs-2008-web-designer-and-css-support.aspx

New features-

§ Split View Editing – No Need. Read Post.

§ CSS Style Manager - Need. Read Post.

§ CSS Properties Window - Supported in both design and source view. Read Post

§ CSS Source View Intellisense - Supported in both design and source view. Read Post

§ Nested Master Page Support – No Need. Read Post

Hope this helps.

Thanks & Regards,

Arun Manglick || Tech Lead