{"product":{"product_id":"0321578899","title":"Advanced .NET Debugging","price":"59.99","image_url":"https://m.media-amazon.com/images/I/41wpKsEtxxL._SL500_.jpg","url":"https://www.amazon.com/dp/0321578899"},"comments":[{"body":"Yes, that's what I meant by type information. There's no good solution , the GC approach is probably closest if you know what you're doing. Serialisation can work to give an approximate size. \r\n\r\nTheoretically you can iterate through the class members and recursively dip into reference types then add up everything, but this is fraught with difficultly. If you want to know more, take a look at [Advanced .net debugging](https://www.amazon.co.uk/Advanced-Debugging-Addison-Wesley-Microsoft-Technology/dp/0321578899) which is old but goes into a lot of the internals and describes ways of inspecting and dumping .net objects. [This](https://www.amazon.co.uk/Internals-Debugging-Techniques-Addison-Wesley-Technology/dp/0321934717) is the updated version that I don't have and may no longer exist (edit: or it isn't published yet). And [This](https://www.pluralsight.com/courses/dotnet-internals-adv-debug) is a pluralsight course on the same.\r\n\r\nPossible some context of what OP intends to do with the object sizes would help. \r\n\r\nAnother option I just thought of is to use DotMemory with the DotMemory unit test extensions. This gives you the ability to build a unit test that measures memory usage, allocations, basically everything that DotMemory can show you in its profiler, but in a unit test. It's pretty simple to use (Was pretty simple to use, I haven't used it in 18 months). I don't remember if you need to own DotMemory to use it, it's a nuget package, so give it a go.\r\n\r\n\r\n","subreddit_name":"csharp","author":"serentilla"},{"body":"Hewardt also made the Advanced .NET Debugging book which is pretty great for that type of debugging.\r\n\r\nhttps://www.amazon.com/Advanced-NET-Debugging-Mario-Hewardt/dp/0321578899","subreddit_name":"ReverseEngineering","author":"devinvisible"}]}