We recently needed to parse and modify some query strings while building Request Metrics. Query string parsing has never been pleasant in .NET, has it improved in .NET Core? We were familiar with HttpUtility.ParseQueryString() for the task, but that API has a major landmine. With the release of .NET Core, Microsoft took another swing at it. We figured we’d try the new way and see how they did! If you want the fully uncensored version, check out the video above.
Rostyslav Kosmirak is a .NET developer from Ivano-Frankivsk, Ukraine using Rider and Visual Studio IDE. Kosmirak was not looking for a Dynamic Code Profiler when he came across Prefix. Kosmirak explains that initially he was searching through Google for a log management system when he stumbled on Prefix. Upon downloading, Kosmirak discovered hidden performance problems in his code before they manifested to actual performance problems.
“Object Reference Not Set to an instance of an object.” Cast the first stone those who never struggled with this error message when they were a beginner C#/.NET programmer. This infamous and dreaded error message happens when you get a NullReferenceException. This exception is thrown when you try to access a member—for instance, a method or a property—on a variable that currently holds a null reference. But what is a null reference?
Welcome to Stackify’s guide to C# exception handling. Why is this topic so important? In modern languages like C#, “problems” are typically modeled using exceptions. Jeff Atwood (of StackOverflow fame) once called exceptions “the bread and butter of modern programming languages.” That should give you an idea of how important this construct is.
It’s Friday afternoon, the majority of the development staff has already packed up and headed home for the weekend, but you remain to see the latest hotfix through to production. To your dismay, immediately after deployment, queues start backing up and you begin to get alerts from your monitoring system. Something has been broken and all evidence points to an application performance bottleneck.
After working with engineering teams of the leading companies in Java technology and receiving multiple requests to support more languages, we are excited to announce that we are expanding our support to the .NET ecosystem. Engineering teams building and delivering .NET Core and .NET Framework apps will now be able to leverage the power of OverOps to proactively identify, prevent, and resolve critical issues in their applications.
At Raygun, we’re a pretty polyglot group of developers. Various parts of Raygun are written in different languages and frameworks - whatever is best for the job. Given the vast amount of C# and the explosive growth in data we’re dealing with, some optimization work has been needed at various times. Most of the big gains come from really re-thinking a problem and approaching it from a whole new angle.