[p4] Fwd: Simpler Perforce integration with Visual Studio 2005/ 2008

[Robert Cowham]

For details on what VS certainly did in the first release or so (not sure
how much this has got better recently), see this thread:

http://groups.google.com/group/microsoft.public.vstudio.sourcesafe/browse_th
read/thread/a778db9273d4eeee/4cbdb3367f6d1b2c?lnk=st&q=scc+api+temp+files&rn
um=2&hl=en#4cbdb3367f6d1b2c

Quoting:

<<<<<<<<<<<<<<<<<
Having said that, the VS.NET support for the SCC API seems to be doing far
more than it needs to. For example, here is the scenario when adding a new
solution to Source Code Control:

    1) QueryInfo on every file in the Project
    2) Create a dummy project file for each project in the solution (with a
temp name)
    3) QueryInfo on each dummy project file
    4) Add each dummy Project File to Source Control
    5) Remove each dummy Project File
    6) QueryInfo on each Project File in the solution
    7) Add a temporary file
    8) Check out the temp file
    9) QueryInfo on the temp file
    10) Uncheckout the temp file
    11) Remove the temp file
    12) Do a Diff on every .vsscc and .vbproj in the solution

    13) Finally, Add the solution source files
    14) QueryInfo on all files (twice)
    15) CheckIn on the solutions .vsscc even though it didn't check it out. 
>>>>>>>>> 

Robert

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Ling Lo
> Sent: 24 December 2007 16:59
> To: Jim Tilander
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Fwd: Simpler Perforce integration with 
> Visual Studio 2005/ 2008
> 
> We use NiftyPerforce and it is superb.  The only downsides 
> are that it doesn't appear to be an SCM plug-in for Visual 
> Studio so the VS file explorer will not display the padlock 
> icon next to the file and the automagic check-out of a 
> readonly file does not always work so I end up clicking on 
> the check out button just to doubly make sure.
> 
> I've had a tinker with the SCM provider project in the VS SDK 
> and it appears to be possible, if a bit arduous, to make a 
> custom Perforce SCM plug-in.  It was interesting to see that 
> VS executes a callback to the plug-in for each file in the 
> project and I assume this is what causes the performance 
> problems as the Perforce SCM plug-in then has to query the 
> server for each and every file even though the API looks like 
> it would present all the files in one go.  I mocked up an SCM 
> that displayed padlocks for readonly files and it was 
> lightning fast and this seems like a decent route to go down 
> until MS gets round to fixing the callback.