Re: Wich is the way to put projects into sourcesafe for reusable compo

Re: Wich is the way to put projects into sourcesafe for reusable compo
What we did was to create a project in VSS that uses the PublicAssemblies 
directory as it's working folder.

We added the bin/release directory as a subproject of the main project in 
VSS and added the shared component assembly to the VSS project.  We then 
"shared" the release assembly to the PublicAssemblies project.

Before doing a release build, we check out the assembly file.

When testing is completed, the assembly is checked in (making it available 
in the PublicAssemblies project because of the share)

We then do a "get latest" on the PublicAssemblies project which places the 
assembly in the location where all .Net projects can refer to it.

If you're not worried about multi user access, you can just add a post build 
step on the release mode  of our shared componenent assembly that copies it 
to the PublicAssemblies directory.



"Roger Tranchez" <run1789@community.nospam> wrote in message 
news:0439B72D-1F6B-4AD4-8664-669E9A079F66@microsoft.com...
> Hello,
>
> Wich is the way to put projects into sourcesafe for reusable components ?
>
> I'll explain:
>
> I have an assembly (dll) with lots of common functions (customized 
> dialogs,
> components...) that I'm including on lots of different projects
>
> I though the best way to put it into sourcesafe was:
>
> First, put the common dll into a separate project into sourcesafe
>
> second, for each solution that uses that component, I add that dll project
> from sourcesafe, and reference it from my solution.
>
> Third (last), I add the new solution to sourcesafe AT THE SAME LEVEL.
>
> e.g. Sourcesafe tree:
>
> $/my_common_dll/my_common_dll.sln
>
> $/solution1/solution1.sln
> .
> .
> $/solutionN/solutionN.sln
>
> (Solution1..N ALL have references to the same my_common_dll project)
>
> The problem is, that on the third (last) step, when I try to add each
> solution1..N to SourceSafe, the following warning appears:
>
> "The project that you are attempting to add to source control may cause
> other source contro users to have difficulty opening this solution or 
> getting
> newer versions of it. To avoid this problem, add the project from a 
> location
> below the binding root of the other source controlled projects in the
> solution."
>
> I think I'm planning wrong this structure... could you help me ? wich way
> shoud I do ?
>
> Thanks,
>
>
> -- 
> Roger Tranchez
> MCTS
> .NET 2005 and DB developer
date: Wed, 17 Oct 2007 12:02:57 -0400 author: bryan