dotMemory Unit is a unit testing framework which allows you to write tests that check your code for all kinds of memory issues. You can now extend NUnit, MSTest or another .NET unit testing framework with the functionality of a memory profiler.
Perfect fit for any workflow: integrated with Visual Studio, works with stand-alone unit test runners, Continuous Integration ready. Last but not least, dotMemory Unit is free.
This week I was running into some memory issues with 3rd party library. I just stumbled up on dotMemory Unit and proved to be really useful to verify no memory leaks.
This repository shows an example of controlling NuGet package versions at the repository level, while at the same time ensuring that projects only opt into packages that they want.
This is fantastic. Ability to specify all the NuGet packages and the version that your solution projects can opt-in without having to worry about the version per project. This is especially useful when you have a solution with multiple projects that all need to reference the same NuGet package. This allows you to keep them in sync without having to worry keeping the versions in-sync across multiple csproj and <PackageRefernece>. Lovely.
We’ve updated WinDbg to have more modern visuals, faster windows, a full-fledged scripting experience, and Time Travel Debugging, all with the easily extensible debugger data model front and center. WinDbg Preview is using the same underlying engine as WinDbg today, so all the commands, extensions, and workflows you’re used to will still work as they did before.
I blogged about Troubleshoting Stackoverflow Exceptions, and WinDbg came in really handy. I first used the original version and then realized there is a new WinDbg in the Windows Store that has a much needed UI refresh.
I was lucky enough to present at this conference in 2017. I thought this was a great presentation and refer people to watch it all the time. Highly recommend if you are interested in Event Driven Architecture.
Explore DDD 2017 – Denver, Sept. 21-22 The real world, with all its complexity, can at the same time be simple, elegant and beautiful. It thrives on autonomy and asynchrony, the two most important things that bring order to chaos. The real world does not pause for something to complete before moving on. And yet, when we write software, “Command and Control” is the norm. We find clever ways of doing this while keeping up with all the new technologies and the languages in fashion, all the while ignoring the realities of life. In this session, explore an alternate universe in which Event Driven Architecture can power even the most complex mission-critical systems. Learn how communicating asynchronously via events leads to building systems that are autonomous and much more reliable. Embrace asynchrony and autonomy. Make the complex simple.
About Indu Indu Alagarsamy has been programming for over 15 years. She is currently part of the development team at Particular Software, the makers of NServiceBus, practicing her passion. Indu is also passionate about diversity and inclusiveness in the tech industry. When not programming, she is either rock climbing in sunny Southern California or having fun with her kids!
If you’re running full framework, you might want to check out the release notes to see if there are any improvements for your workloads. Quite a few BCL and CLR bug fixes.
If you have any content you want me to take a look at to include in my next Roundup, let me know in Twitter or in the comments. If you enjoyed this roundup, I plan on emailing them out weekly after posting. Sign up below!Follow @codeopinion