Sybex,MasteringASP.NETwithC#2002.pdf

Table of Contents

Mastering ASP.NET with C#

Introduction

Part I - Basic Web Programming

Chapter 1 -Behind the Scenes — How Web Applications Work

Chapter 2 -HTML Basics

Chapter 3 -Brief Guide to Dynamic Web Applications

Part II - Server-Side Web Programming with Visual C#

Chapter 4 -Introduction to ASP.NET

Chapter 5 -Introduction to Web Forms

Chapter 6 -Introduction to the System.Web Namespace

Chapter 7 -The SessionState Object

Chapter 8 -The HttpServerUtility Object

Chapter 9 -Debugging ASP.NET and Error Handling

Chapter 10 -File and Event Log Access with ASP.NET

Chapter 11 -Sending and Receiving Messages with ASP.NET

Part III - Accessing Data with ASP.NET

Chapter 12 -Introduction to Relational Databases and SQL

Chapter 13 -Introduction to ADO.NET

Chapter 14 -Accessing Data

Chapter 15 -Using XML in Web Applications

Part IV - C# Web Applications

Chapter 16 -Introduction to C# Web Applications

Chapter 17 -State Maintenance and Cacheing

Chapter 18 -Controlling Access and Monitoring

Chapter 19 -Planning Applications

Part V - AdvancedVisual C# Web Applications

Chapter 20 -Leveraging Browser Clients

Chapter 21 -Web Services

Chapter 22 -Web Services, COM Components, and the SOAP Toolkit

Chapter 23 -Build Your Own Web Controls

Chapter 24 -Efficiency and Scalability

Afterword

Part VI - Appendices

Appendix A -Quick HTML Reference

Appendix B -JScript 5.5 Reference

Index

List of Figures

List of Tables

List of Listings

List of Sidebars

Mastering ASP.NET with C#

A. Russell Jones

Associate Publisher: Richard Mills

Acquisitions and Developmental Editor: Tom Cirtin

Editor: Gene Redding

Production Editor: Erica Yee

Technical Editor: Mike Gunderloy

Book Designer: Maureen Forys, Happenstance Type-O-Rama

Graphic Illustrator: Tony Jonick

Electronic Publishing Specialist: Jill Niles

Proofreaders: Nelson Kim, Laurie O'Connell, Yariv Rabinovitch, Nancy Riddiough

Indexer: Ted Laux

Cover Designer: Design Site

Cover Illustrator: Design Site

reserved. The author created reusable code in this publication expressly for reuse by readers. Sybex

grants readers limited permission to reuse the code found in this publication or on www.sybex.com so

long as the author is attributed in any application containing the reusable code and the code itself is

never distributed, posted online by electronic transmission, sold, or commercially exploited as a stand-

alone product. Aside from this specific exception concerning reusable code, no part of this publication

may be stored in a retrieval system, transmitted, or reproduced in any way, including but not limited to

photocopy, photograph, magnetic, or other record, without the prior agreement and written permission of

the publisher.

Library of Congress Card Number: 2002103165

ISBN: 0-7821-2989-7

SYBEX and the SYBEX logo are either registered trademarks or trademarks of SYBEX Inc. in the United

States and/or other countries.

reserved.FullShot is a trademark of Inbit Incorporated.

Netscape Communications, the Netscape Communications logo, Netscape, and Netscape Navigator are

trademarks of Netscape Communications Corporation.

Netscape Communications Corporation has not authorized, sponsored, endorsed, or approved this

publication and is not responsible for its content. Netscape and the Netscape Communications

Corporate Logos are trademarks and trade names of Netscape Communications Corporation. All other

product names and/or logos are trademarks of their respective owners.

Internet screen shot(s) using Microsoft Internet Explorer 6 reprinted by permission from Microsoft

Corporation.

The author created reusable code in this publication expressly for reuse by readers. Sybex grants

readers limited permission to reuse the code found in this publication or on www.sybex.com so long as

the author is attributed in any application containing the reusable code and the code itself is never

distributed, posted online by electronic transmission, sold, or commercially exploited as a stand-alone

product.

TRADEMARKS: SYBEX has attempted throughout this book to distinguish proprietary trademarks from

descriptive terms by following the capitalization style used by the manufacturer.

The author and publisher have made their best efforts to prepare this book, and the content is based

upon final release software whenever possible. Portions of the manuscript may be based upon pre-

release versions supplied by software manufacturer(s). The author and the publisher make no

representation or warranties of any kind with regard to the completeness or accuracy of the contents

herein and accept no liability of any kind including but not limited to performance, merchantability, fitness

for any particular purpose, or any losses or damages of any kind caused or alleged to be caused directly

or indirectly from this book.

Manufactured in the United States of America

10 9 8 7 6 5 4 3 2 1

I dedicate this book to my friend Brenda Lewis, who cares not at all about its contents, but has nurtured

its author since near childhood, and to my wife, Janet, who has— yet again— had the patience to endure

a book's creation.

Acknowledgments

I would like to acknowledge the considerable talents of the editorial staff at Sybex, who have been both

patient and thorough, particularly Richard Mills, Tom Cirtin, Erica Yee, Gene Redding, Denise Santoro

Lincoln, and Mike Gunderloy, and the many, often unrewarded people who spend time answering

questions in technical newsgroups. You do make a difference.

Introduction

For the past 20 years, programming efforts have alternated between servers and clients. From

mainframe batch processing to stand-alone applications to client-server to Internet, the focus of

development shifts back and forth according to the current hardware, software, and communications

model available. From teletypes to terminals, mainframes to minicomputers to modern servers, desktops

to laptops to handheld devices, hard-wired direct connections to private networks to the Internet,

programmers have concentrated their efforts either on improving the user interface or building the back-

end systems that serve data to the devices that run the user interface. During the 1980s and early

1990s, the rapid evolution of microcomputers forced developers' attention toward the latter, which is why

today's computer buyers enjoy high-resolution, deep-color displays; sound and voice capabilities; fast

processors; a surfeit of data storage options; cheap memory; and powerful, graphical, interactive

operating systems.

The rapid improvement in microcomputers caused a corresponding fragmentation of data; people

worked with individual files on their own computers. Interestingly, that very fragmentation led to a rapid

corresponding rise in networking capabilities, because businesses needed workers to be able to share

information— and they also needed centralized, secure control of that information. Those needs drove

the development of client-server computing, which couples the rich graphical user interface and fast

processing of microcomputers with fast centralized databases.

Unfortunately, client-server computing, as it was initially conceived, caused several problems. The "fat"

client programs were difficult to deploy, install, maintain, and upgrade. What companies needed was a

different kind of client application: one that could accept data and application code from the centralized

servers but display and let users interact with that data as with the desktop applications they had come

to expect. The advent of the World Wide Web and browser technology seemed to promise an answer.

In the past several years, we've seen the resurrection of the "thin" client— typically a browser or small

executable that retrieves data on demand from a central server much as mainframe terminals did back

in the early days of computing. While the new thin clients have much more functionality than their

mainframe-terminal counterparts did, they're still not completely satisfying to a public used to the

richness of commercial applications such as Microsoft Office, Quicken, and thousands of custom client-

server applications.

However, despite these shortcomings, browsers running HTML-based front-ends have changed the

world. People and businesses are growing increasingly dependent on location irrelevance. They want to

be able to reach any server, anywhere, anytime— and they're well on the road to realizing that desire.

Location irrelevance trumps ease-of-use, so browsers and other remote clients are now ubiquitous.

Unfortunately, browsers haven't completely replaced the rich desktop client applications. They leave

many people feeling as if they've been transported a couple of decades into the past. Browsers work

extremely well when delivering static data, such as reports, documents, and images, but considerably

less well when they're forced into client-server, form-driven, data-entry roles. The smooth, point-and-

click page transitions you experience when browsing the Web often stumble when the application

suddenly requires you to enter data.

I believe .NET has the capability to change the situation. With the .NET framework, it's possible to

create more interactive and responsive centrally located software. At the same time, .NET improves the

tools and simplifies the process for building rich clients. Finally, it bridges the two by making it extremely

easy to provide both rich and thin clients (remember, you can't be too rich or too thin) with centrally

located and managed data, meaning your users can have their familiar graphical controls and behavior,

and you can manage the application centrally by having it dynamically update on demand.

What's in This Book?

This is a book of exploration (mine) as much as it is a book of explication. Microsoft's .NET framework is

extremely well designed for such a large and complex entity— but it is both large and complex. The

biggest problem I faced during the writing of this book wasn't what to include, but what to leave out, and

that is a severe problem. There's so much material I would have liked to include, but time, space, the

dramatic changes in the .NET framework and Visual Studio during the early portions of the writing and

my own still-immature knowledge of the .NET framework prevented that.

The driving force behind this book was the idea that .NET provides a completely new model for building

Web applications, as well as two brand-new languages for doing so (C# and VB.NET) and an expanded

version of server-side JScript (JScript.NET).

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika: