.NET Core is a cross-platform version of .NET and its going everywhere. So here is my tale on how I got .NET Core running on Raspberry Pi 3B.
A simple trace and analysis application to showcase, how Event Pipe in .NET Core works for taking a trace of a .NET Core process and how to extract managed thread stack from the resulting trace which is very useful when analyzing performance issues.
AutoDebug : A simple Automated Debugger to run Windbg Commands and also query .NET CLR Runtime data in C#.
ML.NET is a cross-platform open-source machine learning framework that makes machine learning accessible to .NET developers. With ML.NET, you can create custom ML models using C# or F# without having to leave the .NET ecosystem. Oh yes it is cross-platform and works on Windows, Linux and macOS.
Lets look at the code to enumerate Modules in each App Domain. But first questions, what is AppDomain? Application domain or AppDomain is nothing but a logical region where .NET […]
Lets take a look at some basic CLR information which is essential before delving into other kinds of data for troubleshooting. Also keep in mind DAC information is extremely important to get data about CLR Runtime.
So here is the code to dump the Object handles grouped into different types. Also a summary of all handles at the end.
Let us see how to use ClrMD to extract the same details as !sos.dumpheap command included in SOS extension available through Windbg. This has been an important command for troubleshooting memory and performance issues in .NET process or process memory dumps.