Tell me more ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.
up vote 0 down vote favorite

I have a Visual Studio solution with multiple projects:

  • Acme.Core
  • Acme.Core.Tests
  • Acme.UI.MvcSite1
  • Acme.UI.MvcSite2
  • Acme.UI.WinformsApp1
  • Acme.UI.WinformsApp2
  • ...

The entire solution is checked-in in a single GitHub (private) repo. Acme.Core contains our business logic and all UI projects are deployables. UI projects have different requirements and features, but some of them are implemented in more than one project.

All issues are opened in a single issue tracker and classified using labels ([MvcSite1], [WinformsApp1], etc) but I'm thinking it's starting to get messy.

Is it ok to use a single repository and issue tracker to track multiple projects in one solution?

share|improve this question
Please DO NOT cross post questions. It robs the community of the chance to contribute and learn from the other answers presented. I have flagged your question for mod review and potential merging. – GlenH7 May 2 at 11:43
1  
Please don't cross post. If you want the question migrating flag it. – ChrisF♦ May 2 at 11:43
Sorry for the mess and thank you for closing the question at StackOverflow. I cross-posted because I had no responses there and after some thought I realized that the question was more suitable here. – Luiz Damim May 2 at 11:56

1 Answer

up vote -1 down vote

Certainly -- why would visual studio's fundamental unit be a solution if this weren't the case?

share|improve this answer
What does the organization of an IDE/build have to do with the number of repositories and issue trackers you have? You can still fit into the IDE model with multiple repositories as submodules, for example. – Lars Viklund May 2 at 11:41
I never said you had to, nor was the question that deep. He had a pretty simple question -- "Is it ok to use a single repository and issue tracker to track multiple projects in one solution?" -- that didn't need a philosophical answer. Also, in most visual studio specific cases the stu modules were their own solutions more than a single included project. – Wyatt Barnett May 2 at 11:45
An answer should answer the real underlying question and demonstrate some actual experience or common practices. A simple "yup/nope" with some non-applicable rationale isn't a quality answer. I'm sorry, but your answer contributes nothing to the actual underlying question. – Lars Viklund May 2 at 11:48

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.