Blog posts on .NET Software Development, C#, and Debugging on Michael's Coding Spot

I recently went through a series of job interviews for some of the biggest companies in tech.

When you’re using LINQ to work with a database the experience is kind of magical, right?.

Memory problems in a big .NET application are a silent killer of sorts.

Thanks for confirming your humanity!

You’re interested in ASP.NET, Got it!

You’re interested in C#, Got it!

You’re interested in debugging, Got it!

You’re interested in .NET memory, Got it!

You’re interested in .NET performance, Got it!

Please check your inbox to confirm your subscription!

Every once in a while you need to add meta functionality without actually changing the business logic code.

About a month ago I released my first book Practical Debugging for .NET Developers .

I don’t know about you, but reference conflicts in .NET led me to tears multiple times.

If you’re like me, then you’re addicted to productivity tools.

For almost a year now, I’ve been writing a book about debugging and problem-solving in .NET.

This article was originally written for the Ozcode blog .

For better or for worse, a senior .NET developer needs to understand how the .NET runtime loads assemblies.

Memory and performance are tightly coupled to each other in .NET.

One of the biggest memory-related problems and I daresay all-round problems in .NET, are memory leaks.

Memory problems are some of the most important and potentially devastating things in .NET.

This is a guest post written by Roy Green of The Sensor Shack , a free online resource for engineers to learn about different types of industrial sensors for measuring temperature, pressure, flow rate, displacement and more.

Back in the distant past, in a simpler time, version releases were very different from today.

Is C# slower than C++?

When it comes to debugging software, tools are extremely important.

There are many ways to communicate between a C# client and a C# server.

Welcome to michaelscodingspot.com I’m really happy you decided to join.

You’re sending an HTTP request to your ASP.NET server, and out of the blue, it returns a 500 error.

It’s not so rare to see weird things happen in 3rd party library code.

You might have heard about OzCode before.

One of the reasons modern computers are so fast is because of multi-core processors.

Performance issues never seem to disappear from the world, no matter how fast new computers become.

.NET Core 3 was recently released and brought with it a bunch of innovations.

There’s an incredible built-in mechanism in Windows called Performance Counters that allows you to follow a whole lot of useful metrics.

In this 3rd part of the series, we’ll continue our journey to explore multi-threaded pipeline pattern implementations in C#.

Logging is a big part of software development for many years now.

One of the most important concepts in modern programming is Exceptions.

This tutorial is part of a series: Part 1 – Getting started with Visual Studio Debugging Part 2 – Visual Studio Debugging Tool Windows In the previous tutorial, we saw some of the basics of debugging in Visual Studio.

In the First Part of the series, we talked about the Pipeline Pattern in programming.

The Pipeline pattern, also known as the Pipes and Filters design pattern is a powerful tool in programming.

I’ve been developing software for 10 years now.

Don’t know about you, but I’m obsessed about performance.

This tutorial is part of a series: Part 1 – Getting started with Visual Studio Debugging Part 2 – Visual Studio Debugging Tool Windows Unfortunately, writing code goes hand in hand with creating bugs.

In late 2007, C# 3.0 was released with some of the best features in the language.

In a .NET application, memory and performance are very much linked.

One of the most commonly used patterns in software development is Caching.

Software Engineering is very different from any other type of engineering.

I recently wrote 3 blog posts ([1] [2] [3] ) on different Producer/Consumer (Job Queues) implementations.

How many times did you use a desktop application to end up with a frozen unresponsive window?

Any experienced .NET developer knows that even though .NET applications have a garbage collector, memory leaks occur all the time.

In Part 1 and Part 2 we went over what are Job Queues, why they are so important and how to implement them with several methods.