I don't think this makes sense. Source control is supposed to make breaking changes less likely to happen, not conventions or constraints like "don't let more than one solution include any project file."
It seems to me that VisualSVN does not support solutions that contain references to projects that are NOT in subdirectories of the solution directory. This is really bad for us. On Nov 19, 9:27 am, "Q Johnson" <[email protected]> wrote: > I'm not sure it's a "work around" but I think it's a better way to work. > > Don't put source for a single Class Libray project in multiple solutions. > Just reference the DLL in the other solutions that will use it. As long as > you reference the Debug versions, you will be able to step through the > source code. > > This solves more than one problem over the method you describe. Most > importantly, since there is only one source code project, you never have to > worry about different versions of the source code evolving over time. You > also enjoy the remedy to the problem that brought you here; since there is > only one source code project, there is only one instance of it under version > control. It also permits you much finer control over who is permitted to > make changes to source code. Any number of developers might be given access > to the DLLs to use their functionality in the solutions in which they are > authorized to work. But only those permitted access to the SOURCE CODE > version of the class library project can modify it. So you can put an end > to the pain you've endured in the past over "accidental changes" to such > source projects with this simple alternative technique. > > Hope this helps, > > Q Johnson > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > > Behalf Of SURFThru.com > Sent: Tuesday, November 18, 2008 8:39 PM > To: VisualSVN > Subject: Solution File with Multiple Projects > > I created a Class Library Project and checked it into SubVersion. > > I then created a new Empty Solution and added this class library project and > a new web site. > > Now in this new solution the Class Library does not show as being checked > out. SVN wants me to check the class library and web site in again under > this new solution. I know that SVN works on a solution basis but it is now > aware that the project in this solution is already under source control??? > There was another post here about a class libraries used on multiple > projects and this type of issue. > > Is there a work around? > > Thanks, > Patrick
