To fully understand C# you need to see the whole picture
-
I found that knowing parts of OOP C# such as the classes is like knowing parts of a car, you still need the overall picture to understand how things are linked together. For example if I was told the purpose of a spark plug is to product a spark then I would think somewhere in the cars engine there is a spark plug producing a spark, but to see how the engine worked I would need the whole picture (how everything is linked together) of the engine not just parts of it. After studying C# it seems that the main reason to program in C# is for the OOP that it and other languages provide as C# does not have a global variables option making it more difficult to use for procedural type programming. I was lucky to find a helpful text tutorial on the internet that showed me step by step how to write a C# program using OOP. Once the program was written I could then start to understand how things fit together. The tutorial continues to show how code can be improved by refactoring as well as other enhancements. The text tutorial is called "Learn C# by building a simple RPG." (see links below) https://scottlilly.com/learn-c-by-building-a-simple-rpg-index/ The PDF file of the text tutorial can be found here: https://scottlilly.com/CSRPGPDFLOCAL Brian