Practical Standards for Microsoft® Visual Basic® .NET (Pro-Developer) (Paperback)

by James Foxall (Author) "If you or your development team creates numerous projects, you can save considerable development time and promote application consistently by creating and using object and..." (more)
Key Phrases: procedure comment header, custom setup program, single tab stop, End Sub, Private Sub, Select Case (more...)

Editorial Reviews

Product Description
Building on the popularity of this book's first edition, PRACTICAL STANDARDS FOR MICROSOFT VISUAL BASIC, the author shows developers and teams migrating to Visual Basic .NET how to save valuable time and resources-and writer faster, more manageable programs-by incorporating programming standards into Visual Basic .NET coding. Readers learn best practices for object-oriented programming, file operations, solution distribution, and more-with advice on how to apply these standards to their own projects.

Product Details

• Paperback: 458 pages
• Publisher: Microsoft Press (August 31, 2002)
• Language: English
• ISBN-10: 0735613567
• ISBN-13: 978-0735613560
• Product Dimensions: 9.1 x 7.2 x 1.6 inches
• Shipping Weight: 2.4 pounds
• Average Customer Review: 4.0 out of 5 stars See all reviews (14 customer reviews)
• Amazon.com Sales Rank: #590,743 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

7 of 7 people found the following review helpful:

3.0 out of 5 stars Somewhat rehashed VB standards book, January 7, 2003

By	Gregory A. Beamer "Cowboy" (Nashville, TN United States) - See all my reviews (REAL NAME)

After seeing the author jump in for a review, I decided I would add my two cents into this fray. While I do not agree with the 1 star "slam" that the author set out to counter, I think 3 stars may be pushing it, however.

There is a lot of practical advice in this book. While it should be obvious that a developer needs to set up templates without hard-coding and make all procedures perform very specific duties, we find that this is not the case in code. The book has quite a few good pieces of advice around the basic nature of programming. I will disagree with the author, however, on some points. For example, you should certainly minimize fan out (calling many procedures) for all but control functions, fan-in (multiple procedures using the same procedure) is a sign of very specialized functions, which he advised only two pages earlier.

This book has a whole chapter on naming conventions, using Hungarian. While this is not a cardinal sin, it should be noted that Microsoft has deprecated Hungarian in .NET. The inclusion in the book (chapter 4) suggests that the author has simply updated some of his material from his VB 6 book.

The suggestions for enumerators, commenting, looping and code flow are fairly decent and may help your coding efforts. Mr. Foxall falls a bit short on exception handling taking the tried and true route (see Richter's book for a better methodology). One item of contention is the idea that you handle unexpected as well as anticipated exceptions. In general, handle what you can and catch what you wish to log. Let the rest get handled on the UI to ensure the user does not get an ugly exception message. Most books on the market advocate catching everything, and then rethrowing the same error; what a waste of CPU cycles. In VB 6, you had to handle every exception, and pass it up the stack if you caught anything. In VB.NET, exception handling gives you the ability to catch those exceptions that you can handle or log for debugging a live application. Using finally, especially with objects with a dispose method, is a much better option.

I would agree with the 1 star reviewer on the coverage of modules before objects. Modules are a sloppy method of programming in Visual Basic .NET. They are placed in for VB 6 developers that miss their .bas files. On the other hand, this is not enough reason to kill the chapter, as some of the other advice in the chapter (2) is very useful.

A 2.5 rating would be a bit better as there is some bad advice in this book, but I have to choose between 2 and 3 and would rather give the author the benefit of the doubt. I hope Mr. Foxall has a chance to make a second version of the book that moves completely into the .NET paradigm, as it would be much more useful to developers.

4 of 4 people found the following review helpful:

4.0 out of 5 stars A Good Guide For All VB.NET Programmers, March 10, 2004

By	"lukeo" (Portland, OR USA) - See all my reviews

This is a good book for both the experienced and beginning Visual Basic .NET programmer.

The purpose of this book is not to show you how to write a program in VB.NET but to provide a style template on how you should write a program; not only for readability but also for maintainability. To that end Foxall provides many examples of "bad" programming practices and styles along with a suggested "good" one.

The whole argument about using Hungarian notation (HN) or not is really irreverent. The very fact that this book exists and is hopefully read by more than a handful of people means more consistency and more error-free code.

One of the things I appreciate in this book is the use of color (various shades of blue-green) to mark things like comments in code, section headers, etc.

Overall this book was an easy read and can easily be grasped by entry level VB.NET programmers and functional enough for more experienced programmers to reference.

6 of 7 people found the following review helpful:

5.0 out of 5 stars Perfect for beginners and Managers alike, November 7, 2002

By	Edwin Luciano (Salt Lake City, UT) - See all my reviews

With a new way of coding VB comes new ways of making the environment more effecient for programmers.

This book is full of good advice about programming practices in the .NET world. The advice is sound and could be even used as an intro since the author goes through great pains to make everthing clear while concise.

Should you follow all the advice? Depends on you. I don't think you should follow anybody's suggestions without some critical thought but the suggestions here are definitely worth taking a look at and debating. VB.NET ain't VB6 and you should not code and organize your code the way you did in VB6. Foxall gives us some good, pratical advice on how to code. More importantly, he gives great advice on how to organize code (something programmers tend to be bad at doing).

The only surprise was the recommendation to use Hungarian notation. I find it amusing that people get so hung up on Hungarian notation (I happen to like it but would not miss it if I never used it again). It's just a way to try to making code more readable when using local variables. If you think it gets in the way, then you shouldn't use it. Other than that confusing suggestion (MS says don't use Hungarian but you ARE free to use or not to use whatever convention you like) the book is flawless.

This is a book that every team doing VB.NET development should discuss if not follow. Standards are important, most of the software building cycle is in testing, debugging and modifying existing code. His standards are something to draw on as we come up with the best practices for our particular solutions.