Comments about oreilly Programming .NET Components:

I read little this book very, but, I know that here it will be the new phase of my evolution with C#.

Talking with my mentor in C#, it I said to me that when I will be domindo this book, I will be prepared for the new revolution that comes arriving WENT C#: Construtivismo in Went with C#.

Ours, this is opening my head in some parts, who intends to advance with components, does not lose time, but before if it prepares to understand what it will be reading!

Comments about oreilly Programming .NET Components:

Brilliant book! Every .NET developer must read and have it for personal reference.

This is a kind of book, I was looking for, for component programming in .Net.

Thanks a lot Juval!

Comments about oreilly Programming .NET Components:

An outstanding book.

The first three chapters gives you a brief intro to essential knowledge about what components is. I missed a references section though (other books treat the topic of components in general in more depth, and I suspect the author should have referenced a few of those).

The rest of the book is an excellent introduction to writing components using .NET and C#. What is special is the selection of code snippets. They are very short, but are targeted at showing the point, and only that.

This is one of the few books you can read from the first to the last page without doing some coding on the side to understand the contents. On top of that the writing is extremely fluent, clear and pedagogically constructed. At times there are even a bit of well placed humor.

I own around 20 books on .NET and C#. This is easily the best of them all.

Comments about oreilly Programming .NET Components:

When I was reading the first three chapters of this book I could have sworn that it was miss-titled; it should have been called Component Oriented Programming in .NET. Just so we get this straight, this is not a book about the wonderful components in the .NET Framework that Microsoft has provided -- this is a book about CREATING components in the .NET Framework.

The next item that needs to be clarified: What is a component? If you are from the Delphi/VCL world, a component is a non-visual object that can be manipulated in design-time with the mouse and the property browser, while usually being dragged onto a form (TTimer, TDatabase, TSession, TTable, etc). But in this book a component is a class -- the simpler the class, the better. No inheritance unless absolutely necessary, no class hierarchies, but interfaces are cool.

Now, once you get beyond the philosophy lessons of the first three chapters, you are left with one outstanding book on practical .NET development. The chapter on Events is worth the price of admission alone. The chapter on Versioning is excellent as well, but the rest of the sections are every bit as good.

Many of the topics covered in the book are not things you will find in the help files, or if they are, they are too scattered to be useful. What is covered: a large number of best practices, defensive coding techniques (again the chapter on Events is gold), and general you-really-need-to-know-this topics.

One note, some of the topics covered are very large (Remoting and Security are two examples), and if you are interested in those topics, there are other books that deal with them individually.

Summary: if you are into creating top-quality .NET software you should own this book.

Comments about oreilly Programming .NET Components:

This is the best book in C# I have seen. It is very practical, solved all the problems I am facing in work.