Article Options
Premium Sponsor
Premium Sponsor

 »  Home  »  Windows Development  »  VB.NET Class Design - Inheritance
VB.NET Class Design - Inheritance
by Steven Sartain | Published  05/08/2003 | Windows Development | Rating:
Steven Sartain

Steven Sartain is a consultant currently designing and leading a VB.NET project using n-tier architecture and WebServices for Accuride International Ltd.

During his 8 year career as a developer and development lead, Steve has designed and implemented a diverse number of mission critical software solutions using VB, VBA, MS Access, C/C++, ASP, Delphi, DCOM & MTS, SQL Server, Oracle, SQL Anywhere and others. See his Resume for details.

He is also a Director of Iridium Software - a UK based bespoke software development house.

Steve is always open to take over a challenging programming opportunity. If you experience a need for a professional consultant who has all the necessary skills to take a proposition from first client meeting through to profitably and elegantly completed projects; I'm sure Steve could assist. See his Resume and Professional Statement for details.


View all articles by Steven Sartain...
VB.NET Class Design - Inheritance

Article PDF download: VB NET, Class Design Handbook - Inheritance

About a year ago I finished writing a book for Wrox regarding Visual Basic .NET Class Design concepts. The book was aimed at encouraging correct design principles with the new OO features of VB. Designing effective classes that don't need a huge amount of maintenance is a skill and the book was attempting to help bridge the gap that this skill required.

The truth is, it is impossible to write code in .NET that isn't OO as everything you do follows some form of inheritance. The book was aimed at those who were familiar with .NET, the Visual Basic language and basic OO concepts.

However, this isn't a plug for the book. After the demise of Wrox, any sales of the book don't benefit me so there is little point in plugging a book that I have little care in you buying :o)

When I first started working with Wrox they had no brief in order for me to work with and so the first couple of draft I produced never even made it into the book. The chapters were very good, just not what was required for the book. As they have been sitting on my hard drive now since then, and Wrox have now disappeared off the face of the earth - I thought I would release them privately. I was never paid to write these chapters and so am perfectly within my rights to publish them.

I hope you enjoy them both

Article PDF download: VB NET, Class Design Handbook - Inheritance

Related devCity.NET articles:

How would you rate the quality of this article?
1 2 3 4 5
Poor Excellent
Tell us why you rated this way (optional):

Article Rating
The average rating is: No-one else has rated this article yet.

Article rating:3.58974358974361 out of 5
 78 people have rated this page
Article Score34503
Sponsored Links