VS + Subversion: best repository layout?
-
Hi, anybody out there using Subversion + Visual Studio? I have a question for you. I have a VS solution with multiple projects, with a folder structure similar to this one:
SolutionFolder
Solution.sln |
|
+---Project1FolderSourceFile1.cs ... SourceFileN.cs Project1.csproj |
+---Project2FolderSourceFile1.cs ... SourceFileN.cs Project2.csproj |
\---SampleAppFolder
SampleApp.cs
SampleApp.csprojUp till now I just committed the whole structure as a single unit, working from the root (SolutionFolder), but with this approach I cannot keep a distinct versioning on single Projects (i.e. I have to commit the whole solution, even if I only change Project1, and this also applies to branches and tags!). Which is the best SVN repository folder structure in order to have separate versioning on "child" project and at the same time maintain cohesion with the "root level" solution?
-
Hi, anybody out there using Subversion + Visual Studio? I have a question for you. I have a VS solution with multiple projects, with a folder structure similar to this one:
SolutionFolder
Solution.sln |
|
+---Project1FolderSourceFile1.cs ... SourceFileN.cs Project1.csproj |
+---Project2FolderSourceFile1.cs ... SourceFileN.cs Project2.csproj |
\---SampleAppFolder
SampleApp.cs
SampleApp.csprojUp till now I just committed the whole structure as a single unit, working from the root (SolutionFolder), but with this approach I cannot keep a distinct versioning on single Projects (i.e. I have to commit the whole solution, even if I only change Project1, and this also applies to branches and tags!). Which is the best SVN repository folder structure in order to have separate versioning on "child" project and at the same time maintain cohesion with the "root level" solution?
Metal76 wrote:
I have to commit the whole solution, even if I only change Project1
So what is wrong with it changing the version if you change a particular project within the solution?
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
Metal76 wrote:
I have to commit the whole solution, even if I only change Project1
So what is wrong with it changing the version if you change a particular project within the solution?
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
The problem is that the solution includes several projects which should be versioned independently; instead, with a single commit I have to tag the whole solution, I cannot tag single projects. For example suppose that both Project1 and Project2 are version 1.0.0, then I work only on Project1 and it moves to version 1.1.0. If I have a single commit with the whole solution, I will not able to store Project1 and Project2 versions as separate tags.