Project Structure Advice - Common Solution without NuGet
Please could I get some project structure advice? I'd like to build a project which consists of multiple solutions. I'm splitting down a rather large product into multiple separate solutions - Authentication, Frontend, Backend and Shared. The first three all need to reference Shared, but must not reference each other.
How should I let these three solutions' projects reference the Shared solution (which will also be multiple projects) without packaging and publishing the Shared projects as NuGet packages?
Of course, I could just add the projects from Shared to each other solution that needs to reference them, but this is kinda messy, and would also rely on relative paths on disk which may not apply to other collaborators on the project.
2 Replies
Ideally you would have all projects under the same solution. You still have to manually define each project to reference others and it's easiest to do within the same solution.
Would really like to keep them in separate repositories, separate solutions
Guess I'll have to make the directory names and paths be a requirement