Persistent integration with visual studio without checking project files

Question

I am working on a large source database (about 15 thousand files), divided into 25 projects. I want the source in perforce (and I evaluate perforce for this purpose), but due to configuration difficulties, I can’t keep the visual studio projects in source control, I know theoretically, the answer is to check the projects, but this is not possible ( we completed projects for several versions of VS, as well as several options for each of them, instead they are generated automatically, and this setting works very well).

Is there a way to get VS for validation files for editing, since it goes without adding a project to perforce so that the user cannot go to the perforce client and manually check each file for editing as they arrive? Alternatively (and even better) is there a way to get VS to recognize that the files in the project are under source control, without having to add the project to the original control?

I know that we can also adhere to the fact that each user can check all the files that they may want to edit beforehand, and then return the unmodified files before sending their changes, is there a performance penalty when accepting this?

Answer 1

In your case, I would suggest not using visual studio integration for Perforce.

You can add Perforce commands to the Tools menu or try Nifty Perforce from Google:

http://code.google.com/p/niftyplugins/

Answer 2

One option is to use Perforce as if you were disconnected from the server and later corrected your changes, instead of telling Perforce everything you do before you do it. (This is roughly equivalent to the workflow in CVS or Subversion.) You would synchronize your working copy, leave and develop, and then ask Perforce to find out what you were doing while it was not looking.

Perforce has a good document describing the process: Work is disabled with Perforce Server

allwrite clientspec, , , .

Answer 3

For completeness: there is a new tool for your desire called P4VS . I like that P4SCC , which never worked for me as I wanted.