Local Code Challenge

In this challenge, you'll update the Issue Tracker API with support for dependency injection by adding a DI container to the "IssueTracker" ASP.NET project.

You'll be completing this challenge using an IDE or code editor locally on your own computer. Download the code to get started and use the tools in your IDE or code editor to help you complete it. When you're ready, upload your finished code to run a series of tests and make sure everything's in working order!

Extra tips:


Here are the tasks that you need to complete for this code challenge. If you get stuck completing any of these tasks, see below for a list of detailed tasks.

  • Update the IssuesController class to use constructor injection to declare a dependency for the IssuesRepository class
  • Install the Simple Injector DI container
  • Configure the DI container
    • Register the Context, IssuesRepository, and DepartmentsRepository types with the DI container using the "Scoped" lifestyle

Project Overview

As you complete the code challenges in this course, you'll be working on a simple API for creating, reading, updating, and deleting user issues. When completed, this API could be used as the back-end for a simple issue tracker client.

The provided Visual Studio solution includes an empty ASP.NET project, a shared class library project, and a test project. The shared class library project contains Entity Framework related classes (repository, database context, database initializer, and two model classes) to enable data persistence. The test project contains a collection of unit tests that will verify if your code implements all of the necessary requirements for each code challenge.

Note: When opening the Visual Studio solution for the first time, you'll be prompted with a security warning, for each project. Visual Studio does this to ensure that you're aware of the risks of executing code from untrusted sources. Go ahead and click the "OK" button to continue with opening the project.

Getting Started

Once you've downloaded the files for the code challenge, extract the ZIP file, and open into Visual Studio 2017 the IssueTracker.sln file located in the "src" folder.

Each code challenge will include instructions listing the specific tasks that you need to complete. To help determine when you've successfully completed all of the tasks, you can use Visual Studio's Test Explorer window to run all of the provided unit tests. If all of the tests pass, you're ready to upload your solution! If a one or more tests fail, review the error messages for hints on how you can resolve the issues.

Some of the challenges are purely setup or configuration related, so there won't necessarily be something that you easily manually test by debugging the application. For those challenges, you'll have to rely solely upon the provided unit tests to check if you've successfully completed all of the required tasks. Other challenges will have you adding a controller or adding/updating action methods. For those challenges, you can manually debug the application using a browser or a tool like Postman, in addition to running the provided unit tests.

As a convenience, the root of the "IssueTracker" ASP.NET project contains a gulp script that you can run using Visual Studio's Task Runner Explorer window. The gulp script contains a "default" task that will restore NuGet packages (if necessary), build the solution, run the unit tests, and if all of the tests pass, create a ZIP file of your solution. You'll find the "project.zip" file in the root folder (the folder that contains the README.md file). Upload this file when you're ready to complete the challenge.

Detailed Tasks

  • Update the IssuesController class to use constructor injection to declare a dependency for the IssuesRepository class
    • Add a constructor to the IssuesController class
    • Define a single parameter of type IssuesRepository named issuesRepository
  • Store the injected IssuesRepository object reference into a private field
    • Add a private field to the IssuesController class of type IssuesRepository named _issuesRepository
    • In the constructor, set the private field to the issuesRepository parameter value
  • Install the Simple Injector DI container
    • Install into the IssueTracker project the SimpleInjector.Integration.WebApi.WebHost.QuickStart package (v4.0.8)
  • Configure the DI container by updating the SimpleInjectorWebApiInitializer class' InitializeContainer method (see the SimpleInjectorWebApiInitializer.cs file in the "App_Start" folder)
    • Remove the line of code #error Register your services here (remove this line).
    • Use the Container.Register method to register the Context, IssuesRepository, and DepartmentsRepository types with the DI container using the "Scoped" lifestyle

Note: The boilerplate code that the Simple Injector NuGet package creates in the SimpleInjectorWebApiInitializer.cs file uses a deprecated class for the default scoped lifestyle. While this doesn't generate a compilation error, it's generate a warning.

To eliminate the warning, you can optionally update this line of code:

container.Options.DefaultScopedLifestyle = new WebApiRequestLifestyle();


container.Options.DefaultScopedLifestyle = new SimpleInjector.Lifestyles.AsyncScopedLifestyle();