Detailing Current Implementation

Here I will discuss how the library is implemented in detail.

As I might have mentioned before this library depends heavy on .NET's reflection. With reflection you are given the ability to access attributes and values within child classes (for this instance, classes that will extend DatabaseEntity), indirectly, of-course. And without the support for Reflection or Run-time Information, this would not have been possible (However I have plans for implementing this on C++ with the help of macros).

So, getting to the point, we have the following list of classes. I guess by now you know what these are, but just to recite,

• DatabaeEntity (which extends libdatabasehelper.classes.generic.GenericDatabaseEntity) - which should be extended by any class that will represent a table on the database, but always remeber to let the library handle any database related tasks.
• DatabaseManager (extending libdatabasehelper.classes.generic.GenericDatabaseManager) - the class that handles table creation and deletion related tasks, however it's duty does not end here. The class is also used to fetch data from the database (as database entities or into DataGridViews or DataTables) and perform bulk deletions.
• ConnectionManager (extending libdatabasehelper.classes.generic.GenericConnectionManager) - the class that will be managing connections for any database. Chances are that, you will rarely, if not jsut once, use this class for any of your development needs.
• FieldTools - Another class that you will not need. This class is used to convert C# datatypes to database specific data types.