http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.pnghttp://channel9.msdn.com/forums/TechOff/258159-sizeof/!sizeofhttp://channel9.msdn.com/forums/TechOff/258159-sizeof/en-usThu, 11 Oct 2007 14:54:58 GMTThu, 11 Oct 2007 14:54:58 GMTEvNet (EvNet, Version=1.0.3243.35083, Culture=neutral, PublicKeyToken=null)<blockquote> <div>thumbtacks2 wrote:</div> <div>In C#, it's my understanding that variables are created as objects. </div> </blockquote> <br /> <br />That depends. Primitive types are primitive and have a fixed size - ints are 32bit, longs are 64bit and so forth.&nbsp; Here's a <a href="http://msdn2.microsoft.com/en-us/library/ms228360(vs.80).aspx">reference</a> of the C# primitive types and their sizes.<br /><br />It might also be a good idea to read up on boxing and unboxing to understand the meaning of an integer being both a primitive value type and also being an object inheriting from System.Object. Here's the <a href="http://msdn2.microsoft.com/en-us/library/yz2be5wk(VS.80).aspx">MSDN lowdown</a>. In a nutshell, an int will be a stack-allocated value as long as you treat it as such. Once you decide to treat it as an object (casting, polymorphism and the like) it will automatically be wrapped in a heap-allocated object.http://channel9.msdn.com/forums/TechOff/258159-sizeof/?CommentID=357987Thu, 11 Oct 2007 14:54:58 GMThttp://channel9.msdn.com/forums/TechOff/258159-sizeof/?CommentID=3579870http://channel9.msdn.com/357987/WebViewBug.aspx?EVT=0 thumbtacks2 wrote: In C#, it's my understanding that variables are created as objects. That depends. Primitive types are primitive and have a fixed size - ints are 32bit, longs are 64bit and so forth.&nbsp; Here's a reference of the C# primitive types and their sizes.It might also&#8230;Yggdrasil0http://channel9.msdn.com/357987/Trackback.aspxGetting the runtime size of a Managed object depends on a lot of factors, but there are some classes in System.Interop, primarily for marshalling between Managed and Non-Managed code. Generally speaking, you'll never need to touch it.<br /><br />What do you need the size of an object for? With the exception of structs like (U)Int* everything is on the heap and stored as references. So just multiply the class's fieldcount by the size of IntPtr... pointless (and totally inaccurate) measurement IMO.http://channel9.msdn.com/forums/TechOff/258159-sizeof/?CommentID=357802Wed, 10 Oct 2007 19:27:15 GMThttp://channel9.msdn.com/forums/TechOff/258159-sizeof/?CommentID=3578020http://channel9.msdn.com/357802/WebViewBug.aspx?EVT=0Getting the runtime size of a Managed object depends on a lot of factors, but there are some classes in System.Interop, primarily for marshalling between Managed and Non-Managed code. Generally speaking, you'll never need to touch it.What do you need the size of an object for? With the exception of&#8230;W3bbo0http://channel9.msdn.com/357802/Trackback.aspx