We always value hearing from our readers, and we want to know what you think about this book: what you liked, what you didn't like, and what you think we can do better next time. You can send us your comments, either by returning the reply card in the back of the book, or by e-mail to <feedback@wrox.com>. Please be sure to mention the book title in your message.
How to Download the Sample Code for the BookWhen you visit the Wrox web site, www.wrox.com, locate the title through our Find a Book facility or by using one of the title lists. Click Download Code on the book's detail page, or on the Download item in the Code column for title lists. The files that are available for download from our site have been archived using WinZip. When you've saved the archive to a folder on your hard drive, you need to extract the files using a decompression program such as WinZip or PKUnzip. When you extract the files, the code will be extracted into separate folders for each chapter of this book, so ensure your extraction utility is set to use folder names.
ErrataWe've made every effort to make sure that there are no errors in the text or in the code. However, no one is perfect and mistakes do occur. If you find an error in one of our books, such as a spelling mistake or a faulty piece of code, we would be very grateful to hear about it. By sending in errata you may save another reader hours of frustration, and, of course, you will be helping us to provide even higher quality information. Simply e-mail the information to <support@wrox.com> - your information will be checked and, if correct, posted to the errata page for that title, and used in reprints of the book. To find errata on the web site, go to www.wrox.com, and simply locate the title through our Advanced Search or title list. Click the Book Errata link below the cover graphic on the book's detail page.
E-Mail SupportIf you wish to query a problem in the book with an expert who knows the book in detail, then e-mail <support@wrox.com> with the title of the book and the last four numbers of the ISBN in the subject field of the e-mail. A typical e-mail should include the following things:
We need the above details to save your time and ours - we never send unsolicited junk mail. When you send an e-mail message, it will go through the following chain of support:
The Wrox support process can only offer support for issues that are directly pertinent to the content of our published title. Support for questions that fall outside the scope of normal book support is provided via the community lists of our http://p2p.wrox.com/ forum.
p2p.wrox.comFor author and peer discussion, join the P2P mailing lists. Our unique system provides programmer to programmer™ contact on mailing lists, forums, and newsgroups, all in addition to our one-to-one e-mail support system. If you post a query to P2P, you can be confident that the many Wrox authors and other industry experts who are present on our mailing lists are examining it. At p2p.wrox.com, you will find a number of different lists that will help you not only while you read this book, but also as you develop your own applications. Particularly appropriate to this book are the vs_dotnet and uml lists. To subscribe to a mailing list, just follow these steps:
Why This System Offers the Best SupportYou can choose to join the mailing lists, or you can receive them as a weekly digest. If you don't have the time (or the facility) to receive the mailing lists, then you can search our online archives. Junk and spam mails are deleted, and your own e-mail address is protected by the Lyris system. Queries about joining or leaving lists, and any other general queries about lists, should be sent to <listsupport@p2p.wrox.com>.
| |||||||||||||||||||||||||||||||||||