|
|
This training kit is designed for developers who plan to take Microsoft Certifi ed Technology Specialist (MCTS) exam 70-505, as well as for developers who need to know how to develop Microsoft Windows–based applications using the Microsoft .NET Framework 3.5. We assume that before you begin using this kit you have a working knowledge of Windows, Microsoft Visual Studio, and Microsoft Visual Basic or C#.
Windows Forms are the basic building blocks of the UI. They provide a container that hosts controls and menus and allow you to present an application in a familiar and consistent fashion. Forms can receive user input in the form of keystrokes or mouse interactions and can display data to the user through hosted controls. Although it is possible to create applications that do not contain forms, such as console applications or services, most applications that require sustained user interaction will include at least one Windows Form, and complex applications frequently require several forms to allow the program to execute in a consistent and logical fashion.
When you create a new Windows Forms project, a form named Form1 is added to your project by default. You can edit your form by adding controls and other visual elements in the Designer, which is a graphic representation of a designable, visual element (such as a Form) that appears in the Visual Studio Integrated Development Environment (IDE). The Visual Studio IDE is shown in Figure 1-1.
…..
This book has existed (in one form or another) since the first edition of C# and the .NET Platform was published in conjunction with the release of .NET 1.0 Beta 2, circa the summer of 2001. Since that point, I have been extremely happy and grateful to see that this text was very well received by the press and, most important, by readers. Over the years it was nominated as a Jolt Award finalist(I lost . . . crap!) and for the 2003 Referenceware Excellence Award in the programming book category (I won? Cool!).
Since that point, I have worked to keep the book current with each release of the .NET platform, including a limited printing of a Special Edition, which introduced the technologies of .NET 3.0 (Windows Presentation Foundation, Windows Communication Foundation, and Windows Workflow Foundation) as well as offered previews of several forthcoming technologies, which we now know as LINQ. The fourth edition of this text, which you hold in your hands, is a massive retelling of the previous manuscript to account for all of the major changes that are found within .NET 3.5. Not only will you find numerous brand-new chapters, you will find many of the previous chapters have been expanded in great detail.
…..
Any interactive application must have at least one window through which to present its user interface. In the Windows Forms framework, all such top-level application windows are represented by objects whose types derive from the Form class. As with any user interface element, the Form class inherits from the Control class, but it adds windowing features, such as management of the window border and interaction with the Windows taskbar. All Windows Forms applications have at least one class derived from Form.
In this chapter we will examine the structure of a typical Windows Forms application and the way its constituent forms are created. We will look at the programming model for forms, and the way that the Visual Studio .NET Forms Designer uses this model. We will look in detail at the relationship between a form and the controls it contains, and also at the relationships that can exist between forms. The mechanisms underpinning the automatic layout features described in the previous chapter will be examined, and we will see how to use these to add our own custom layout facilities
Making Object,Oriented Design Accessible
This book is an introduction to object-oriented design and design patterns at an elementary level. It is intended for students with at least one semester of programming in an object-oriented language such as Java or C++.
I wrote this book to solve a common problem. When students first learn an object-oriented programming language, they cannot be expected to instantly master object-oriented design. Yet, students should learn the principles of object-oriented design early enough to put them to work throughout the computer science curriculum.
This book is suitable for a second or third course in computer science-no background in data structures is required, and students are not assumed to have experience with developing large sof tware systems. Alternatively, the book can be used as a companion text in a course in sof tware engineering. (If you need a custom version of this book for integration into another course, please contact your Wiley sales representative.)
It’s difficult for me to write this foreword, not because the road to LINQ was long and arduous or that I’m teary-eyed, wrought with emotion, or finding it difficult to compose just the right the words for a send-off worthy of a product that I’ve poured my very soul into. It’s difficult because I know that this is going to be a well-respected book and I’m finding it tricky to work in a punch line.
For me the LINQ project started years before anything official, back when I was involved in plotting and scheming over a new managed ADO. Back then, a few very smart developers had the audacity to suggest shucking off the chains of traditional data access APIs and designing around the ubiquity of objects and metadata that were fundamental to the new runtime—the Java runtime. Unfortunately, none of that happened. The traditionalists won, and at the time I was one of
them. Yet what I gained from that experience was a perspective that data belongs at the heart of any programming system, not bolted on as an afterthought. It made sense that in a system based on objects, data should be objects too. But getting there was going to take overcoming a lot of challenges.
|
|
