crazystar

 Profile Answers by crazystar 

• Aug 7th, 2009

 

Supplying parameters to the constructor at the time of object creation to initialize the object fields wil incur lesser cost compared to initialising fields through properties.
Reason: Properties are nothing but 'get_' and 'set_'  METHODS and therefore incur the  method invocation cost wen called.

jsubha2009

 Profile Answers by jsubha2009 Questions by jsubha2009

• Nov 27th, 2009

 

Properties are more effective when compared to field values intialized by constructors. Properties can be either read only property, write only property or read-write property. But this is not the case in field values. Also the Properties are strongly typed. They appear in the intellisense to choose from among the class elements. So Properties are useful by utility more than the field values intialized through constructors.

v_n_r

 Profile Answers by v_n_r 

• Dec 23rd, 2009

 

If the values are constant and known then, Create object once i.e, default constructor
and assign values to properties and add it to the list.

If the values are changing or the values are given at the time of execution then parameterised constructor is used.

so it depends on the values and methods how we use in the code.

chaugule_p

 Profile Answers by chaugule_p 

• Jan 20th, 2010

 

It is a scenario based decision the architecture of the application should take.

Any parameters which are required for that object to perform minimal Operations, can be added to the default constructor. e.g. UserName is mandatory for the user registration for any website.

By any means, if you maintaing the age of the person, it should be calculated based on the date of Birth and age should be just ready only property of the class, to make sure, no one overwrites it.

In general scenarios, I prefer to use properties instead of constructor parameters, as the code is more readable.