Search

Search Tips

.NET Windows Forms in a Nutshell

By Ian Griffiths, Matthew Adams
March 2003
Pages: 896
Series: In a Nutshell
ISBN 10: 0-596-00338-2 | ISBN 13: 9780596003388
(Average of 3 Customer Reviews)

Description

.NET Windows Forms in a Nutshell offers an accelerated introduction to this next-generation of rich user interface development. The book provides an all-inclusive guide for experienced programmers along with a compact but remarkably complete reference to the .NET Framework Class Library (FCL) Windows Forms namespaces and types. Included on CD is an add-in that will integrate the book's reference directly into the help files of Visual Studio .NET.
Full Description

---

---

Featured customer reviews

Help in a book,  December 05 2006
Submitted by Anonymous Reader   [Respond | View]

hi,I have a q about your book. I agree that VS help is deficient in some ways, especially along VC++ lines. Does your book cover Windows Forms programming in Visual C++? I assume it does, since the cover does not mention any specific language.
But I thought I would ask before ordering it.
thanks


The Show NET Windows!,  September 30 2005
Submitted by Eduardo Cesar Lunardelli   [Respond | View]

It really looks at I I learned very with this book and together with others it is serving of base for the courses that I am lecionando in the institution that I minister my lessons.

Since that I started to read this workmanship I I am each time more intrigued with the chapters and the tips that are presented me.

I was with this book two months, and repassed the other professors.

One of them said me that the explanation detailed on the classroom is of congratulations!

Another one said that with the tips on as to instanciar classroom also they are perfect.

Another professor said that he intends to use this book in a visual project with its pupils of components.

My friend teacher spoke that this is important to give communications on as to develop graphical interfaces.

I say, that this book, net has the focus for that likes to aprendar the platform and the Microsoft focus.

We like this subject and them details!


Help in a book,  February 16 2005
Submitted by Anonymous Reader   [Respond | View]

Could you show some examples of where you felt we 'cut and paste' from the VS help? Since we wrote the whole book from scratch, I'll be very surprised if you are able to find any.

I am perplexed, but also intrigued to know specifically what it was that made you think that the book is simply a rehash of the VS Help.

Of course when it comes to the reference section, we cover all the same classes as Microsoft - but since the goal is to be comprehensive, the subject headings are necessarily the same. But the approach we took was different. Because Microsoft's documentation already provides a perfectly good reference to the class libraries, we chose not to duplicate this effort. Instead, we provided tips and pointers which are (or at least were at time of going to press) absent from Microsoft's help.

As a concrete example of our approach, consider System.ComponentModel.Component. Microsoft's documentation doesn't mention the design-time environment - it talks about abstract container relationships without ever explaining what you use it for in practice. This is a bizarre omission because designer integration is the main reason you would use this class. Also, Microsoft's documentation mentions the Dispose method, but neglects to mention the fact that there are two of them, and why. To support resource cleanup correctly, you need to be aware of this and the reasons behind it. Resource cleanup is the other major function of this class besides designer integration, so again we felt this was a significant omission on Microsoft's part, so our book's entry for Component covers this distinction. In short, reading Microsoft's entry for this class, it looks like it was written by someone who has never shipped a designable component, and didn't fully understand the reasoning behind the Dispose methods. Our entry for this same class was written by someone who has more experience than most in shipping Windows Forms solutions and dealing with designer integration issues. (Matthew Adams wrote this particular topic by the way, not me.) I believe our entry provides a more useful explanation of the Component class than the one in the VS help.

This example is typical of the approach we took - whenever we felt that the VS help was deficient in some way or could usefully be augmented, we filled the gaps. (And of course for many of the classes, there wasn't much to add. For these we have fairly perfunctory entries.) This is why I'm very surprised at your summary of the book, and would like to know specifically what parts you felt were, as you put it 'cut and paste' rather than the complementary approach in the example I just gave.

Read all reviews

• 
  

---

• Table of Contents
• Index
• Sample Chapter
• Release Notes
• Colophon
• Register Your Book
• View/Submit Errata
• View/Submit Review