General information
Category:
Source Safe Control
Hey Alex,
Turns out I'm a one man band also.
However, I'm not clear on how putting the common stuff into a separate VSS project would allow me to compile without getting the Read-Only error. Isn't it still in a VSS project and therefore still in a Read-Only state?
Aloha,
James
>>I just started using Visual Source Safe and have run across a problem.
>>
>>I created one application ("Application 1") and have added it to VSS. Now, in another application ("Application 2") I want to use some of the libraries from "Application 1". When I try to do a "Rebuild Project" I get an error saying the libraries from "Application 1" are Read-Only.
>>
>>Is there a work around for this?
>
>
>It's a rather complex subject and you may get more than one opinion on this. I prefer to use the VSS interface (as oppossed to the VFP Project Interface to VSS) and put the common routines and libraries (VCX) in their own VSS project. As the common libraries do not change often (they are basically part of your framework) you don't need to get to them in VSS every day. That way each project has its own VSS folder and the common stuff another one shared by all. This is of course for a one-man band, as I am, not exactly for a team project where many devs access the same code and it gets a little more complex (but not much).
>
>Just my .02
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only