C
C#8mo ago
abdesamed

Common Library GUI & CLI clients

Hi, I'm starting projects that have several separate sub projects; Server, Windows Client, CLI Client, Flutter Client. I want the the Windows and the CLI clients to share the common logic. the way I saw it done is to create a common class library project within the same solution as the GUI and CLI projects. however I don't want to change the current structure of separate folder for each project. how can I solve this
13 Replies
Angius
Angius8mo ago
What do you mean? Projects already are in separate folders Or, well, should be
abdesamed
abdesamedOP8mo ago
but within the same solution folder
Angius
Angius8mo ago
Yeah, and why is that an issue? Do you have a separate solution for each project?
abdesamed
abdesamedOP8mo ago
I didn't create any solution yet and it's not really an issue. I have multiple projects as I said not all of them are in C# so each one of them is on it's separate folder. I just hate breaking the consistency by having to put the windows and cli clients in the same folder
leowest
leowest8mo ago
u can create multiple solutions if u want that only hold the relevant projects
Angius
Angius8mo ago
I see no issue with
|——MyProject
|——MyProject.sln
|——MyProject.Server
| |——MyProject.Server.csproj
|——MyProject.Windows
| |——MyProject.Windows.csproj
|——MyProject.Shared
| |——MyProject.Shared.csproj
|——MyProject.Flutter
| |——whatever goes into a Flutter project
|——MyProject
|——MyProject.sln
|——MyProject.Server
| |——MyProject.Server.csproj
|——MyProject.Windows
| |——MyProject.Windows.csproj
|——MyProject.Shared
| |——MyProject.Shared.csproj
|——MyProject.Flutter
| |——whatever goes into a Flutter project
leowest
leowest8mo ago
I dont see any issues with that either this is an unrelated thing but I am working on a library with over 200+ projects and the way I found best to work on it, is by having separated solutions that open related projects that I need, to work at one time.
abdesamed
abdesamedOP8mo ago
the issue with this is that each project is a top level folder within my Github org so I can't have an sln file at the same level. I guess there is no easy way around this
Angius
Angius8mo ago
Wait, so each project is its own repo?
abdesamed
abdesamedOP8mo ago
yes
leowest
leowest8mo ago
that changes things a bit from your original question thou
Angius
Angius8mo ago
I'd probably look into using Github's nuget feed, then, and distribute the shared library as a nugget
abdesamed
abdesamedOP8mo ago
I think this will do thank you all, I appreciate the help
Want results from more Discord servers?
Add your server