cdkey who know ??在线!

ywm0123 2003-08-20 02:33:26
谁知道网络三剑客的序列号!
...全文
68 11 打赏 收藏 转发到动态 举报
写回复
用AI写文章
11 条回复
切换为时间正序
请发表友善的回复…
发表回复
ywm0123 2003-08-22
  • 打赏
  • 举报
回复
谢谢
jy2004 2003-08-22
  • 打赏
  • 举报
回复
不错
Davelu 2003-08-22
  • 打赏
  • 举报
回复
对,我也在用DreamweaverMX了。
ssson 2003-08-22
  • 打赏
  • 举报
回复
晕就一个字
哇虾米丢吾哉啊
bxjgood66 2003-08-22
  • 打赏
  • 举报
回复
和楼上的有同感呀!!!
kenshin17 2003-08-20
  • 打赏
  • 举报
回复
强烈推荐DreamweaverMX
用了它,你会马上抛弃DW4的
moukyou 2003-08-20
  • 打赏
  • 举报
回复
4. Flash MX FLW600-09531-57240-83750
5. Dreamweaver MX DWW600-54622-26755-01760
6. Fireworks MX FWW600-04860-63582-21175
meilidehua 2003-08-20
  • 打赏
  • 举报
回复
DWW400-00470-47289-60450
ywm0123 2003-08-20
  • 打赏
  • 举报
回复
dreamweaver4.0中文的
zjallan 2003-08-20
  • 打赏
  • 举报
回复
FT
楼主不会搜?
www.google.com
meilidehua 2003-08-20
  • 打赏
  • 举报
回复
dreamweaverMX: DWW600-54622-26755-01760
flashMX: FLW600-09531-57240-83750
fireworkMX FWW600-04860-63582-21175
Thank you for purchasing or considering the purchase of Windows 7 In Depth. It’s amazing the changes that 20-odd years can bring to a com- puter product such as Windows. When we wrote our first Windows book back in the mid-1980s, our publisher didn’t even think the book would sell well enough to print more than 5,000 copies. Microsoft stock wasn’t even a blip on most investors’ radar screens. Boy, were they in the dark! Who could have imagined that a little more than a decade later, anyone who hoped to get hired for even a temp job in a small office would need to know how to use Microsoft Windows, Office, and a PC. Fifteen or so Windows books later, we’re still finding new and excit- ing stuff to share with our readers. Who could have imagined in 1985 that a mass-market operating system two decades later would have to include support for so many technolo- gies, most of which didn’t even exist at the time: DVD, DVD±RW, CD-R and CD-RW, Internet and intranet, MP3, MPEG, WMA, DV, USB, FireWire, APM, ACPI, RAID, UPS, PPOE, Gigabit Ethernet, 802.11g, WPA2, IPv6, Teredo, speech recognition, touch and pen interfaces, fault tolerance, disk encryption and compression…? The list goes on. And that 8GB of disk space Windows 7 occupies? It would have cost about half a million dollars in 1985. Today, it costs less than a dollar. In 1981, when we were building our first computers, the operating sys- tem (CP/M) had to be modified in assembly language and recompiled, and hardware parts had to be soldered together to make almost any new addition (such as a video display terminal) work. Virtually nothing was standardized, with the end result being that computers remained out of reach for average folks. Together, Microsoft, Intel, and IBM changed all that. Today you can pur- chase a computer, a printer, a scanner, an external disk drive, a key- board, a modem, a monitor, and a video card over the Internet, plug Introduction From the Library of Lee Bogdanoff Introduction them in, install Windows, and they’ll work together. The creation and adoption (and sometimes forcing) of hardware and software standards that have made the PC a household appliance the world over can largely be credited to Microsoft, like it or not. The unifying glue of this PC revolution has been Windows. Yes, we all love to hate Windows, but it’s here to stay. Linux and Mac OS X are formidable alterna- tives, but for most of us, at least for some time, Windows and Windows applications are “where it’s at.” And Windows 7 ushers in truly significant changes to the landscape. That’s why we were excited to write this book. Why This Book? We all know this book will make an effective doorstop in a few years. You probably have a few already. (We’ve even written a few!) If you think it contains more information than you need, just remember how helpful a good reference can be when you need it at the 11th hour. And we all know that computer technology changes so fast that it’s sometimes easier just to blink and ignore a phase than to study up on it. Windows 7 is definitely a significant upgrade in Windows’ security and sophistication—one you’re going to need to understand. If you’re moving up to Windows 7 from Windows XP, you should know that Windows 7 is a very dif- ferent animal. Yes, the graphics and display elements are flashier, but it’s the deeper changes that matter most. With its radically improved security systems, revamped Control Panel, friendlier net- work setup tools, new problem-tracking systems, improved power management and usability tools for mobile computers, and completely revamped networking and graphics software infrastructures, Windows 7 leaves XP in the dust. And if you’re moving up from Vista, you’ll be very pleasantly surprised at the improvements. Vista got a bad rap, perhaps for some good reasons: It was slow, required too much RAM, had driver issues, and annoyed users with its User Account Control prompts. Windows 7 fixes all of that, thank goodness! Think of Windows 7 as Vista after three years at a spa/reform school. It’s leaner, stronger, more refined, and ever so polite. In all ways, Windows 7 is superior to any operating sys- tem Microsoft has ever produced. Is Windows 7 so easy to use that books are unnecessary? Unfortunately, no. True, as with other releases of Windows, online help is available. As has been the case ever since Windows 95, how- ever, no printed documentation is available (to save Microsoft the cost), and the Help files are writ- ten by Microsoft employees and contractors. You won’t find criticisms, complaints, workarounds, or suggestions that you use alternative software vendors, let alone explanations of whyyou have to do things a certain way. For that, you need this book! We will even show you tools and techniques that Microsoft’s insiders didn’t think were important enough to document at all. You might know that Windows 7 comes in a bewildering array of versions: primarily Home Premium, Professional, Enterprise, and Ultimate (not to mention Starter, intended for relatively primitive “netbook” computers and emerging markets; Home Basic, sold only in emerging markets; and several extra versions sold in the European Union to comply with antitrust court-mandated restrictions). But Windows 7 is Windows 7, and all that really distinguishes the versions is the availability of various features. Mostof the differences matter only in the corporate world, where Windows 7 will be managed by network administrators, so most corporate users won’t need to 2 From the Library of Lee Bogdanoff 3 Why This Book? worry about them. For the remaining features, we tell you when certain features do or don’t apply to your particular version of Windows 7. (And we show you how to upgrade from one version to a better version, if you want the features your copy doesn’t have!) In this book’s many pages, we focus not just on the gee-whiz side of the technology, but why you should care, what you can get from it, and what you can forget about. The lead author on this book has previously written 17 books about Windows, all in plain English (several bestsellers), designed for everyone from rank beginners to full-on system administrators deploying NT Server domains. The coauthor has designed software and networks for more than 20 years and has been writing about Windows for 10 years. We work with and write about various versions of Windows year in and year out. We have a clear understanding of what confuses users and system administrators about installing, configuring, or using Windows, as well as (we hope) how to best convey the solu- tions to our readers. While writing this book, we tried to stay vigilant in following four cardinal rules: •Keep it practical. •Keep it accurate. •Keep it concise. •Keep it interesting, and even crack a joke or two. We believe that you will find this to be the best and most comprehensive book available on Windows 7 for intermediate through advanced users. And whether you use Windows 7 yourself or support others who do, we firmly believe this book will address your questions and needs. Our book addresses both home and business computer users. We assume you probably are not an engineer, and we do our best to speak in plain English and not snow you with unexplained jargon. As we wrote, we imagined that you, our reader, are a friend or co-worker who’s familiar enough with your computer to know what it’s capable of, but might not know the details of how to make it all happen. So we show you, in a helpful, friendly, professional tone. In the process, we also hope to show you things that you might not have known, which will help make your life easier—your com- puting life, anyway. We spent months and months poking into Windows 7’s darker corners so you wouldn’t have to. And, if you’re looking for power-user tips and some nitty-gritty details, we make sure you get those, too. We try to make clear what information is essential for you to understand and what is optional for just those of you who are especially interested. We’re also willing to tell you what we don’t cover. No book can do it all. As the title implies, this book is about Windows 7. We don’t cover setting up the Server versions of this operating system, called Windows 2000 Server, Windows Server 2003, and Windows Server 2008. However, we do tell you how to connect to and interact with these servers, and even other operating systems, including Mac OS X, Linux, and older variants of Windows, over a local area network. Because of space limitations, there is only one chapter devoted to coverage of Windows 7’s numer- ous command-line utilities, its batch file language, Windows Script Host, and Windows PowerShell. For that (in spades!), you might want to check Brian’s book Windows 7 and Vista Guide to Scripting, Automation, and Command Line Tools, which is due to be published in the fall of 2009. From the Library of Lee Bogdanoff Introduction Even when you’ve become a Windows 7 pro, we think you’ll find this book to be a valuable source of reference information in the future. Both the table of contents and the very complete index will provide easy means for locating information when you need it quickly. How Our Book Is Organized Although this book advances logically from beginning to end, it’s written so that you can jump in at any location, quickly get the information you need, and get out. You don’t have to read it from start to finish, nor do you need to work through complex tutorials. This book is broken down into seven major parts. Here’s the skinny on each one: Part I, “Getting Started with Windows 7,” introduces Windows 7’s new and improved features and shows you how to install Windows 7 on a new computer or upgrade an older version of Windows to Windows 7. It also shows you how to apply service packs to keep your version of Windows 7 up-to- date. Finally, we take you on a one-hour guided tour that shows you the best of Windows 7’s fea- tures and walks you through making essential settings and adjustments that will help you get the most out of your computer. In Part II, “Using Windows 7,” we cover the core parts of Windows 7, the parts you’ll use no matter what else you do with your computer: managing documents and files, using the Windows desktop, starting and stopping applications, searching through your computer’s contents, printing, and using the desktop gadgets and other supplied accessories. Don’t skip this section, even—or rather, espe- cially—if you’ve used previous versions of Windows. Windows 7 does many things differently, and you’ll want to see how to take advantage of it! Windows 7 has great tools for viewing, playing, creating, editing, and managing music, movies, and pictures. In Part III, “Multimedia and Imaging,” we show you how to use the new Windows Media Player, burn CDs, extract and edit images from cameras and scanners, send faxes, and create DVDs. Finally, we show you how to use Windows Media Center, which lets you view all that stuff and, on a properly equipped computer, record and play back your favorite TV shows. We even show you how to burn DVDs from your recorded shows and discuss compression options for storage consider- ations and format options for playback on other devices. In Part IV, “Windows 7 and the Internet,” we first help you set up an Internet connection and then move on to explain Windows 7’s Internet tools. We provide in-depth coverage of the new and improved (and safer!) Internet Explorer. The final chapter shows you how to diagnose Internet con- nection problems. Networks used to be found only in high-falutin’ offices and corporate settings. Now, any home or office with two or more computers should have a network. A LAN is inexpensive, and with one you can share an Internet connection, copy and back up files, and use any printer from any computer. In Part V, “Networking,” we walk you through setting up a network in your home or office, and show you how to take advantage of it in day-to-day use. We also show you how easy it is to share a DSL or cable Internet connection with all your computers at once, show you how to network with other operating systems, and, finally, help you fix it when it all stops working. Part VI, “Maintaining Windows 7,” covers system configuration and maintenance. We tell you how to work with the Control Panel and System Administration tools, provide tips and tricks for cus- tomizing the graphical user interface to maximize efficiency, explain how to manage your hard disk 4 From the Library of Lee Bogdanoff 5 Conventions Used in This Book and other hardware, and describe a variety of ways to upgrade your hardware and software (includ- ing third-party programs) for maximum performance. We show you how to troubleshoot hardware and software problems, edit the Windows Registry, and, for real power users, how to use and tweak the command-line interface. When Windows was introduced over two decades ago, computer viruses, online fraud, and hacking were only starting to emerge as threats. Today (thanks in great part to gapingsecurity holes in pre- vious versions of Windows), computer threats are a worldwide problem, online and offline. In Part VII, “Security,” we provide a 360-degree view of Windows 7’s substantial improvements in security. Here you’ll find out both what Windows 7 will do to help you, and what you must do for yourself. We cover protection against viruses and spyware, loss and theft, hackers and snoops, and fraud and spam—in that order. Part VIII, “Windows On the Move,” shows you how to get the most out of Windows 7 when either you or your computer, or both, are on the go. We show you how to use wireless networking safely, how to get the most out of your laptop, and how to connect to remote networks. We also show you how to use Remote Desktop to reach and use your own computer from anywhere in the world. We finish up with a chapter about the cutting edge in laptops and desktops—pen and touch computing using the Tablet-PC features of Windows 7. Appendix A, “Using Virtualization on Windows 7,” explains how to use a newly released, free ver- sion of the Microsoft Virtual PC program to run older XP programs under Windows 7. For some users, this can be an excellent alternative to creating a dual-boot system with XP and Windows 7.
Introduction Like many of my colleagues in this industry, I learned Windows programming from Charles Petzold's Programming Windows—a classic programming text that is the bible to an entire generation of Windows programmers. When I set out to become an MFC programmer in 1994, I went shopping for an MFC equivalent to Programming Windows. After searching in vain for such a book and spending a year learning MFC the old-fashioned way, I decided to write one myself. It's the book you hold in your hands. And it's the book I would like to have had when I was learning to program Windows the MFC way. MFC, as you probably already know, is Microsoft's C++ class library for Windows programming. Programming Windows with MFC isn't a book about C++; rather, it's a book about writing 32-bit Windows applications in C++ using MFC rather than the Windows API as the chief means of accessing the operating system's essential features and services. It was written with two kinds of people in mind: Windows API programmers who want to learn MFC Programmers who have never before programmed Windows Whichever camp you fall into, I assume that you know the C++ programming language already and are comfortable with basic C++ idioms such as derived classes and virtual functions. If these assumptions are true, you're ready to begin climbing the hill that is MFC programming. Even veteran Windows programmers frequently find MFC code confusing the first time they see it, in part because of the presence of code created by the MFC code-generating wizards in Visual C++ and in part because of the countless lines of code hidden away in MFC classes such as CFrameWnd, CDocument, and CView. That's why this book takes a rather unusual approach to teaching MFC. It begins by having you write MFC code by hand (without the wizards) and by utilizing MFC 1.0-style application architectures—that is, applications that use neither documents nor views. Only after you've mastered the fundamentals and become acquainted with basic MFC classes such as CWnd and CWinApp do I introduce the wizards and teach you how to take advantage of MFC's document/view architecture. Along the way, you build a understanding from the ground up of the message-oriented nature of Windows and of key components of Windows itself, such as the Graphics Device Interface (GDI). I believe that this approach makes learning MFC not only less intimidating, but also more enjoyable. I think that you'll agree once you've worked your way through the book and can look back on the learning experience from the standpoint of a knowledgeable Windows programmer. Programming Windows with MFC is divided into four parts. Part I introduces the core tenets of MFC and Windows programming, beginning with a simple "Hello, MFC" application and introducing, one by one, menus, controls, dialog boxes, and other application building blocks. Part II builds on the foundation laid in Part I with a detailed look at the document/view architecture. In particular, Chapters 9, 10, and 11 reveal much of the "magic" behind documents and views and explain not only how to write basic document/view applications but also how to implement some not so basic features such as split-window views of a document and print previews. Part III covers some of the more advanced features of Windows and MFC—features such as color palettes, bitmap handling, and multiple threads of execution. In Part IV, you'll learn how MFC wraps its arms around COM, OLE, and ActiveX and how to write COM-enabled applications and software components. By the time you're finished with Chapter 21, you'll be well versed in the art of 32-bit Windows programming using MFC. And you'll have prodigious amounts of sample code to draw from when it's time to strike out on your own and write your first great Windows application. What's New in the Second Edition Those of you who read the first edition of this book will notice two rather obvious changes in the second edition. First, this edition contains seven new chapters. One is devoted to the MFC view classes; another covers the MFC collection classes; one introduces MFC file I/O and serialization mechanisms; and four cover the relationship between MFC and COM. MFC is not the general-purpose COM framework that the Active Template Library (ATL) is, but MFC makes certain types of COM programming exceptionally easy. For example, MFC greatly simplifies the task of writing ActiveX controls, and it makes writing Automation servers—programs that use COM to expose their functionality to scripting clients—a breeze. The second major change in this edition has to do with wizards. The first edition didn't cover the MFC wizards at all. The second edition uses hand-generated code in Chapters 1 through 3 but then shifts gears and begins using AppWizard and ClassWizard in Chapter 4. Why the change of heart? I still believe that code-generating wizards are an impediment to learning and should be used only by knowledgeable programmers, but I've also come to realize that in the real world, MFC programmers use the wizards. For certain tasks—writing ActiveX controls, for example—it doesn't make sense not to use the wizards. So after much deliberation, I decided I would be remiss not to cover them. Despite the new material regarding wizards, however, this is not—and never will be—a book about clicking buttons in AppWizard. After introducing a fundamental skill, such as how to write a message handler with ClassWizard, I thereafter let the source code do the talking and assume that you can figure out how the source code was created. Keep in mind that the wizards never do anything you can't do yourself, so it's perfectly feasible to type in every source code listing by hand if you'd like to. The downside to using wizards in a book that teaches MFC programming is that they produce code that isn't fit to publish. The first edition of this book included printed listings for each and every source code file. This one does not. It contains printed copies of relevant source code files and provides the others on CD. Why? Because printing a source code file that's 50 percent meat and 50 percent fat adds bulk to a book without adding content. Some of the code produced by the MFC AppWizard in Visual C++ 6.0 won't even compile. (For details, see Chapter 4.) I'm not very proud of the parts of my book that the wizards created, because those portions are littered with arbitrary blank lines, comments that lack consistent style, and unnecessary functions. For someone who takes pride in writing concise, readable sample code, wizard output is a bitter pill to swallow. Nevertheless, wizards represent the new world order in Windows programming, and they're something that you, I, and everyone else must get used to. It's a shame that the Visual C++ team won't give us real wizards to play with instead of the toys that they pass off as wizards today. Until they do, we must make do with what we have. What's On the CD The CD that accompanies this book contains source code and executables for all the sample programs presented in the book. All samples were written and compiled with Visual C++ 6.0 and MFC 6.0 and tested on various Win32 platforms. Unless otherwise noted, all are compatible with Windows 98, Windows NT 4.0, and Windows 2000. Most are also compatible with Windows 95 and Windows NT 3.51. You can copy the contents of the CD to your hard disk by running the setup program found in the CD's root directory, or you can retrieve the files directly from the CD's \Code directory. The \Code directory contains one subdirectory for each chapter of the book—Chap01, Chap02, and so on. Inside these subdirectories you'll find the sample programs. Each set of source code files is accompanied by a release-build EXE as well as a Visual C++ workspace (DSW) file that you can open with Visual C++'s Open Workspace command. From Me to You (and You to Me) From the day in 1995 when I began writing the first edition of Programming Windows with MFC, my goal has been to provide C++ programmers with the same kind of timeless, irreplaceable resource that Programming Windows is to C programmers. Whether I've achieved that goal, I'll let you be the judge. I want to know what you think about Programming Windows with MFC, and I particularly want to hear from you if you find mistakes. You can reach me by sending mail to jeffpro@msn.com or by visiting my Web site at www.prosise.com. At that site you'll find up-to-date information regarding the book, a list of errata, and information about other projects that I'm working on. Later this year, I plan to post a brand new chapter on MFC DLLs that you can read and comment on online. With the huge volume of computer books vying for buyers' attention in bookstores today, I know that you could have chosen any number of MFC books besides this one. I thank you for purchasing Programming Windows with MFC, and I sincerely hope you conclude that your money was well spent. Enjoy! Jeff Prosise
VC技术内幕第五版.chm Introduction Like many of my colleagues in this industry, I learned Windows programming from Charles Petzold's Programming Windows—a classic programming text that is the bible to an entire generation of Windows programmers. When I set out to become an MFC programmer in 1994, I went shopping for an MFC equivalent to Programming Windows. After searching in vain for such a book and spending a year learning MFC the old-fashioned way, I decided to write one myself. It's the book you hold in your hands. And it's the book I would like to have had when I was learning to program Windows the MFC way. MFC, as you probably already know, is Microsoft's C++ class library for Windows programming. Programming Windows with MFC isn't a book about C++; rather, it's a book about writing 32-bit Windows applications in C++ using MFC rather than the Windows API as the chief means of accessing the operating system's essential features and services. It was written with two kinds of people in mind: Windows API programmers who want to learn MFC Programmers who have never before programmed Windows Whichever camp you fall into, I assume that you know the C++ programming language already and are comfortable with basic C++ idioms such as derived classes and virtual functions. If these assumptions are true, you're ready to begin climbing the hill that is MFC programming. Even veteran Windows programmers frequently find MFC code confusing the first time they see it, in part because of the presence of code created by the MFC code-generating wizards in Visual C++ and in part because of the countless lines of code hidden away in MFC classes such as CFrameWnd, CDocument, and CView. That's why this book takes a rather unusual approach to teaching MFC. It begins by having you write MFC code by hand (without the wizards) and by utilizing MFC 1.0-style application architectures—that is, applications that use neither documents nor views. Only after you've mastered the fundamentals and become acquainted with basic MFC classes such as CWnd and CWinApp do I introduce the wizards and teach you how to take advantage of MFC's document/view architecture. Along the way, you build a understanding from the ground up of the message-oriented nature of Windows and of key components of Windows itself, such as the Graphics Device Interface (GDI). I believe that this approach makes learning MFC not only less intimidating, but also more enjoyable. I think that you'll agree once you've worked your way through the book and can look back on the learning experience from the standpoint of a knowledgeable Windows programmer. Programming Windows with MFC is divided into four parts. Part I introduces the core tenets of MFC and Windows programming, beginning with a simple "Hello, MFC" application and introducing, one by one, menus, controls, dialog boxes, and other application building blocks. Part II builds on the foundation laid in Part I with a detailed look at the document/view architecture. In particular, Chapters 9, 10, and 11 reveal much of the "magic" behind documents and views and explain not only how to write basic document/view applications but also how to implement some not so basic features such as split-window views of a document and print previews. Part III covers some of the more advanced features of Windows and MFC—features such as color palettes, bitmap handling, and multiple threads of execution. In Part IV, you'll learn how MFC wraps its arms around COM, OLE, and ActiveX and how to write COM-enabled applications and software components. By the time you're finished with Chapter 21, you'll be well versed in the art of 32-bit Windows programming using MFC. And you'll have prodigious amounts of sample code to draw from when it's time to strike out on your own and write your first great Windows application. What's New in the Second Edition Those of you who read the first edition of this book will notice two rather obvious changes in the second edition. First, this edition contains seven new chapters. One is devoted to the MFC view classes; another covers the MFC collection classes; one introduces MFC file I/O and serialization mechanisms; and four cover the relationship between MFC and COM. MFC is not the general-purpose COM framework that the Active Template Library (ATL) is, but MFC makes certain types of COM programming exceptionally easy. For example, MFC greatly simplifies the task of writing ActiveX controls, and it makes writing Automation servers—programs that use COM to expose their functionality to scripting clients—a breeze. The second major change in this edition has to do with wizards. The first edition didn't cover the MFC wizards at all. The second edition uses hand-generated code in Chapters 1 through 3 but then shifts gears and begins using AppWizard and ClassWizard in Chapter 4. Why the change of heart? I still believe that code-generating wizards are an impediment to learning and should be used only by knowledgeable programmers, but I've also come to realize that in the real world, MFC programmers use the wizards. For certain tasks—writing ActiveX controls, for example—it doesn't make sense not to use the wizards. So after much deliberation, I decided I would be remiss not to cover them. Despite the new material regarding wizards, however, this is not—and never will be—a book about clicking buttons in AppWizard. After introducing a fundamental skill, such as how to write a message handler with ClassWizard, I thereafter let the source code do the talking and assume that you can figure out how the source code was created. Keep in mind that the wizards never do anything you can't do yourself, so it's perfectly feasible to type in every source code listing by hand if you'd like to. The downside to using wizards in a book that teaches MFC programming is that they produce code that isn't fit to publish. The first edition of this book included printed listings for each and every source code file. This one does not. It contains printed copies of relevant source code files and provides the others on CD. Why? Because printing a source code file that's 50 percent meat and 50 percent fat adds bulk to a book without adding content. Some of the code produced by the MFC AppWizard in Visual C++ 6.0 won't even compile. (For details, see Chapter 4.) I'm not very proud of the parts of my book that the wizards created, because those portions are littered with arbitrary blank lines, comments that lack consistent style, and unnecessary functions. For someone who takes pride in writing concise, readable sample code, wizard output is a bitter pill to swallow. Nevertheless, wizards represent the new world order in Windows programming, and they're something that you, I, and everyone else must get used to. It's a shame that the Visual C++ team won't give us real wizards to play with instead of the toys that they pass off as wizards today. Until they do, we must make do with what we have. What's On the CD The CD that accompanies this book contains source code and executables for all the sample programs presented in the book. All samples were written and compiled with Visual C++ 6.0 and MFC 6.0 and tested on various Win32 platforms. Unless otherwise noted, all are compatible with Windows 98, Windows NT 4.0, and Windows 2000. Most are also compatible with Windows 95 and Windows NT 3.51. You can copy the contents of the CD to your hard disk by running the setup program found in the CD's root directory, or you can retrieve the files directly from the CD's \Code directory. The \Code directory contains one subdirectory for each chapter of the book—Chap01, Chap02, and so on. Inside these subdirectories you'll find the sample programs. Each set of source code files is accompanied by a release-build EXE as well as a Visual C++ workspace (DSW) file that you can open with Visual C++'s Open Workspace command. From Me to You (and You to Me) From the day in 1995 when I began writing the first edition of Programming Windows with MFC, my goal has been to provide C++ programmers with the same kind of timeless, irreplaceable resource that Programming Windows is to C programmers. Whether I've achieved that goal, I'll let you be the judge. I want to know what you think about Programming Windows with MFC, and I particularly want to hear from you if you find mistakes. You can reach me by sending mail to jeffpro@msn.com or by visiting my Web site at www.prosise.com. At that site you'll find up-to-date information regarding the book, a list of errata, and information about other projects that I'm working on. Later this year, I plan to post a brand new chapter on MFC DLLs that you can read and comment on online. With the huge volume of computer books vying for buyers' attention in bookstores today, I know that you could have chosen any number of MFC books besides this one. I thank you for purchasing Programming Windows with MFC, and I sincerely hope you conclude that your money was well spent. Enjoy! Jeff Prosise March 12, 1999
Introduction Welcome to .NET and Visual Basic .NET.As you already know, .NET is a name for a new strategy: a blueprint for building applications for the next decade. It’s actually even more than that. It’s Microsoft’s commitment to remain at the top of a rapidly changing world and give us the tools to address the needs of tomorrow’s computing. Visual Basic .NET is a language for creating .NET applications, like many others. It also happens that Visual Basic is the easiest to learn, most productive language (but you already know that). Visual Basic .NET is released shortly after the tenth anniversary of the first version of VB. The original language that changed the landscape of computing has lasted for 10 years and has enabled more programmers to write Windowsapplication than any other language. Programmers who invested in Visual Basic 10 years ago are in demand today. In the world of computing, how- ever, things change very fast, including languages. At some point, they either die, or they evolve into something new. Visual Basic was a language designed primarily for developing Windows applications. It was a simple language, because it managed to hide many of the low-level details of the operating system. Those who wanted to do more with Visual Basic had to resort to Win- dows API. In a way, earlier versions of Visual Basic were ‘sandboxed’ to protect developers from scary details. Microsoft had to redesign Visual Basic. The old language just didn’t belong in the .NET pic- ture (at least, it wouldn’t integrate very well into the picture). Visual Basic .NET is not VB7; it’s a drastic departure from VB6, but a necessary departure. Visual Basic .NET was designed to take us through the next decade of computing, and if you want to stay ahead, you will have to invest the time and effort to learn it. The most fundamental component of the .NET initiative is the .NET Framework, or simply the Framework. You can think of the Framework as an enormous collection of functions for just about any programming task. All drawing methods, for example, are part of the System.Drawing class. To draw a rectangle, you call the DrawRectangle method, passing the appropriate argu- ments. To create a new folder, you call the CreateDirectory method of the Directory class; to retrieve the files in a folder, you call the GetFiles method of the same object. The Framework contains all the functionality of the operating system and makes it available to your application through numerous methods. VB was such a success because it was a very simple language. You didn’t have to learn a lot before you could start using the language. Being able to access the Framework’s objects means that you’re no longer limited by the language. The new version of the language unlocks the full potential of .NET; now there’s hardly anything you can do with another language but can’t do 2877c00.qxd 11/11/01 4:13 PM Page xxiii INTRODUCTION xxiv with Visual Basic. This makes the language as powerful as any other language, but it also makes the learning curve steeper. The good news is that, if you get started today, you’ll get a head start, which may well last for another decade. Who Should Read This Book? You don’t need to know Visual Basic to read Mastering Visual Basic .NET,but you do need a basic understanding of programming. You need to know the meaning of variables and functions and how an If…Thenstructure works. This book is addressed to the typical programmer who wants to get the most out of Visual Basic. It covers the topics I feel are of use to most VB programmers, and it does so in depth. Visual Basic .NET is an extremely rich programming environment, and I’ve had to choose between superficial coverage of many topics and in-depth coverage of fewer topics. To make room for more topics, I have avoided including a lot of reference material and lengthy listings. For example, you won’t find complete project listings or Form descriptions. I assume you can draw a few controls on a Form and set their properties, and you don’t need long descriptions of the properties of the control. I’m also assuming that you don’t want to read the trivial segments of each application. Instead, the listings concentrate on the “meaty” part of the code: the procedures that explain the topic at hand. If you want to see the complete listing, it’s all on the CD. The topics covered in this book were chosen to provide a solid understanding of the principles and techniques for developing applications with Visual Basic. Programming isn’t about new key- words and functions. I chose the topics I felt every programmer should learn in order to master the language. I was also motivated by my desire to present useful, practical examples. You will not find all topics equally interesting or important. My hope is that everyone will find something interesting and something of value to their daily work—whether it’s an application that maps the folders and files of a drive to a TreeView control, an application that prints tabular data, or an application that saves a collection of objects to a file. Many books offer their readers long, numbered sequences of steps to accomplish something. Fol- lowing instructions simplifies certain tasks, but programming isn’t about following instructions. It’s about being creative; it’s about understanding principles and being able to apply the same techniques in several practical situations. And the way to creatively exploit the power of a language such as Visual Basic .NET is to understand its principles and its programming model. In many cases, I provide a detailed, step-by-step procedure that will help you accomplish a task, such as designing a menu. But not all tasks are as simple as designing menus. I explain why things must be done in a certain way, and I present alternatives and try to connect new topics to those explained earlier in the book. In several chapters, I expand on applications developed in earlier chap- ters. Associating new knowledge to something you have already mastered provides positive feedback and a deeper understanding of the language. This book isn’t about the hottest features of the language; it’s about solid programming tech- niques and practical examples. For example, I’m not going to show you how to write multithreaded applications. The real challenge with multithreaded applications is their debugging, which requires substantial experience. Once you master the basics of programming Windowsapplications with Visual Basic .NET and you feel comfortable with the more advanced examples of the book, you will find it easy to catch up with the topics that aren’t discussed.

6,849

社区成员

发帖
与我相关
我的任务
社区描述
Windows 2016/2012/2008/2003/2000/NT
社区管理员
  • Windows Server社区
  • qishine
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧