Performance: Code It Any Way You Want!

Back when .NET was first released in 2002, generally, there was only one way to code things. But now that we have the .NET Framework (Clr), .NET Core, and .NET, there can be many ways to code the same thing. The results in this article will focus on showing the different ways where there is very little difference in .NET 5.

dotNetDave Rocks The GLUGnet User Group

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!

dotNetDave Says... Memory Affects Performance and Performance Effects Memory!

dotNetDave Says… Memory Affects Performance and Performance Effects Memory!

When architecting and wring code, performance and memory usage should always be something that needs to be addressed. Especially since so much is being moved to the cloud. Performance and memory usage done improperly can dramatically increase the cost of cloud services. If performance is slow, YOU WILL LOOSE CUSTOMERS!

Not “Super” Code with Over 7,000 Violations

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.

Analyzing Code for Issues: .NET Memory Profiler

I have stated many, many times, “Performance affects memory and memory affects performance”. None of the code analysis tools I've written about will find every issue when it comes to memory and performance issue. The only way to find the rest is by using a memory profiler tool on running code near to production machine setup as possible.