Important Note: Please do not submit a pull request or push your branch to this repository, as this will make your work available to other candidates.
Getting Started
Make sure you have version 2.2 of .NET Core installed: LINK
Clone this repository.
In the root, run dotnet restore.
If using Visual Studio Code, it will add the necessary files to debug.
To compile and run the app, run dotnet build in the app root and in the 'bin/Debug/netercoreapp*' folder run dotnet Bridgeway.Developer.Test.dll.
General Notes
This is a simple console app. The necessary infrastructure has already been written to allow dependency injection and to make the app run non-stop until CONTROL and C is pressed to cancel it.
Take note of Startup.cs. New services can be added to the application here. This is where you will plug your work into the app.
When the app starts a service runs called HourlyActionService. In this service a timer will call a method once an hour. It is up to you if you want to use this service to help acheive the below.
The Project
We want to have the ability to add classes to this project that will be called and run on specified days, at specified hours. For instance, we might want something to happen on Sundays and Wednesdays at 1400. For the purposes of this test, we will call this a ScheduledAction.
The ScheduledAction in the above example doesn't have to run precisely at 1400, but we need to guarantee it runs at some point between 1400 and 1500.
Please write the code that will enable us to do this within this project without using any external libraries. It should follow the object oriented rule of being open for extention but closed to change.
Once up and running we should be able to add or remove a ScheduledAction and specify the day and hour-of-day we want it to run. The actions to be performed at the specified hours are not currently known, and it's anticipated the need for different actions will grow over time.
An example ScheduledAction might involve sending emails or updating a database.
Important: As such, it should be possible to inject dependencies into the class or code that carries out the scheduled action, without having to 'new up'.