Sorry, the text below was translated automatically by Power Translator 7...


Hi,

We used the Visual Source Safe here in the company does already about 2 years, until then without larger problems. We already used Source Safe 6d and now we are using Source Safe 2005 - both with Visual Studio.Net (2003 and 2005).

We are in the moment looking for to institutionalize the use of the tool in our teams that work with Visual FoxPro 8, and we are finding some small problems in relation to the synchronization of the project file; problems these that report below counting with your collaboration.

For the that I understood, the source Safe maintains a file ". pjm" instead of using the traditional ". pjx" and ". pjt" of VFP, where Fox would make an updating of this file in the server (in text format) when we used the option "Project \ Source Control \ Update Project List", and the other (server for station) it would be accomplished in the moment of "Join Source Control Project."

Everything well... until then a "annoying" routine of whenever it adds a new object in the project (screen, report, etc), the developer to have to go until the option of "Update Project List" so that the project in the server is updated and the other developers of the team start to see that new item in the project.

The problem is being in relation to the "check-in" of that file (. pjm), that it is not being done automatically, and I am not also found option of doing from within of VFP, tends to go until the client of Source Safe to accomplish such task, in two moments:

1 - when opening a project for the option "Join Source Control Project": VFP download the project and the updated items of the server, however it maintains PJM with exclusive check-out for the developer, that needs to go until the screen of source safe for manually to liberate the file for the other developers.

2 - when updating the project in the server using "Update Project List": VFP makes the check-out in PJM, it updates him with the new items, however it doesn't accomplish the check-in to free the project for other, maintaining the file with lock... tends the developer that to go again until the client of VSS to do manually.

In other words, a routine a little difficult and insecure, once it depends on the good memory of the developers of the team in accomplishing such tasks, taking the risk of they maintain the "locked" project or even not updated, creating new screens and forgetting to synchronize... or then synchronizing and not liberating the file...

Does some friend use VSS with VFP in their companies, and could he tell as overcoming these subjects, increasing the quality in the administration and versioning of the sources, with productivity and safety in the process?

Regards,

Leandro Macedo