In-Depth

Books: Debug VB.NET Apps

Debugging software systems is a necessary step to creating stable, low-defect software. Comprehensive VB.NET Debugging provides a roadmap that helps you avoid common traps and achieve your software goals.

Today's tools allow us to develop increasingly complicated and distributed software. However, the penalties of these advances come in the relative difficulty in creating stable and low-defect software. You must be increasingly diligent to avoid the traps and dangers associated with designing and developing software. In his book, Comprehensive VB.NET Debugging, Mark Pearce provides a roadmap to help you avoid these traps and achieve your software quality goals.

Debugging software systems has many dimensions depending on the type and style of your applications, and Pearce does a great job of addressing each one. The first four chapters are mandatory reading, because they lay the foundation for all the other chapters. Other chapters focus on specific topics; you'll have no trouble bouncing between chapters that interest you. In fact, Pearce covers almost every conceivable debugging topic, from basic debugging techniques and tools, to specific debugging practices for different types of applications.

Pearce also provides great insight into SQL Server, interop, multithreading, and distributed apps—areas that traditionally have been extremely difficult areas to master. Pearce assumes you're an intermediate to senior VB developer who has some prior knowledge and understanding of VB.NET, the CLR, and the .NET Framework. If you meet these criteria and you're looking to fine-tune your debugging skills, you simply can't go wrong with this book.


Comprehensive VB.NET Debugging
by Mark Pearce
Apress
ISBN: 1590590503
Price: $54.99
Quick Facts: Provides complete coverage of VB.NET debugging techniques when writing Windows Forms, ASP.NET, or XML Web services apps.
Pros: Covers the complete spectrum of debugging in VB.NET, including techniques on debugging SQL Server, multithreaded, and distributed systems. Covers virtually all debugging scenarios and additional debugging tools. Provides excellent examples and explanations.
Cons: Not well suited to an introductory audience.

About the Author

Joel Semeniuk is a founder of Imaginet Resources Corp., a Canada-based Microsoft Gold Partner. Currently, Joel is also serving as an Executive VP of Agile Project Management Tools at Telerik. He is also a Microsoft Regional Director and MVP Microsoft ALM, with a degree in Computer Science. With more than 18 years of experience, Joel specializes in helping organizations around the world realize their potential through maturing their software development and information technology practices. Joel is passionate about Application Lifecycle Management tooling, techniques and mindsets, and regularly speaks at conferences around the world on a wide range of ALM topics.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube