---
title: "Discussion on \"EF Core in a separate class library\" | Hashnode"
description: "Discussion on \"EF Core in a separate class library\". Whenever I start a new .NET Core project I like to separate out parts of the app into individual projects. Traditionally, I break down a solution like this:\n\n[Solution Name].Data - contains models, migrations and database context classes\n[Solution Na..."
url: "https://hashnode.com/posts/ef-core-in-a-separate-class-library/65b0099e0446a33bc2f899fc"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [EF Core in a separate class library](https://itsallinthecode.com/ef-core-in-a-separate-class-library?utm_source=hashnode&utm_medium=feed)

Whenever I start a new .NET Core project I like to separate out parts of the app into individual projects. Traditionally, I break down a solution like this: \[Solution Name\].Data - contains models, migrations and database context classes \[Solution Na...

Aug 26, 2019 · 3 min read · itsallinthecode.com  
Read the article

## Written by

[Rob](https://hashnode.com/@itsallinthecode)

@itsallinthecode

  
[View profile](https://hashnode.com/@itsallinthecode)

Automating

## Responses

Markdown supported · ⌘↵ to post

No responses yet.