Bummer! This is just a preview. You need to be signed in with a Basic account to view the entire video.

Preview

Start a free Basic trial
to watch this video

Sign up for Treehouse

Reviewing the Comic Book Artists Repository

3:36 with James Churchill

Let's review my solution for moving the comic book artist related repository methods to their own repository class.

Follow Along

To follow along committing your changes to this course, you'll need to fork the dotnet-comic-book-library-manager repo. Then you can clone, commit, and push your changes to your fork like this:

git clone <your-fork>
cd dotnet-comic-book-library-manager
git checkout tags/v3.5 -b reviewing-the-comic-book-artists-repository

Keyboard Shortcuts

  • CTRL+M CTRL+O - Collapse to Definitions
  • 0:00

    How did it go?

  • 0:01

    Were you able to move the comic book artists related repository methods

  • 0:05

    to their own repository class?

  • 0:07

    Let's walk through my solution.

  • 0:09

    I started by adding the class named ComicBookArtistsRepository

  • 0:13

    to the class library's data folder.

  • 0:15

    To which I added a private field for the context instance and

  • 0:19

    a constructor that accepts a context instance, and

  • 0:22

    initializes the private field to that instance.

  • 0:25

    I then moved the GetComicBookArtist, AddComicBookArtist, and

  • 0:29

    DeleteComicBookArtist methods from the Repository class to

  • 0:33

    the ComicBookAristRepository class.

  • 0:38

    And added the using directives for the comic book shared models and

  • 0:42

    system data entity name spaces.

  • 0:49

    After I move the methods to the new class,

  • 0:52

    I renamed the GetComicBookArtist method to Get.

  • 1:03

    The AddComicBookArtist method to Add, and

  • 1:06

    the DeleteComicBookArtist method to Delete.

  • 1:12

    That keeps the entity type focused repositories

  • 1:15

    following the same method naming convention.

  • 1:18

    Then I moved on to the ComicBookArtistsController class and

  • 1:21

    added a private field from the new repository and

  • 1:24

    instantiated an instance of it in the constructor.

  • 1:40

    Then I finished up by fixing the build errors in the controller.

  • 1:46

    Repository.AddComicBookArtist became _comicBookArtistsRepository.Add.

  • 1:58

    Repository.GetComicBookArtist became _comicBookArtistRepository.Get.

  • 2:10

    Repository.DeleteComicBookArtist became _comicBookArtistsRepository.Delete.

  • 2:18

    Once the project was successfully building again, I ran the web app and

  • 2:22

    tested each page.

  • 2:31

    Remember, it's okay if you did things slightly differently than I did.

  • 2:35

    There's often more than one way to do something.

  • 2:38

    Let's take a closer look at our two entity type focused repositories.

  • 2:42

    I'll open them and place them in side by side tabs.

  • 2:48

    They both contain private fields for their context instances and initialized

  • 2:52

    those fields using a constructor that accepts a context instance.

  • 3:00

    They also both contain a Get method,

  • 3:02

    though the signature of those methods differ slightly.

  • 3:06

    The CRUD related methods are also very similar,

  • 3:08

    basically just varying by the entity type they're operating against.

  • 3:16

    So our repository classes look very similar to each other.

  • 3:20

    Which might make you wonder if there's a way that we can reduce some of this

  • 3:24

    very close to the same code.

  • 3:25

    While still retaining our entity type focused repositories.

  • 3:29

    Well, it turns out there is something that we can do.

  • 3:33

    We'll see exactly what in the next video.

You need to sign up for Treehouse in order to download course files.

Sign up