Question

C# question.
Say I have a customers class that has a bunch of props for storing string only data such as name postal data and phone numbers.

I don’t use this entity for ORM as I’m only adding it to some type of collection for use during app life cycle.
Additionally I don’t need to add any entity specific methods to it or persist the data to xml or database, or even to a webservice.

Is it better to make this a struct rather than a class? or no benefit?
Also side question, should I make the collection Customers, a list structure?

Be harsh, please critique.. 🙂

 struct customer
    {
        private string name;

        public string Name
        {
            get { return name; }
            set { name = value; }
        }

    }

struct Customers<List>
{
    private customer cust;

    public customer Cust
    {
        get { return cust; }
        set { cust = value; }
    }

}

Answer 1

I can’t see any value in making the customer a struct. The string fields will all be reference types, so you might as well make the whole thing a reference type (ie. class).

I’d be inclined to use one of the built-in collection types rather than create my on type for Customers. Something like:

List<Customer> Customers = new List<Customer>();