Code management in different projects with different svn repositories
- by uzay95
First of all I want to tell you what kind of system I have and I want to build on.
1- A Solution (has)
a- Shared Class Library project (which is for lots of different solutions)
b- Another Class Library project (which is only for this solution)
c- Web Application project (which main part of this solution)
d- Shared Web Service project (which also serves for different solutions)
2- B Solution (has)
a- Shared Class Library project (which is for lots of different solutions)
c- Windows Form Application project (which is main part of this solution)
d- Web Service project (which also serves for different solutions)
and other projects like that....
I am using xp-dev.com as our svn repository server. And I opened different projects for these items (Shared Class Library, Web Service project, Windows Form Application project, Web Application project, Another Class Library project) .
I want to do the versioning of all these projects of course.
My first question is, should I put each project(one solution) to one svn repository to get their revision number later on?
Or should I put each of them to different svn repository and keep( write down) their correct version number that is used to publish/deploy every solution?
If I use one svn for each project(Shared Class Lib, Web App, Shared Web Service....) how can I relate the right svn address and version on VS.2010 within the real solution?
So, how do you manage your repositories and projects?
