Thanks for reading.

I’ve previously done what you’ve suggested, I’m building an API client which is in the same repo as the respective API service, which has worked, but it feels like there’s still some cognitive load required to know when to actually build a version. I find I don’t have this problem when I have a single package (or multiple packages with the same version) per repo.

I’m on the lookout for a more robust mono-repo type solution, as elsewhere I have about half a dozen related NuGet packages that are a pain to manage in separate repos.



Freelance Engineer, Architect, Problem Solver etc.

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store