Skip to main content

New AJAX Framework for the ASP.NET 1.1

ASPI have been constantly searching for the Ajax development for ASP.NET 1.1 technology. I want the ajax framework should be as simple as Ajax framework provided by Microsoft for ASP.NET 1.1.

After Searching So Far i have found a framework called

MagicAjax.NET is a free open-source framework, designed to make it easier and more intuitive for developers to integrate AJAX technology into their web pages, without replacing the ASP.NET controls and/or writing tons of javascript code. MagicAjax initially appeared as a codeproject article. Now it is hosted on Sourceforge and you can find the latest release at the downloads section.

It has some great features like following..

Easy integration

  • Just a few lines in web.config are enough to have MagicAjax
  • Only one easy to use control (AjaxPanel) is required to be your page to enable the AJAX functionality


  • You put the part of your page that you want to have AJAX =
    functionality inside an Ajax Panel and that's it; the Magic Ajax framework takes care all of the intrinsic details for you
  • The Ajax Panel works like the ASP.NET Panel and can display its contents on the Visual Studio Designer, allowing you to add controls to it visually
  • No javascript code is needed to be written


  • For most cases you can add AJAX functionality to your existing pages by only adding Ajax Panels and without even a single change in the source code
  • Magic Ajax replaces Post Backs with AJAX callbacks (Ajax Calls) that do not cause a refresh .on the client's browser
  • The Post Back and AJAX functionality can co-exist in the same page
    only the controls that are inside an Ajax Panel will perform an Ajax Call
    instead of Post Back
  • The page's View State is shared amongst Post Backs and Ajax call on changes to it by an Ajax Call will be available to a Post Back and vice
  • You handle an Ajax Call just like a Post Back, using the ASP.NET
    server-side programming model
  • Magic Ajax intuitively spots the changes that occur ed during an Ajax Call and sends the minimum possible required javascript that will reflect the changes on the client's browser
  • There are plenty of helper methods to help you with handling an
    Ajax Call. by code (i.e. if you want to send additional custom javascript to the client)

User experience

  • The user of your page enjoys a faster and richer browser UI, without the annoying Post Backs
  • A 'Loading' label notifies the user that an Ajax Call has been invoked
  • Instead of downloading the whole page for a Post back, the client only
    downloads chunks of javascript code that apply the changes made to the
    page's html
  • Magic Ajax's changes to the page are kept in the browser's cache, so if the
    user navigates to another page and then presses the browser's 'Back'
    button,he will see the same page that he was viewing before


  • Many configuration options give you total control of the inner workings of Magic Ajax
  • A small set of attributes applied to your ASP.NET controls can customize the way that they will be handled by Magic Ajax
  • You can define that an Ajax Call will be invoked asynchronously or synchronously for all controls of an Ajax Panel or for a single control You can define that certain controls of an Ajax Panel will invoke a plain Post Back
  • If the 'tracing' configuration option is enabled, a pop up window is created that displays information about the data that were sent to and from the server, allowing you to monitor the traffic of Ajax Calls that the page invokes
  • Clean object-oriented design makes it easy to extend the framework and add your own controls


  • Internet Explorer, FireFox, Netscape and Opera browsers are supported
  • If a browser is not supported or the user has disabled javascript,the
    page will revert to plain Post Backs automatically


  1. this is exactly what i was looking for in adding AJAX to 1.1 framework project without needing to do alot of extra coding to the current pages.

    thanks...ep (honolulu, hawaii)


Post a Comment

Your feedback is very important to me. Please provide your feedback via putting comments.

Popular posts from this blog

How to create Rest API(Web API) with ASP.NET Core 1.0

Recently Microsoft has released ASP.NET Core 1.0 RC2, I am getting lots of request from readers that about creating Web API. So I thought it will be a good idea to write a blog post about how to create Rest API(Web API) with ASP.NET Core 1.0.

So let’s get started via creating an ASP.NET Core 1.0 Web Application like following.

Once you click on ASP.NET Web Application, It will ask whether you need to create Web Application or Web API application. We are going to Web API so I am going to select Web API Application like following. Please note that in ASP.NET Core 1.0 there is no separate libraries or DLLs required for creating web APIs. This is just a project template.

Now once you click on OK It will create a Web API application with default values controller and program.cs.  As you know Program.cs is now starting point for the ASP.NET Core 1.0 application so It contains all the required configuration and startup items. Following is a code for that.
using System.IO; using Microsoft.Asp…

How to use migration with Entity Framework Core

Entity framework core is  the lightweight, extensible and cross-platform version of Entity Framework. Before some time, Microsoft has Released a new version of Entity Framework RC2. I have written a couple of blog post about Entity framework code first migration earlier for Entity framework 6.0. So there was a couple of request coming for writing a blog post about Entity Framework Core RC2 migration. So I thought it will be a good idea to give an overview how database migration works in Entity Framework Core RC2. This post will cover a basic scenario where we are going to create the database with existing ASP.NET Identity migration and then we are going to create a new model and have that migration applied in the database.

How to use Entity Framework Migrations: Let’s get started, To demonstrate entity framework core migrations, I am going to create a sample core web application like following.

Once we select core application it will appear the following dialog.

Now w…

Solution: gulp is not recognized as internal or external command- Visual Studio

Recently, After Upgrading to the newer version of Gulp, I was getting this error.  After doing lots of  finding online and in my system I was able to figure out that Modules like Gulp does not installed to the path. So when you try to run it from the command line it was showing below error.
gulp is not recognized as internal or external command How to solve : gulp is not recognized as internal or external command To solve this error we just need to create a new environment variable and set the NPM modules path there.

To create an environment variable,  Right click My Computer/ This Pc and click on properties.  It will open following windows.

Go to Advance System Settings and it will open system properties windows like below.

Click on Environment Variables it will open an environment and system variables windows like below.

Click on new System variable and put NODE_PATH in system variable name and %AppData%\npm\node_modules into the variable value like below.

Click on Ok. That’s it. N…