-
Notifications
You must be signed in to change notification settings - Fork 0
Installation
Jamie Pollock edited this page Jan 11, 2024
·
4 revisions
For the most update to date information check the readme.
In most cases adding Rhythm.Drop to your main web project will be enough to get you up and running. However in certain projects you may want to split your code out into different projects and not include the kitchen sink when doing so.
This table will determine what is where.
Package | Purpose |
---|---|
Rhythm.Drop | Contains everything needed to run and install Rhythm.Drop |
Rhythm.Drop.Models | Contains only the models used by the rest of the packages. If you only want to build your models manually without any builders you can add this to your project without additional dependencies. |
Rhythm.Drop.Infrastructure | Contains factories and data builders for images and links. Also contains component meta data logic. This project contains no web logic. |
Rhythm.Drop.Web | Contains the tag helpers needed to render models. Also references other projects to get this off the ground such as default implementations of key helpers and tag helper renderers. |
Rhythm.Drop.Web.Infrastructure | Contains the infrastructure used by the web package without the tag helpers. This package should be added if you have a project which intends to write custom tag helper renderers without including the tag helpers. |