Conventions and Special Elements Used in This Book

function OpenWin(url, w, h) { if(!w) w = 400; if(!h) h = 300; window.open(url, "_new", "width=" + w + ",height=" + h + ",menubar=no,toobar=no,scrollbars=yes", true); } function Print() { window.focus(); if(window.print) { window.print(); window.setTimeout('window.close();',5000); } }
Team-Fly    

Special Edition Using Microsoft® Visual Basic® .NET
By Brian Siler, Jeff Spotts
Table of Contents
Introduction


This book includes various conventions and special elements to highlight specific things and make using the book easier. Familiarize yourself with these conventions and elements, and allow them to enhance your reading experience.

Conventions

The following list details conventions used in the book:

  • Italic type is used to emphasize the author's points or to introduce new terms. You may also see italics used in code samples to indicate a placeholder for additional code.

  • Screen messages, code listings, and command samples appear in monospace type.

  • URLs, newsgroups, Internet addresses, and anything you are asked to type also appears in monospace type.

  • Occasionally, a code sample or listing will show a portion of program code with certain lines set in bold type. In such cases, the bold type signifies code you are to add to existing code. This approach enables you to see what you are supposed to add or change in context.

  • Because of the space limitations of this book's pages, a few code lines in this book's examples cannot be printed exactly as you must enter them. In cases where breaking such a line is necessary to fit within the book's margins, the Visual Basic continuation character (_) will be used at the end of the line that is broken. You can leave these characters out and enter the code on a single line, or just enter the characters as they appear. Visual Basic will understand the code either way. If you download the code from the Web site, you will not have to worry about adding this character.

Special Elements

Certain types of information are set off in special book elements. The following explanations and examples indicate the kinds of elements you will encounter in the book.

At the end of each chapter you may find a "From Here . . . " section, a Q&A, or a Troubleshooting section to wrap up the chapter. These sections refer you to other chapters that cover related material or extend the topic you just read about. They are designed to help you synthesize the information or troubleshoot problems.

See cross-references within each chapter for directions to more information on a particular topic.

Tip

Tips present short advice on a quick or often overlooked procedure.


Note

Notes provide additional information that might help you avoid problems, or offer advice that relates to the topic.


Caution

Cautions warn you about potential problems that a procedure might cause, unexpected results, and mistakes to avoid.


Sidebar

Longer discussions not integral to the flow of the chapter are set aside as sidebars. Look for these sidebars to find out even more information.


    Team-Fly    
    Top
     



    Special Edition Using Visual Basic. NET
    Special Edition Using Visual Basic.NET
    ISBN: 078972572X
    EAN: 2147483647
    Year: 2001
    Pages: 198

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net