OOP: Building Reusable Components with Microsoft Visual Basic .NET

Object Oriented Programming (OOP) is now a reality with Microsoft Visual Basic .NET. This hands-on reference teaches professional programmers the proven, real-world strategies for constructing rich, object-oriented frameworks for complex business applications-faster and more efficiently. Focusing on a crucial problem many businesses face today, the shortage of skilled application developers, this book details how to quickly create reusable code components using Visual Basic.NET. All the book's code examples are contained on a companion CD-ROM.

User review
This book is 99% crap.
I have 2 bookshelves of bargain .net books. This is by far the worst on the whole collection.

I was expecting a book on component building. What I got was a walkthrough of building a clunky enterprise application. For component building, I reccommend the Apress! Class design Handbook as a starting point.

Despite the inappropriate title, I read on and found poor practice after poor practice. If I were tasked with maintaining the resulting application, I would schedule a re-write from scratch.

For a better insight about modern real world n-tier and component development, I recommend any of Rockford Lhotka's Business Objects books, especially the newer ones.

User review
Fantastic!
I found this book was very easy reading. The ASP.Net server controls are very good. I also use the Data Layer in all of my .Net applications. It's very solid code. Simply a great a read.

User review
No good . . .
Well, if you have absolutely NO experience with OOP and were looking for a good book to help you learn it . . . don't get this. :P

I think most of the practices in this book are poor. For example, and this is simply personaly opinion, there is a section on using a data access layer that they wrote (I think it stinks). Hardly a very good DAL in my opinion. The thing I don't like about it is when they tell you to use it from other layers, you still have to know about this concept of SQLServer, connection strings, stored procedures, and parameters, and that is just lame. When I write a DAL, I abstract that stuff out. How in the world would I cleanly swap my DAL out if I wanted to go from SQL Server to Oracle?! Well, using their techniques it seems that I would have to go through the code in my other layers and change quite a bit . . . Horrible!

Then, when they talk about using a security layer, they say this: `Our first thought was to create the security layer and have ASP.NET developers simply place code to check the login status at the top of each page. This approach is fraught with problems because it places the responsibility on the developer to work out the security on each page and include it.` So, what do they do 2 paragraphs later? Tell you to put this header control that will handle it into EVERY page: `All the developer needs to do is put the header on the page and the page is secure.` Big deal, they abstract the security into one component, and then call that from this header. But the developer still needs to stick it in every page . . . (I personally would have used inheritence for this, but whatever works.)

All in all, I think this book is about 5% useful. Seems like a good article would have accomplished the same goal, I don't see that this book has much valuable information. Thankfully I didn't pay for it, just read it via O'Reilly's Safari Subscription service!

User review
Putting it all together
The .Net framework is huge. After professionally developing several web projects I had the nuts and bolts pretty much nailed. However, putting it all together into a sound model/approach is tough.

I wish I'd read this book earlier on because it would have saved me a lot of pain. After you're past the novice stage and have a handle on the VB.Net syntax and object model, this book is the next step. It contains lots of code snippets and you can download their entire code library used to build the sample apps but the real key here is learning a sound methology.

One review was critical of their approach. I disagree with his comments. This book offers not only a sound approach to application design using .Net (with some concentration on web development), n-tier architecture is accepted practice. The book offers a sound VB.Net implementation. Of course, it's hardly the only way and is a tad simplistic for the real world intranet apps I'm working on. But it should help intermediate programmers put it all together to move to the next level.

My only complaint is that I wish it contained more code details, some broader coverage, and was more advanced. But that's a personal gripe because by the time I'd picked this up I'd personally grown past its content through the school of hard knocks.

User review
#2 VB.NET book on my list
I have only read 9 books related to vb.net and most of them seem to be a copy of the MSDN library. This book is underrated but I found this book to be precise what I needed. It gives real world solutions, exploiting many of the .NET framework classes. While in other books only two or three chapters are of value this book is withinh the TOP on my list. This book is different because you are creating a full enterprise application, building different classes with specific purposes and then putting it together to have an End-product. It is this putting together that will help you understand the potentials of VB.NET