This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 99%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Sysinternals Process Explorer has 1 unique among other process explorers feature - display additional diagnostics for .Net framework processes
It could be a big value added feature, to do the same for .Net Core processes
Display core version, memory prams and so on
Is that possible to implement?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 36%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3E7%3C/text%3E%3C/svg%3E)
Yes, agreed. I've been waiting so long for Process Explorer to be updated to work with modern versions of .NET. and this show the tabs for '.NET Assembles' and '.NET Performance'. .NET core was originally released in 2016, and here we are in 2023 and still no support in Process Explorer. The issues also expands to the 'Threads' tab where if you try to examine the 'Stack' of a .NET process it gets confused at the transition from unmanaged to managed code. All the above works great for the 'legacy' .NET Frameworks. With Microsoft wanting everyone to transition to the modern .NET runtimes, it would be so good if this were supported by Process Explorer.
Yes, agreed. I've been waiting so long for Process Explorer to be updated to work with modern versions of .NET. and this show the tabs for '.NET Assembles' and '.NET Performance'. .NET core was originally released in 2016, and here we are in 2023 and still no support in Process Explorer. The issues also expands to the 'Threads' tab where if you try to examine the 'Stack' of a .NET process it gets confused at the transition from unmanaged to managed code. All the above works great for the 'legacy' .NET Frameworks. With Microsoft wanting everyone to transition to the modern .NET runtimes, it would be so good if this were supported by Process Explorer.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 73%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA3%3C/text%3E%3C/svg%3E)
+1 would be good to have support for modern .NET frameworks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 91%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
.NET Assemblies tab for .NET/.NET Core processes was added to Process Explorer v17.09 - https://techcommunity.microsoft.com/blog/sysinternals-blog/coreinfo-v4-0-notmyfault-v4-30-and-process-explorer-v17-09/4478567
Please note that this works for non self-contained .NET apps (this will be added in future versions).