(Maybe Iāll get lucky and have Robert Scoble pick this up so it really gets wide distribution. š
Ā
Workās begun on the third edition of my debugging book.Ā I might be opening myself up to tons of mail, but Iām looking for a larger group of reviewers than Iāve had in the past. Ā Iād like to get a broader base of developers to look at the book so I can better appeal to the whole range of developers.Ā The number one complaint I heard about the previous book was that it was ātoo hard.āĀ That meant I didnāt effectively do my job and I want to fix that.
Ā
For this edition, Iām splitting the book into two books: one for .NET and one for Win32.Ā Iāll be doing the .NET version first and the title is changing to āDebugging, Testing, and Tuning .NET Applicationsā to reflect the new tools in VS.NET 2005. Ā Before I get tons of flame mail and comments from you Win32 folks, we will be working on the Win32 version as soon as I get the .NET one done. Ā Thereās only one of me and only so much time in the day. Ā I know I shouldnāt use sleep as a crutch, but waking up with my forehead on the keyboard gets old after a while. J
Ā
From the new title, you can see that Iāll be adding coverage for the new testing and performance tools in VS.NET 2005. Ā Iāve wanted to write more about those areas of debugging for a while. Ā To address the ātoo hardā problem, Iām adding a huge section that covers all sorts of common and not so common scenarios people run into and how to get started fixing them. Ā For example, if youāre seeing an OutOfMemoryException in a .NET application, Iāll discuss the steps you can take to start narrowing down the problem. Ā As part of the suggestions for tackling the problem Iāll point to parts of the book that go into deeper discussions, other books, web sites, blog entries, etc.Ā My hope is that by giving folks a starting point theyāll be able to take advantage of more the book and solve problems faster. Ā
Ā
If you have any suggestions or tricks I would LOVE to hear about them.Ā They can be big or as small as āProblem: My web service is timing out when debugging.āĀ āHints: Set the IIS HTTP timeout value to higher than the web service timeout as that take precedence. Ā (followed by the steps on setting the IIS timeout value).āĀ If you also have āWar Storiesā to share, Iām looking for more of them as well.
Ā
For those of you that loved the utilities, example code and hard core stuff, I certainly wonāt be getting rid of that!Ā I have ideas for all sorts of diagnostic tools, more Visual Studio .NET Add-Ins, and even deeper digging for this edition.Ā If youāve wanted a tool or know how something worked, shoot me a mail, as itās early enough in the cycle for me to possibly add it.
Ā
What Iām interested from the Review Crew are good reviews of the chapters for mistakes, clarity, and missing ideas.Ā Additionally, testing of the code would be extremely helpful (I want zero bugs in the code for this edition!).Ā From you Iām looking for the following:
1. Good reviews on the chapters
2. Provide good tricks
3. Find good bugs in the source code.Ā
Ā
Whatās in it for you?Ā Well, youāll get to read the book and see the code before anyone else.Ā Youāre prize package will also include:
1. A HUGE thank you in the acknowledgements
2. A free dinner at a great restaurant next time Iām in your area (or youāre in mine)
3. My total, eternal gratitude (if that counts for anything!)
4.Ā An autographed copy of the book
Ā
If youāre interested, send me an email (Iām ājohnā care of this company) with a short blurb about the type of .NET development youāre doing.Ā Additionally, please include how much overall development as well as .NET experience you have. Ā I want to ensure I get a broad range of folks from newer .NET developers, to super seasoned pros, to managers (yes, even managers!).Ā Please understand that I donāt have the bandwidth to handle everyone who wants to be a reviewer, so please donāt be disappointed if you arenāt selected.
Ā
When Jeff Prosise wrote his last book, he kept a book blog about what he was doing and it proved extremely popular. Ā Iāll be doing the same here in Wintellog so if youāve wanted to see what a different author is thinking as they struggle through a book, keep your readers pointed here.
Microsoft Azure and Amazon Web Services (AWS) are two of the most popular cloud platforms.…
ļ»æ Cloud management is difficult to do manually, especially if you work with multiple cloud…
Azureās scalable infrastructure is often cited as one of the primary reasons why it's the…
https://www.youtube.com/watch?v=wDzCN0d8SeA Watch our "Unlocking the Power of AI in your Software Development Life Cycle (SDLC)"…
FinOps is a strategic approach to managing cloud costs. It combines financial management best practices…
Using Kubernetes with Azure combines the power of Kubernetes container orchestration and the cloud capabilities…