| Building ASP.Net Server Controls Softcover Repri Edition Contributor(s): Michalk, Dale (Author), Cameron, Rob (Author) |
|
 |
ISBN: 1590591402 ISBN-13: 9781590591406 Publisher: Apress OUR PRICE: $49.49 Product Type: Paperback Published: October 2003 Annotation: The authors start out with very basic 'write' statements, but they progress into a sophisticated control -- one that includes templates, CSS styling and data binding. -- Paul Schaeflein, schaeflein.net This book is great for learning how pages and controls work in ASP.NET. -- Aaron Weiker Weblog This tutorial and reference will benefit you, the dedicated ASP.NET developer. If you understand the gains of object-oriented development, and want to apply those principles to ASP.NET and server control development, then this book will be your guide! In fact, this book is the most up-to-date text available on the market. Hot, new topics of discussion include mobile server control development (for supporting mobile phone web application development), and how to utilize the latest versions of Visual Studio .NET 2003 and the .NET Framework 1.1. |
| Additional Information |
| BISAC Categories: - Computers | Programming - Microsoft - Computers | Computer Engineering - Computers | Programming Languages - General |
| Dewey: 005.276 |
| Series: Expert's Voice |
| Physical Information: 1.77" H x 7.02" W x 9.16" (3.05 lbs) 880 pages |
| Descriptions, Reviews, Etc. |
| Publisher Description: IN THE EARLY DAYS of the web it was great fun to craft web pages by hand, carefully placing each HTML tag onto the page. As time has gone on, we've acquired a wealth of new technologies, including CSS, JavaScript, and the full gamut of HTML standards, including XHTML and DHTML. These advances bring freedom but also complexity and an almost overwhelming array of choices. Few developers can intimately know all of these technologies, and even if they could, browser compat- ibility issues are often significant enough to humble the most hard-core developer. However, even with these new technologies, we still often feel that we're rein- venting the wheel each time we build a website. For example, when we create image buttons that change when the mouse pointer rolls over them, we're writing fresh JavaScript script. That script has to be written and tested, but it also adds potentially unhelpful complexity when we come to change the page later. Then when we want to reuse the script, we have to figure out how to transplant it neatly, and then go through the whole test cycle again to make sure we didn't break it. And if the user interface element is more complex-for instance, a pop-up menu, a navigational tool bar, or a rich form control-we disappear into a deep, dark pit of DHTML and script, and it may not be clear whether the work is worthwhile. |