visual studio - Are there any drawbacks to having 1 solution per project -


we working on big application, comprising around 100 projects (40 views, 40 controllers/models, 20 utilities libraries). have outsourced bulk of work , deliverables come in randomly.

when deliverable (a project), need run fxcop, stylecop, associated unit-tests, etc, etc. before committing source control. make easier, have mandated every project has solution file. allows run automated script on solution file tests before checking in.

my question "can think of drawbacks having 1 solution each project?".

drawbacks have discussed include:

  1. additional maintenance required developers. doesn't bother have outsourced development on fixed-price contract.
  2. sourcesafe bindings in solution file. have been huge issue, luckily migrated tfs year ago.

we're in similar boat 200 projects, many of them common use, accross our various solutions of varying sizes.

while disadvantage load time, 1 advantage debugging - i.e. if code calling other assemblies, it's nice have in same solution.

also, keep our unit , integration tests along our core project (dll or exe) in same solution, on bare bones template have @ least 3 per solution.

ultimately i'd largest advantage of common solution boils down cross-project debugging, imo. - never toss them unless there @ least this, or other compelling reason.

on side note - not allow project without solution reasons noted above (running fxcop, etc.) plus continuous integration. 1 disadvantage of large solution several projects build time - know if messing component ended breaking unrelated solution/project.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -