Rookie question - allow team members overwrite DLLs?

If you are having a problem using Collab, post a message here.

Moderator: SourceGear

Posts: 2
Joined: Thu Oct 05, 2006 3:50 am
PostPosted: Thu Oct 05, 2006 3:56 am
Hi there,
This may have been covered before, but I haven't had any luck with search, so apologies if I'm asking anyone to repeat themselves.

We have a VS 2005 website solution which includes a class library project. We use SOS to make sure we can all edit our class files and web pages together without any risk. The entire project is stored within SOS, including all of the dlls and object files created during compile. This is the best arrangement for us, really, because as well as being a pure source-control application, SOS is also serving as a repository. We can easily deploy our project to another machine using SOS.

The problem is that when one of us wants to compile we have to check out all DLLs and object files so that VS can overwrite them. Ideally we'd like to have them included in SOS but allow anyone to overwrite at any time. Is there a solution, or should we instead remove them from SOS?


Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
PostPosted: Thu Oct 05, 2006 9:03 am
When working with an integrated IDE, it is best to let the IDE control
how things should work (working directories, what files are stored,
etc.) With that, it is recommended to not store the files in the
database at the same path where a compilation does its work.

If you still want to store them there, you could create a NEW folder
in a different folder, and have a POST compilation step copy the output
(.dlls) to that new folder. Doing this though would require that you check them out when doing a build.

Posts: 2
Joined: Thu Oct 05, 2006 3:50 am
PostPosted: Thu Oct 05, 2006 9:26 am
yeah, seems like checking out before a build is the way to go.


Return to Support (Collab)

Who is online

Users browsing this forum: No registered users and 1 guest