Scribd Logo
Upload

Welcome to Scribd!

  • 91 views

    Read This First: C# Intermediate: Classes, Interfaces and OOP

    Uploaded by

    jfreddy82
    The document discusses exercises for learning interfaces in C# programming. It provides an exercise to design a workflow engine that takes a workflow object and runs it by iterating through each activity in the workflow and executing it. The workflow engine should not care about the concrete implementation of each activity, only that they implement a common Execute() method interface. This allows new activity types to be created without changing the engine. The goal is to understand how to build extensible applications using interfaces and polymorphism.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Read This First: C# Intermediate: Classes, Interfaces and OOP

    Uploaded by

    jfreddy82
    91 views2 pages
    The document discusses exercises for learning interfaces in C# programming. It provides an exercise to design a workflow engine that takes a workflow object and runs it by iterating through each activity in the workflow and executing it. The workflow engine should not care about the concrete implementation of each activity, only that they implement a common Execute() method interface. This allows new activity types to be created without changing the engine. The goal is to understand how to build extensible applications using interfaces and polymorphism.

    Original Description:

    Original Title

    7. Exercises

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses exercises for learning interfaces in C# programming. It provides an exercise to design a workflow engine that takes a workflow object and runs it by iterating through each activity in the workflow and executing it. The workflow engine should not care about the concrete implementation of each activity, only that they implement a common Execute() method interface. This allows new activity types to be created without changing the engine. The goal is to understand how to build extensible applications using interfaces and polymorphism.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    91 views2 pages

    Read This First: C# Intermediate: Classes, Interfaces and OOP

    Uploaded by

    jfreddy82
    The document discusses exercises for learning interfaces in C# programming. It provides an exercise to design a workflow engine that takes a workflow object and runs it by iterating through each activity in the workflow and executing it. The workflow engine should not care about the concrete implementation of each activity, only that they implement a common Execute() method interface. This allows new activity types to be created without changing the engine. The goal is to understand how to build extensible applications using interfaces and polymorphism.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    C# Intermediate: Classes, Interfaces and OOP

    By: Mosh Hamedani



    

    www.programmingwithmosh.com

    INTERFACES - Exercises

    Read this first


    I’ve designed these exercise to help you apply what you have learned in this section. Make sure
    to do these exercises before moving on to the next chapter if you want to get the most out of this
    course.

    Where are the answers?


    I have deliberately decided not to provide the answers. Why? Because I want to make a great
    programmer out of you, not a lazy programmer who is used to copying/pasting code from various
    sources, without knowing what is happening!

    In the real world, when you are at work, your job is to solve a problem. No one (including myself)
    knows the answers to real world problems initially. So we need to research, think, try different
    ideas, and see what works best. And that’s exactly the kind of attitude I would like to see in you.
    If I give you the answers, you’re going to get lazy and quickly look at the solution. This way, your
    programming brain will not be trained and you will always be dependent on other people’s
    answers in the real-world.

    So, do your best to solve these problems. They are not excessively hard, and any student who
    has taken all the lectures in this section should be able to solve these problems with a little effort.
    If you get stuck along the way, post your question in the discussion area. I’m happy to help you
    out. But please check the discussion area first to make sure no one has asked the same
    question before. This way, you’ll save both your and my time.

    So, let’s get started!

    1
    Exercise: Design a workflow engine

    Design a workflow engine that takes a workflow object and runs it. A workflow is a series of steps
    or activities. The workflow engine class should have one method called Run() that takes a
    workflow, and then iterates over each activity in the workflow and runs it.

    We want our workflows to be extensible, so we can create new activities without impacting the
    existing activities.

    Educational tip: we should represent the concept of an activity using an interface. Each activity
    should have a method called Execute(). The workflow engine does not care about the concrete
    implementation of activities. All it cares about is that these activities have a common interface:
    they provide a method called Execute(). The engine simply calls this method and this way it
    executes a series of activities in sequence.

    The aim of this exercise is to help you understand how you can use interfaces to design
    extensible applications. You change the behaviour of your application by creating new classes,
    rather than changing the existing classes. You’ll also see polymorphic behaviour of interfaces.

    Real-world use case: in a real-world application you may use a workflow in a scenario like the
    following:

    1- Upload a video to a cloud storage.


    2- Call a web service provided by a third-party video encoding service to tell them you have a
    video ready for encoding.
    3- Send an email to the owner of the video notifying them that the video started processing.
    4- Change the status of the video record in the database to “Processing”.

    Each of these steps can be represented by an activity. For the purpose of this exercise, do not
    worry about these complexities. Simply use Console.WriteLine() in each of your activity classes.
    Your focus should be on sending a workflow to the workflow engine and having it run the
    workflow and all the activities inside it. We don’t care about the actual activities.

    You might also like