Class, Constructor and Property - II

[RP]

Refer to my original post at:

http://groups.google.com/group/micro...202ff938fed637

I want to know:

(1) Is it necessary to define SET property if the constructor is
already there?

(2) When the constructor has been instantiated, I want to insert the
values in a table. Where the code to insert records must reside, in
the class itself or in the Button_Click event of Windows Form.

(3) Where I can find information about C# naming convention which is
used as a standard by developers?

[Andy Mueller]

RP wrote:

Refer to my original post at:

http://groups.google.com/group/micro...202ff938fed637

I want to know:

(1) Is it necessary to define SET property if the constructor is
already there?

No. Only if you want to change the property *after* the object has been
constructed

>
(2) When the constructor has been instantiated, I want to insert the
values in a table. Where the code to insert records must reside, in
the class itself or in the Button_Click event of Windows Form.

I would not implement it inside the class, as it ties the class to a
specific purpose. however, I can't tell if the button click is a good
place to do so.

>
(3) Where I can find information about C# naming convention which is
used as a standard by developers?

http://msdn2.microsoft.com/en-us/lib...ke(vs.71).aspx

Can be enforced using FxCop. If you are using VS 2005, open the project
properties and navigate to "Code Analysis". If not, you can download the
FxCop tool.

HTH,
Andy
--
You can email me by removing the NOSPAM parts below:
xm**********@gmxNOSPAM.net

[RP]

I am still not following why a constructor and a property [with
GET ... SET] is used simultaneously. I noticed it in many examples. I
am new to OOP. The class which I created [see my original post] uses
both a constructor and properties. After setting values in property, I
am puzzled where to use a constructor and for what?

On Nov 8, 11:30 am, Andy Mueller <[e-mail]:

No. Only if you want to change the property *after* the object has been
constructed

[=?Utf-8?B?RmFtaWx5IFRyZWUgTWlrZQ==?=]

There is no requirement to have a property in a class, and there is no
correlation from a constructor to a property. A property is simply a way of
encapsulating the desire to change a value of a facet of the object.

Some things, such as binding, only work with properties and not members.

Properties can be used to mask certain pieces of code behind the scenes.
For example, if you have a property on an object of class TicTacToeCell,
called CellValue, you may desire in the property set method, to check the
board to see if it causes a "win". If you did this with members rather than
properties, it would be somewhat more difficult.

I hope this helps a little.

"RP" wrote:

I am still not following why a constructor and a property [with
GET ... SET] is used simultaneously. I noticed it in many examples. I
am new to OOP. The class which I created [see my original post] uses
both a constructor and properties. After setting values in property, I
am puzzled where to use a constructor and for what?

On Nov 8, 11:30 am, Andy Mueller <[e-mail]:

No. Only if you want to change the property *after* the object has been
constructed