<p>After looking at other questions related to sharing solutions between VS 2005 and VS 2008 it seems that the way to go is to have two solution files (one for VS 2005 and one for VS 2008).  </p>

<p>However, if the solution is under source control (VisualSVN in our case), how would we maintain two solution files and not keep overwriting one or the other with each update/commit?</p>

<p>Is it possible to remove just the .sln file from source control and stop the VisualSVN client from checking its status in visual studio?</p>

<p>Thanks</p>

<p>Matt</p>

I'm not sure I see the problem - if you've got two solution files, why would either of them be overwritten? I do really mean two files, e.g. MyApp2005.sln and MyApp2008.sln, where when you create a new project you do it in the 2005 solution and then just "add existing project" in the 2008 solution.
What would VisualSVN do to mess this up?
(I have the same setup for my
C# in Depth source code
, and I use VisualSVN - I haven't seen any problems.)