Should I derive my objects from System.ValueType
I think this would be ok if my objects consist of just value types. If it doesn't, I'm not sure what will happen. Maybe the compiler make the choice for me
Thanks
Jason
deriving from System.ValueType?
Hot Topic
- C# Process Events
- Threaded Controls
- C# .NET Naming Conventions
- updating the UI with progress bar while Business Layer in process
- Questions about Objects in C#
- Where is the "Project From Existing Code Wizard
- Things I would like to see in C# 3.0
- Xml Read
- Checking for internet connection!
- Attempted to read or write protected memory error in TransactionScope with OracleClient(10g)
Visual C#
- Where is Object Test Bench in Beta2 (VSTS)?
- C# and MFC
- line breaks in assembly description
- Simulation Run Time
- Can't call indexer property
- Need to launch a process on the server side
- textbox test always highlighted on window open
- How To Return Null From Class Instantiation
- VS2005 Beta2 Exits abrubply when trying to add a custom windows control to a form
- ArrayList copying a class
deriving from System.ValueType?
Suscuaja
Rather than trying to inherit from System.ValueType to make your object a value type... make it be a struct instead of a class.
While System.ValueType exists, you never explicitly inherit from it, instead anytime you create a class you are implicitly using a reference type while when you make a structure you are using a value type.
MobilTech
Sorry, I'm being stupid - the compiler won't let me derive from System.ValueType!!