This article series emphasizes the importance of understanding memory management and proper usage of the IDisposable interface in .NET code. Part 3 focuses on using various tools and Visual Studio extensions to identify and resolve memory and disposable-related issues in the codebase. While these tools can be helpful, manual analysis and adoption of memory profiler tools are also necessary to uncover all potential problems and improve the overall performance of .NET applications.
These articles will show when you need to use globalization, even when the performance might not be the best. Believe me, you will thank me later. I typically do not use globalization patterns for application logging. Updated February 2023.
There isn't a perfect application ever released, and the same is true for Visual Studio 2022. There are a lot of great features in VS2022, but there are many issues too. So I decided to create a running list of the issues that I find or find frustrating.
On show #38 of Rockin' the Code World with dotNetDave, I am ranting about far too many .NET software engineers DO NOT understand how memory management works when it comes to disposable objects! Not matter what level of software engineer you are, you need to watch this episode... NOW!
Join me live on Saturday, August 28th, 2021 at 10:00 PST on C# Corner Live for season 2, show #35 where I will interview Darrell Dunn, Solutions Architect with OverOps.
The dotNetDave For Those About To Code: Worldwide Tour will be at the GLUGnet User Group in Okemos, MI on August 19th at 6 PM EDT. I hope you will join me at this meeting. This meeting will be virtual, but I wish it was in person. My session will be followed by a Q&A where you can ask me anything!
The focus on code and application performance has become crucial due to the shift to cloud systems. Inefficient code can increase costs and drive users away. Performance should be prioritized in the design phase, as it directly impacts revenue, cloud expenses, and user trust. Build efficient software from the beginning.
I have been analyzing code for issues for a very long time. In this article, I will share what I found at a recent contract I was working on. I have analyzed some bad solutions in my career, and this is hands down one of the worse I have done in recent memory. I will show you just some of the over 7K violations. The biggest issue with this solution, which is in production, is the very poor architecture it has. Honestly, I do not know if there was any architecture for these 7 projects.
Analyze has been available in most of the Visual Studio editions for a long time and is based on FxCop. This article will discuss how to set it up and use it properly.
The dotNetDave For Those About To Code: Worldwide Tour will be at the Tech Valley .NET User Group (TVUG) in Latham, NY on August 10, 2021.
dotNetTips.com 
You must be logged in to post a comment.