ASP.Net Web Developer Guide |
||||||||
|
||||||||
Sitemap : Content in Chapter 1 |
Content in Chapter 2 |
Content in Chapter 3 |
||||||||
|
||||||||
Thursday, January 12, 2006
Introducting ASP.net (Chapter 1)
Introduction
With the advent of ASP.NET we see a shift from traditional scripting to the beginning of full-fledged programming online.VBScript isn’t the only option anymore, as programmers can now employ the full power that lies behind both Visual Basic (VB) and C within their ASP.NET assemblies. There is no denying the widespread acceptance that .NET received from the developer community. It’s proven itself to be a well-developed framework with solid ideas on how the programming world should continue to change.The introduction of a software solution that enables anyone to code in any language that is compatible with the framework is groundbreaking to say the least. In this chapter we will take a look at how Active Server Pages (ASP) itself began just a couple of years ago and how it has captivated programmers ever since. It has had some problems, of course, but the .NET architecture seems to have found solutions to many preexisting programming problems.There have also been changes with how ASP works with the server and client, to provide the user with the information that you want to provide. Even though this is a stable beta, and many people are assuming already that what we are seeing within Beta 2 is basically the “freeze” for many features, it still has a couple of caveats, due to its beta nature. Learning from these problems within the framework can allow for preparation against it.
Learning from the History of ASP
You can trace the history of ASP right back to 1995 and the momentous occasion when microsoft realized they were falling behind in a fundamental shift in the industry by not embracing the Internet. Up until that point Microsoft had been developing their proprietary technologies, tools, and network protocols for the Microsoft Network; all of a sudden they needed an Internet strategy and fast. Microsoft has gone from a position of playing catch-up to one close to dominance, with the Internet Explorer Web browser having a strangle-hold on the Web browsing market, and Internet Information Server (IIS) installed at the majority of Fortune 1000 companies.
The Origins of ASP
Back in the mid ‘90s, when the commercial Web world was still young, there was not a great deal of choice of tools for the Web developer who wanted to make his or her Web site a truly useful place to do business.The choices were limited in both available server-side programming platforms and also desktop development tools to produce the solutions. In the end, the programmer was stuck with clumsy Common Gateway Interface (CGI) programs using compiled languages such as C, Delphi, and Visual Basic, or interpreted scripting languages like Perl or Rexx, and operating system shell scripts on systems such as UNIX.
In early 1996 Microsoft had a first stab at improving the situation by including the Internet Server Application Programming Interface (ISAPI) technology as part of Internet Information Server. ISAPI is an extension to the Windows Win32 API. It was developed as a way to create Web server software that interacts with the inner workings of Internet Information Server, bringing what was claimed to be a five-fold increase in performance. As you can well imagine from this description, as well as the immediate performance increase, it also had a side effect of increasing the complexity of the development for the
programmer. It wasn’t for the faint hearted, and it takes some serious hardcore programming knowledge to do ISAPI applications right.As well as ISAPI, Microsoft encouraged developers to embrace their Internet Database Connector (IDC) technology.This was a new way to connect Web sites to back-end databases through Open Database Connectivity (ODBC). The ISAPI and IDC technologies lifted Microsoft’s youthful and as yet unproven Web server from being a glorified file server to being a basic interactive application server platform for the first time.
Other vendors had tools out there, and several were very popular, such as Netscape Livewire. Livewire was a technology that ran under Netscape’s Web server and used a version of JavaScript for page logic, and also used Java components. Unfortunately, Livewire had similar limitations to ISAPI in that it was a compiled technology and the server needed stopping and starting to make changes visible.
With the advent of ASP.NET we see a shift from traditional scripting to the beginning of full-fledged programming online.VBScript isn’t the only option anymore, as programmers can now employ the full power that lies behind both Visual Basic (VB) and C within their ASP.NET assemblies. There is no denying the widespread acceptance that .NET received from the developer community. It’s proven itself to be a well-developed framework with solid ideas on how the programming world should continue to change.The introduction of a software solution that enables anyone to code in any language that is compatible with the framework is groundbreaking to say the least. In this chapter we will take a look at how Active Server Pages (ASP) itself began just a couple of years ago and how it has captivated programmers ever since. It has had some problems, of course, but the .NET architecture seems to have found solutions to many preexisting programming problems.There have also been changes with how ASP works with the server and client, to provide the user with the information that you want to provide. Even though this is a stable beta, and many people are assuming already that what we are seeing within Beta 2 is basically the “freeze” for many features, it still has a couple of caveats, due to its beta nature. Learning from these problems within the framework can allow for preparation against it.
Learning from the History of ASP
You can trace the history of ASP right back to 1995 and the momentous occasion when microsoft realized they were falling behind in a fundamental shift in the industry by not embracing the Internet. Up until that point Microsoft had been developing their proprietary technologies, tools, and network protocols for the Microsoft Network; all of a sudden they needed an Internet strategy and fast. Microsoft has gone from a position of playing catch-up to one close to dominance, with the Internet Explorer Web browser having a strangle-hold on the Web browsing market, and Internet Information Server (IIS) installed at the majority of Fortune 1000 companies.
The Origins of ASP
Back in the mid ‘90s, when the commercial Web world was still young, there was not a great deal of choice of tools for the Web developer who wanted to make his or her Web site a truly useful place to do business.The choices were limited in both available server-side programming platforms and also desktop development tools to produce the solutions. In the end, the programmer was stuck with clumsy Common Gateway Interface (CGI) programs using compiled languages such as C, Delphi, and Visual Basic, or interpreted scripting languages like Perl or Rexx, and operating system shell scripts on systems such as UNIX.
In early 1996 Microsoft had a first stab at improving the situation by including the Internet Server Application Programming Interface (ISAPI) technology as part of Internet Information Server. ISAPI is an extension to the Windows Win32 API. It was developed as a way to create Web server software that interacts with the inner workings of Internet Information Server, bringing what was claimed to be a five-fold increase in performance. As you can well imagine from this description, as well as the immediate performance increase, it also had a side effect of increasing the complexity of the development for the
programmer. It wasn’t for the faint hearted, and it takes some serious hardcore programming knowledge to do ISAPI applications right.As well as ISAPI, Microsoft encouraged developers to embrace their Internet Database Connector (IDC) technology.This was a new way to connect Web sites to back-end databases through Open Database Connectivity (ODBC). The ISAPI and IDC technologies lifted Microsoft’s youthful and as yet unproven Web server from being a glorified file server to being a basic interactive application server platform for the first time.
Other vendors had tools out there, and several were very popular, such as Netscape Livewire. Livewire was a technology that ran under Netscape’s Web server and used a version of JavaScript for page logic, and also used Java components. Unfortunately, Livewire had similar limitations to ISAPI in that it was a compiled technology and the server needed stopping and starting to make changes visible.
posted by Mr.Q at 11:59 PM
0 Comments:
Post a Comment
<< Home