Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In my .Net application (MVVM application) i have let’s say 10 drop down lists. So i created 10 different classes(Models) containing just Name , Value pair. The reason of creating 10 different classes is just because these drop down lists are functionally independent.
What are the pros and cons (Including memory impact) of 10 different classes instead of just 1 class (Which contains Name Value Pair and Bound to View through ViewModel)
Having a number of different classes over a single one is hardly likely to make a difference to your application. Instantiation of simple types is very fast (billions of objects a second).
You might notice issues if you go into the many many millions of objects and then only if you are doing work when instantiating them.