Skip to main content

Introduction to AJAX

Asynchronous Javascript (AJAX) technology enables web applications to provide features like-
  • Partial Page Updates - Allows you to define an area of a webpage to postback and update independently from the rest of the page. Only the updated content is refreshed when the request completes
  • Indicate Progress of an operation - This allows you to track progress of server-side process and continuously update the user.
  • Desktop-like UI - With AJAX, you can provide users with controls such as modal dialog boxes, progress indicators, masked edit bixes, tooltips and more.
  • Cross Browser, cross platform support - Javascript, AJAX and JQuery are all supported on multiple browsers and multiple platforms.
Every ASP.NET page that uses AJAX must have one and only one ScriptManager class which enables-
  • Registration of custom scripts
  • Registration of web service method calls from client
Since you can use only one instance of ScriptManager class in an ASP.NET page there is a need to use ScriptManagerProxy class in the following scenarios-
  • When AJAX is used in a master page and also needed in content page
  • When AJAX is used in custom or user controls
An UpdatePanel control allows to define areas within a page that are partially updateable. Partial page updates are smaller asynchronous postbacks to the server.

UpdatePanel has some important properties like-
  1. Update Mode - The update mode can be set to one of the following modes
    • Always - If set to this mode the contents of the UpdatePanel is refreshed on every postback
    • Conditional - If set to conditional the refresh takes place based on ChildrenAsTriggers property (described below), or through an explicit call to the Update method or if Parent panel is refreshed.
  2. ChildrenAsTriggers - In case of nested UpdatePanels any update to a child UpdatePanel will not refresh contents of the Parent UpdatePanel unless ChildrenAsTriggers property is set to true.
Labels:

Comments

Post a Comment

Popular posts from this blog

Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.

I received the following error when trying to connect to a server's SQL Server. I was able to telnet the Server on the required TCP Port (1433) but SSMS could not connect to the SQL Server instance.  Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was – [Pre-Login] initialization=13472; handshake=14425; (Microsoft SQL Server, Error: -2) I eventually found that a Hyper-V Adapter was responsible for the issue, disabling which resolved the issue, have faced a similar issue with VirtualBox adapter too. Hope it helps.
Post a Comment
Read more

A simple customization in MPOS (Blank Operation) with AX7

Hi All, I recently had to add a Blank Operation to Modern POS (MPOS) to open a url from MPOS. Blank Operation as you may already be aware enable you to extend Microsoft Dynamics Retail for POS by adding custom logic that can be triggered from the Retail POS Register buttons. The way to implement Blank Operations in MPOS  is different from Enterprise POS as MPOS is a modern app as compared to EPOS which is a windows forms based app. So lets explore a very simple customization i.e. we want to open a URL on triggering a button from MPOS. 1. We would need to start with AX to add a button to the layout of MPOS. If you do not want to disturb the standard layouts its better to copy one of the existing layouts and then modify it using the designer. Please note the designer only opens in Internet Explorer so it will save you time by not trying to open it in other browsers e.g Chrome 2. Next we need to add this layout to the Store where we intend to use it...
Post a Comment
Read more