This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SVCS and Sourcesafe's current project...

Hi

Is there a way to ensure that "Set Current Project" is selected before the next SVCS command is issued?

The reason I ask is that if I have two Keil projects open and I forget which project is "current" to sourcesafe and I issue a command, I may end up really screwing up an existing project file.

For example, project1 has a file called main.c and project 1 is current. If in project2 I also have a main.c file and I check it in, I have just messed up my project.

Any tricks to get around this other than remembering to hit the set current project EVERY time?

Thanks
James

Parents
  • As it turns out, that didn't solve the potential problem.

    The USERNAME value is stored in a global Keil setting somewhere (probably the project). So if I change the username in my second project, it also changes it in my first.

    The problem still exists that if I forget to change the user name before issuing a command, I could corrupt my sourcesafe tree without even knowing.

    James

Reply
  • As it turns out, that didn't solve the potential problem.

    The USERNAME value is stored in a global Keil setting somewhere (probably the project). So if I change the username in my second project, it also changes it in my first.

    The problem still exists that if I forget to change the user name before issuing a command, I could corrupt my sourcesafe tree without even knowing.

    James

Children