Hi, I have a question about Assembly Definitions: how exactly should I use them? E.g., here’s Project Solution of one of my projects and here I went full rogue and basically spited everything that seemed logical it should belong there as if they were folders (previously I’ve actually had them as a folder in a single project, but oh well).
Sooooo… is this overkill? Is it too much? Some of these projects have like a few files
Can anyone show examples of your Project Solution? How do you structure your project using Assembly Definitions?
Thank you!
I really don’t think you need to have multiple assemblies for a single project unless you have parts that you may want to reuse in another project later.
I usually keep everything organized in folders but same assembly
Depends on the project size. If your project is on the larger size then you probably should be using assemblies to both keep your mechanics/systems segregated and to help with compile times.
To OP, you’re making a good start I think. I think of my assemblies in two ways:
- Mechanics/Systems that are used by other systems
- Mechanics/Systems that use other systems
With the former you need to ensure it has no dependencies on other systems that may use it (this is mostly from the perspective of adding assemblies later in the project; if you build it this way from the start this should happen naturally). These are usually general systems. Stuff like UI, helper code, or mechanics that be used by a lot of other mechanics.
The later can generally use the former, but you should be careful about them depending on other assemblies in the second category too.