When working with the Memory Profiler the way that a Dictionary<K,V> is shown in the Managed Fields is not very useful:
Thanks for pointing this out, we should totally show the details of struct instances in the Managed Field as well, not just object instances. That is admittedly a bit of an oversight.
Thanks!
Do you see any way that we could customise how these variables are displayed? Perhaps something along these lines: https://learn.microsoft.com/en-us/dotnet/framework/debug-trace-profile/enhancing-debugging-with-the-debugger-display-attributes
Not as a concrete improvement on our planning horizon, so to speak. I did log it as a feature request on your behalf via the internal equivalent of our feedback collection that is available via our roadmap page (Profiling tab). That way we’ll be sure to process and prioritize it as part of our planning flow 
Thanks, will do so myself next time
It can sometimes help to discuss and clarify it. That can, like in this situation, show that bugs or other issues prevent the underlying problem to be solved, or generally show the underlying problem to be solved by the feature request more clearly. We are most interested in what specific problem one is interested in solving, as there’s often as many different feature requests as there are requesters for something where the underlying issue is the same one.
So there’s definitely a space here in the forums to bring these up, but ultimately, we’ll then need to track the feedback through our system to be able to connect such similar requests and evaluate the priorities.
Hi Tijmen,
The fix for the value types not being properly displayed is finally release with version 1.1.0-exp.1 !
Looking forward to your feedback
