rattfieldnz/ArtDatabaseLINQ
This is an app I made to practice my LINQ skills - using in-memory objects instead of an external database.
Web 3 Tutorial - Implementing and understanding a 3 tier architecture within an ASP.NET C# environment
This repository is cataloged as part of our automated global GitHub synchronization. Full telemetry, velocity snapshots, and code summaries are scheduled for continuous enrichment.
This is an app I made to practice my LINQ skills - using in-memory objects instead of an external database.
This is my first go at implementing the observer design pattern, in C#. After coding this, I quickly realised how powerful this design pattern can be - especially thinking how it might be used in large-scale enterprise apps. I learned the observer pattern in my programming class, and by looking at sites such as http://www.dofactory.com/Patterns/PatternObserver.aspx.
This is my first go at implementing the Factory Design Pattern for an application. By using this design pattern, I was able to decouple a lot of code, by delegating responsibility of animal creation to their respective factories. In this example, I implemented two factories - one for North American species, and the other for Australian species. After finishing this application, I quickly realized the code will be easier to maintain than previous applications I have coded. I used Single Responsibility principle so each object is only responsible for its own jobs, Open-Closed principle so classes/objects can be modified by extension, and the Liskov Substitution principle for the Animal classes (each child can be substituted for it's base class).
This another C# project where I was learning how to implement the Strategy Design factory. You can select a radio button (Cats, Dogs, Ducks, Rabbits), click on the "Show Pets" button, and text-based information about the animals (belonging to the selected species) will be displayed in the listbox. If there are 4 or less of the particular species, their images will be displayed on the right hand side. Through using the Strategy Design pattern, I was able to decouple a lot of code - especially from the form, and attempt to apply Single Responsibility and Open-Closed principles to the application.