PlausiblyDamp
Administrator
Guide to Object Orientated code in .Net
This is a continuation of the series started in here and is preceded by this thread
Introduction
In the previous articles we have looked at a simple class that contains data and functionality. The data is simply stored as variables within the class for simplicity.
The functionality of the class is exposed through three routines the Balance property and the Credit / Debit functions, in this article we will look at a bit of terminology and see how we can take advantage of some more .Net features.
Class A class is a piece of code that defines the functionality of an aspect of our code, in the previous articles we have a simple class called BankAccount; this defines how a BankAccount works in our system
This is a continuation of the series started in here and is preceded by this thread
Introduction
In the previous articles we have looked at a simple class that contains data and functionality. The data is simply stored as variables within the class for simplicity.
The functionality of the class is exposed through three routines the Balance property and the Credit / Debit functions, in this article we will look at a bit of terminology and see how we can take advantage of some more .Net features.
Class A class is a piece of code that defines the functionality of an aspect of our code, in the previous articles we have a simple class called BankAccount; this defines how a BankAccount works in our system
Last edited by a moderator: