|
|
Debugging Microsoft .NET 2.0 Applications
Two issues make debugging in the Microsoft .NET environment difficult and time consuming. The first issue is that debugging has always been a self-taught skillyou've basically been on your own to figure it out. Even if you have a computer science degree, I'm willing to bet that you never took a single college class dedicated to debugging. Other than some esoteric subjects such as devising automatic program verification for languages that no one uses, or developing debuggers for wildly optimistic, massively parallel-processing computers, the science of debugging as it applies to commercial software doesn't seem to be popular with the educational establishment. Some professors point out that you shouldn't be writing code with bugs in the first place. Although that's an excellent point and an ideal we should all strive for, reality is a little different. Learning systematic, proven techniques for debugging won't prevent you from ever writing another bug, but following the practices in this book will help you limit the number of bugs you add to your code and to track down more quickly those bugs that do occur.
The second issue is that although many excellent books on specific .NET technologies are available, none of them cover debugging in enough depth to be useful. To debug any technology effectively, you have to know far more than a book focused on a specific technology provides. It's one thing to know how to write a Microsoft ASP.NET control that plugs into your ASP.NET page, but it's another thing entirely to be able to debug that ASP.NET control. To debug that ASP.NET control, you'll have to know the ins and outs of .NET and ASP.NET, how DLLs are put in the ASP.NET temporary cache, and how ASP.NET goes about finding those controls in the first place. Some books make it look easy to implement sophisticated features, such as remote database connections, by using the hot technology du jour, but when "db.Connect ("Foo")" fails in your programand it eventually willyou're on your own to find and mend the broken link in the technology chain. Moreover, although a few books on project management do discuss debugging, they tend to focus on managerial and administrative issues rather than on developers' concerns. Those books might include fine information about how to plan for debugging, but they don't help much when you're staring at a corrupted database or a constantly restarting ASP.NET worker process.
Download Link
All rights reserved. All other trademarks appearing on on this site are the property of their respective owners. We don't store any files on this server, we just index the link from the other website.
|
|
|
|
