"Add-On" Projects and ASP.NET Core with Entity Framework

I've created a .NET Core MVC product with Entity Framework, and am being tasked with creating "Add-on" products, which give CRUD operations to more tables, but use the same library functions and UI.

From a software engineering perspective, I found this a good opportunity to break my one huge project into multiple projects - the first time I'm doing something like this. This will help decouple the system.

Consider the following MS Paint diagram that illustrates how I envision this:

As mentioned, my current set up is thus:

Solution MainProduct
├── MainProduct

Would this set up work, considering how EF Core functions? Can the Contexts and Migrations (The DAL) be in the Class Library?

Solution MainProduct
├── MainProduct
├── ClassLibrary
├── UnitTests
├── Addon1
├── Addon2

I understand this is a broad question, but I'd like this current setup evaluated. Any resources would be appreciated too.