Scribd
Upload
61 views5 pages

26 July:: Supported OS

The document discusses installing and configuring ASP.NET AJAX. It describes downloading and installing the ASP.NET AJAX package, system requirements which include the .NET Framework and a supported version of Internet Explorer. Key controls for ASP.NET AJAX like the ScriptManager, UpdatePanel and triggers are explained. Examples provided demonstrate using these controls to asynchronously update parts of a webpage.

Uploaded by

Ramakumar MV
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
61 views5 pages

26 July:: Supported OS

The document discusses installing and configuring ASP.NET AJAX. It describes downloading and installing the ASP.NET AJAX package, system requirements which include the .NET Framework and a supported version of Internet Explorer. Key controls for ASP.NET AJAX like the ScriptManager, UpdatePanel and triggers are explained. Examples provided demonstrate using these controls to asynchronously update parts of a webpage.

Uploaded by

Ramakumar MV
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

26th July:

Asp.Net Ajax Installation:


Asp.Net Ajax is built-in into Asp.Net 3.5/4.0/4.5, it is also available as a separate download for Asp.Net 2.0 With Asp.Net Ajax we can create next generation interfaces with reusable Ajax components. We can enhance existing pages using powerful Ajax controls with support for all modern browsers. We can access remote services and data from the browser without complicated script. Even we can take advantage of improved efficiency and ease of use in Visual Studio 2005/08/10/12, with its built-in support for Asp.Net Ajax (The Asp.Net Ajax built-in support is available in Visual Studio 2008/10/12 only). Asp.Net Ajax allows us to create dynamic web pages that support partial page updates. It indicates Microsoft Asp.Net 2.0 Ajax extensions, which is a server framework and the Microsoft Ajax Library, which consists of client scripts that runs on the browser. We can install and use Asp.Net Ajax with Microsoft Visual Studio 2008/10/12 and visual web developer express edition; however we do not require to install Asp.Net Ajax if we are working Visual Studio2008/10/12 as it has built-in support. Note: The installation process install the Asp.Net Ajax assembly (System.Web.Extensions.dll) in the Global Assembly Cache(GAC).

System Requirements for Installation:


The Microsoft Asp.Net Ajax requires the following soft wares: Supported OS: 1. Windows 2003 2. Windows XP Home Edition 3. Windows XP professional 4. Windows vista/windows 2007/08. 5. Any windows OS version(including windows 2000)that support the Microsoft .Net Framework version 2.0 Required Soft Wares: 1. .Net Framework 2.0 or Later Versions. 2. Internet Explorer 6 or Later Versions. Optional Soft Wares: 1. Visual Studio 2005 or later versions, Visual Web Developer Express Edition.

Installation Process:
Make sure we are logged in with an account that has administrator rights(if our account does not have administrator rights the installation process displays errors the system administrator has set policies to prevent this installation. Download the AspAjaxExtSetup.msi installer package from the Asp.Net Ajax download website. Now in order to install just double click on MSI5 it starts automatically installation process in we can optionally provide the installation. If we do not provide it takes automatically by default. Once the installation is done, we can create an Asp.Net website enhanced with Ajax in Visual Studio 2005 and if we create an Asp.Net website in Visual Studio 2005/08/10/12 simply we create Asp.Net website or Asp.Net empty website. In which we can get to work on Asp.Net Ajax extension controls. These are the followings: ScriptManager ScriptManagerProxy Timer UpdatePanel UpdateProgress

ScriptManager:
It manages a script resource for client components, partial page rendering and custom user scripts. The script manager is required in order to use UpdatePanel, UpdateProgress and Timer. A ScriptManager control is a non visual component on the page and this control required on each page that needs to have Ajax features implementation. A ScriptManager control should be only one on the page that needs Ajax feature functionality. Eg: <asp:ScriptManager id=sm runat=server> </asp:ScriptManager>

ScriptManagerProxy:
ScriptManagerProxy should be used on the content pages that have master pages or web user control containing a script manager control. <asp:ScriptManagerProxy id=SMP runat=server>

</asp:ScriptManagerProxy>

UpdatePanel:
The UpdatePanel allows us to refresh selected parts of a webpage, instead of refreshing the whole page by using asynchronous post back. This control is a container that contains any other html as well as Asp.Net controls This control has two child tags: 1. ContentTemplate 2. Triggers The ContentTemplate tag is required, since it holds the content of the panel. The content can be anything that we would normally put on our page from literal text to any web controls which required being update as partial update. The Trigger tag allows us to display certain triggers which will make the panel update is content

27th July:
Eg: Working with UpdatePanel control to get current server date and time using asynchronous request. 1. First create a ScriptManager control on to the aspx page 2. Now we create UpdatePanel control in which a specify ContentTemplate tag and in that place a button control through which we make asynchronous button control post back and place a label control to display Updated current date and time from the server. <asp:ScriptManager ID=SM runat=server> </asp:ScriptManager> <asp:UpdatePanel ID=UP runat=server> <ContentTemplate> <asp:Button ID=Btn runat=server text=Current Date and Time from Server Onclick=Btn_Click/> <br/> <asp:Label ID=lblDateTime runat=server>

</asp:Label> </ContentTemplate> </asp:UdatePanel> Code Behind: Btn_Click() { lblDateTime.Text=DateTime.Now.ToString(dddd dd MMMM yyyy hh:mm:ss tt); } Note: ScriptManager control uses a property i.e. EnablePartialRendering set to true by default to allows asynchronous post back for the UpdatePanel control on support a browser.

UpdatePanel control uses following properties:


UpdateMode: It indicates whether the UpdatePanel will refresh on every asynchronous post back or only as the result of a specific action. The UpdatePanel property containing two property values such as: Always, Conditional. ChildrenAsTriggers: This property indicates whether post back coming from the UpdatePanels child control will cause the UpdatePanel to refresh or not (by default it is set to true). If UpdateMode property is set to always and ChildrenAsTriggers property set to false, it will generate an error at runtime. If UpdateMode property is set to always and ChildrenAsTriggers property set to true, then UpdatePanel refreshes if the whole page refreshes or when a child control inside the UpdatePanel does the post back. If ChildrenAsTriggers property set to false and UpdateMode property set to conditional then UpdatePanel refreshes if the whole page refreshes or when a trigger control outside the UpdatePanel initiates a refresh. If ChildrenAsTriggers property set to true and UpdateMode property set to conditional then UpdatePanel refreshes if the whole page refreshes or when a child control inside the UpdatePanel does not post back or when a trigger control outside the UpdatePanel initiates a refresh. E.g: Refreshing an UpdatePanel from an external button

You might also like