Previous post in this series:SOLID – (OCP) The Open-Closed Principle FUNCTIONS THAT USE POINTERS OR REFERENCES TO BASE CLASSES MUST BE ABLE TO USE OBJECTS OF DERIVED CLASSES WITHOUT KNOWING IT. The importance of this principle becomes obvious when you consider the consequences of violating it. If there is a function which does not conform […]
. Read more
Previous post in this series:SOLID – SRP – Ignoring the rules on the paint can SOFTWARE ENTITIES (CLASSES, MODULES, FUNCTIONS, ETC.) SHOULD BE OPEN FOR EXTENSION, BUT CLOSED FOR MODIFICATION. When a single change to a program results in a cascade of changes to dependent modules, that program exhibits the undesirable attributes that we have […]
. Read more
Previous post in this series:SOLID – (SRP) The Single Responsibility Principle Some of my source links in the previous two posts may not have worked in FireFox (but worked fine in IE and Chrome). These links have been fixed. It was an issue with how google was handling the redirects to the source files. In […]
. Read more
Previous post in this series:SOLID – Getting Started and Source Material Original Source Material on SRP I’m sure most of us have taken an Object Oriented Programming (OOP) class in college (or will soon). What is important to understand is that an OOP class will teach you the fundamentals of understanding the principles of developing […]
. Read more
This next series will follow the principles of SOLID, “five basic principles of object-oriented programming and design.” The concepts as collated into SOLID was organized by a gentleman named Robert C. Martin who has what may be one of my favorite quotes in software engineering: Following the rules on the paint can won’t teach you […]
. Read more
This has been a fun journey and hopefully you’ve learned a bit about MVVM and the TPL. I do have plans for future posts in this series that will center around the TPL.Dataflow namespace. It’s an area of the TPL I don’t seem written about a lot and I think there are probably a few […]
. Read more
Previous Post in this series:Part 12: Cancelling Threads with the CancellationTokenSource – The Code This sample derives from a Microsoft example and an updated solution is available here. AsyncAwaitSample model: There are two runs here, one shown using the keyword “await” with an asyncronous method and another run just running an asyncronous method without using […]
. Read more
Previous Post in this series:Part 11: Cancelling Threads with the CancellationTokenSource – The MVVM So now that we’ve covered the MVVM, which you saw was pretty trivial to implement, let’s cover the actual sample. CancellationSample.Run We start by instantiating the CancellationTokenSource that holds our token. We have to do this for each run or else […]
. Read more
Previous Post in this series:Part 10: Loop control of the Parallel.For and .ForEach Next up we’ll work on cancelling threads with the CancellationTokenSource. This is really a two parter where the first part will deal with the changes I had to make to integrate a new view and the second part covering the sample model. […]
. Read more
Previous Post in this series:Part 9: Basic Exception handling with the AggregateException Generally we’re used to having a break when doing loops. If you’ve tried to continue or break out of a parallel loop you get: No enclosing loop out of which to break or continue “continue” is the easy case, just return. But breaking […]
. Read more