I/O operations impact application responsiveness, scalability, and costs. Enhancing file access, HTTP requests, and networking improves user experience while reducing resource consumption. This chapter discusses techniques to optimize I/O performance in .NET, utilizing benchmark results and profilers to identify bottlenecks and improve efficiency in near-production environments.
Category: Code Quality
GitHub Copilot Agent for Unit Tests: My Real-World Spargine Experiment
After experimenting with the GitHub Copilot Agent during the 2026 Microsoft MVP Summit, the author faced numerous challenges, including code deletion, slow performance, and inconsistent adherence to coding conventions. Despite these issues, the agent added valuable unit tests to the Spargine projects, but it requires careful oversight and refining of prompts for effective use.
On .NET Live: How Coding Standards Supercharge .NET Quality & Performance
For the second time, I’m excited to be a guest on On .NET Live on May 18th at 9 AM PST! I’ll be talking about one of my favorite subjects: coding standards and how they can supercharge .NET code quality, performance, maintainability, and consistency across your projects. Join us live and bring your burning questions. … Continue reading On .NET Live: How Coding Standards Supercharge .NET Quality & Performance
Rock Your Code: I Let AI Build a Visual Studio Extension—Here’s What REALLY Happened
In March 2026, I challenged GitHub Copilot to build a Visual Studio extension, "Version Sync," from scratch without coding. Despite initial failures and needing extensive feedback, it succeeded in creating an extension to sync project version numbers. However, Copilot's code quality was lacking, emphasizing that AI can't replace experienced developers.
dotNetDave Says… Clear Naming Standards Create Clearer Code and Clearer Code Leads to Better Software
Clear naming standards in software development significantly enhance code readability, maintainability, and overall quality. Consistent naming reduces cognitive load, facilitates collaboration, and lowers long-term maintenance costs. Ignoring these standards leads to confusion, longer development times, and increased technical debt. Investing in robust naming conventions is essential for professional-grade software development.
dotNetDave Says… Rushing into Coding Without Proper Planning Will Lead to Costly Mistakes and Delays
Effective software projects require thorough planning and architecture before coding begins. Skipping these steps often leads to costly mistakes, delays, and technical debt. A strong foundation improves system maintainability and user satisfaction. Managers should focus on results over constant activity; proper planning enhances delivery speed and quality, fostering happier users.
Inside the AWS SDK for .NET: A Code Quality Wake-Up Call
The author critically reviews the AWS SDK for .NET, revealing alarming code quality issues, including 959,815 total violations and severe design flaws leading to potential memory leaks and resource management problems. Despite its popularity, the SDK presents significant risks for .NET developers, highlighting the importance of thorough assessment of open-source packages.
Visual Studio 2026: Regressions, Reliability Issues, and Missed Opportunities
Visual Studio 2026 has regressed by removing or disabling key code-quality features, making development more difficult. The Analyze tool suffers from inconsistencies and lack of reliability, while various testing functionalities are also flawed. AI tools like Copilot cannot replace essential code-quality features. Greater MVP involvement and thoughtful updates are needed to enhance the IDE.
Rock Your Code: Code & App Performance for Microsoft .NET (5th Edition)
The fifth edition of David McCarter's book, "Röck Yöur Cöde: Code & App Performance for Microsoft .NET," is now available on Amazon. It offers practical techniques for enhancing .NET application performance, including coding patterns, memory insights, and benchmarking. This definitive guide is essential for modern .NET developers aiming for speed and scalability.
Defensive Programming Rule #6: Verify Resource Availability (Before You Access It)
The article emphasizes the importance of defensive programming in .NET applications by validating resource availability before access. It outlines guidelines for checking connectivity, setting timeouts, and managing user experiences when resources are unavailable. The author shares personal insights and promotes Spargine, an open-source project designed to enhance defensive programming practices.

You must be logged in to post a comment.