title: How to handle SVN when a project needs to be parts of 2 different .NET solutions?
body: <p>I have been working on a .Net C# solution (A) that includes several projects.
  This solution is source-controlled via SVN.</p>
  
  <p>Now I would like to start working on a new solution (B) that will include one of the projects of solution A. This solution B will need to be source-controlled via SVN too.</p>
  
  <p>The most obvious solution would be to create solution B and just include the concerned project.
  If I do that, the concerned project will be part of 2 different SVN folders. I suppose that this will create tons of subsequent issues?</p>
  
  <p>An alternate solution could be to remove the project from solution A SVN folder and create a dedicated SVN folder for the project. Then I can update this project code from both solution A and B. Only downside is that when I update solution A (or B), I ll need to commit changes for solution A (or B) and for the project SVN folder. But probably better than the former solution?</p>
  
  <p>Is there any othere option? What are the best practises in this case?</p>
  
  <p>thx for your knowledge.</p>