@ScottC37 Yes, you may. Although in V21 (which is being released soon), there will no longer be separate projects. Architecturally, these have been replaced with folders in V21. In 19.1 and prior, we generally organize solutions into projects with a layered approach. Each adapter has its own project. That project interacts with one adapter and handles all of the automation of that application. Referencing that project (or above it in the hierarchy) is a controller project where you might tie multiple adapter projects together. This contains all of your use-case-specific logic. Above this in the hierarchy (or referencing it) is what we refer to as the naming project. This is a project that represents your solution and is actually what gets deployed. It contains any of your initialization stuff and your project configurations. This architecture allows you to re-use your controller project and adapter projects in other solutions.
In V21, we'll likely architect our solutions in a similar manner, although it is much easier in V21 to package adapters together with their functionality, so we'll recommend that approach when V21 is released in the near future.