In this paper you will learn about: IIS Fundamentals, ASP - where it falls short, CLR Basics, ASP.NET Basics, ASP.NET and OOP and Type Anatomy

In this article, I would like to discuss the benefits of using server controls in ASP+ page and how it differs from using HTML control in an ASP page.This ASP+ page contains four server-side HTML controls: a text input field, a select list, a text area and a submit button. Lets name the file as simple.aspx. Notice the file extension is .aspx for ASP+ pages, while it is .asp for an ASP file.

As these sites are migrated to use ASP.NET, it is likely that classic ASP and ASP.NET pages will exist side-by-side, which is one of the touted advantages of ASP.NET. Unfortunately, there is no built-in way for an ASP.NET page to take advantage of a classic ASP include file, which means that the obvious solution if you want to maintain a consistent look and feel is to duplicate the look of the classic ASP template in an ASP.NET user control. Unfortunately, this means duplicating presentation logic, and inevitably, the classic ASP template and the ASP.NET template will get out of sync

With the advent of .NET, support for ASP.NET development has been fully integrated into Visual Studio .NET. It provides an extremely powerful and usable environment for ASP.NET development in the guise of Web Forms, as well as the more traditional types of application (Windows Forms). And now Visual Studio .NET is joined by another Microsoft product, namely the Microsoft ASP.NET Web Matrix Project (referred to from here on in as "Web Matrix").

Some ADO.NET sessions focus on the object model and .NET Framework classes and not on specific data access tasks that ADO.NET can solve. This session assumes you're somewhat familiar with the ADO.NET object model and want to see how to address the common tasks your application is likely to perform. Focus on getting connected in an ASP and Windows application, how to setup and run ad hoc queries as well as parameter-driven stored procedures, with and without returned parameters. See how to bind to DataReaders and DataSets and when it makes sense to use each. See how to fill and bind to a ListBox and a DataGrid and how to update the data, even when the query is the result of a complex join. Submit Date: 7/10/2003

Learn how to use the tools and options in Visual Studio .NET to increase your productivity and work efficiently in a team environment when building ASP.NET applications.

Even though the ink is barely dry on the documentation for Active Server Pages 3.0, Microsoft is already hard at work on the next generation of their core server-side programming technology. In this chapter, we introduce this new product, and look at what it is all about. Currently called ASP+ Next Generation Web Services (though this name might yet change) we'll see why we need a new version of ASP, and explore the concepts behind its design and implementation. While this book is aimed predominantly at experienced developers who have used ASP before, we start out in this chapter by examining some of the core issues involved when you decide to migrate to ASP+.

Web Services, in theory, aren't a new concept. They allow distributed applications to share business logic over a network. For example, the classic Web Service scenario is a stock quote service: one company provides a service that can accept requests for stock symbols and respond with stock quote details.A company building an investing site can then use the application logic provided by the stock quote company to retrieve stock quote detail. This problem sounds relatively simple, but it has been quite difficult to solve in the past. That's due largely to proprietary protocol formats, such as RMI, and the lock-down of open ports to only port 80 and port 443 (for HTTP and HTTPS traffic only).

When a page request is sent to the Web server, whether through a submission or location change, the page is run through a series of events during its creation and disposal. When we try to build ASP.NET pages and this execution cycle is not taken into account, we can cause a lot of headaches for ourselves. However, when used and manipulated correctly, a page's execution cycle can be an effective and powerful tool. Many developers are realizing that understanding what happens and when it happens is crucial to effectively writing ASP.NET pages or user controls. So let's examine in detail the ten events of an ASP.NET page, from creation to disposal. We will also see how to tap into these events to implant our own custom code. I'll set the stage with a simple submission form written in ASP.NET with C#. The page is loaded for the first time and has several server-side Web controls on it. When the Web server receives a request for the page, it will process our Web controls and we will eventually get rendered HTML. The first step in processing our page is object initialization

This session will give you the opportunity to learn the basics of building mobile web applications with ASP.NET Mobile Controls. See how the control model and drag and drop designer make it easy to target nearly 200 devices (cell phones, PDAs and pagers) from a single mobile web form. Find out what the adaptive rendering and rich customization and extensibility models can do for your mobile web applications.