There is no denial of
the fact that web applications are more scalable then its counterpart desktop
application. If we call upon the past couple of decades and compare the present
scenario from the standpoint of application software, undoubtedly web
applications have gained popularity over desktop applications. The architecture
of a web application is different than that of desktop applications. Web pages
typically are composed of some html tags, images, scripting tags and
JavaScript. Web pages interact with web servers with specific requests to
execute web pages hosted on the web servers using browsers. There are various
web servers that are in use these days. The most popular are IIS, WebSphere, Weblogic,
Apache, etc. Web servers are installed with script engines. Such scripting
engines are basically collections of libraries (dlls). When a page is requested
from a browser the web server does not convert html tags, but interprets and
parses all server tags and returns html as an output back to the browser.
Web pages have become more and more interactive these days
and often collect some input from the user and send that input to the server
for interpretation. Increasingly, it is the onus of the developer to validate
each and every such input on a web page. Validation of web pages has become
sine-qua-non. If the developer does not validate inputs, the request becomes
erroneous and the web application might throw an exception or even crash at
some point. In order to ensure the inputs are validated before submitting the
same to server, client side validation is required. There are some popular
scripts that are used for client side validation. JavaScript and VBScript are two
of these. Most browsers these days support JavaScript. Had there been no such
scripts for web form validations then the web developers would be in a state of
quandary. Now this is an era where users prefer doing most of their work on the
client side, then to shuttling it to the server as needed.
This kind of technology is in the transition of creating its
potential presence. It is not AJAX (Asynchronous Java and XML). I had an
occasion to make some spade work in AJAX and I came up with one sample
application. It is really great and different too. In AJAX there is no escape
from using less JavaScript. The developer had to shift most of the logic
required for the web form and write JavaScript as a consequence of which the
script size in terms of line numbers increases and so also become arduous to debug
and fix errors. Microsoft’s Visual Studio IDE lets developers write code with ease.
The debugging has become quite simple and easy which was not possible in
traditional ASP application. In spite of the latest and new features in VS IDE,
some of us find it cumbersome to debug JavaScript. But now you can stretch your
legs and unfold you arms for debugging with JavaScript. There is a way out to
debug JavaScript too. A question might be whirling in your mind as to how to do
that. Here are the some useful tips to debug JavaScript in asp.net.
Steps to be followed to debug JavaScript on asp.net: In this
article I have used IIS and Visual Studio 2005.
