Add Files Performance under .NET

[ewan.mcnab]

There seems to have been a few posts regarding the performance of the Add
functionality under Visual Studio .NET

We develop and sell our own Source Code Control tool (Team Coherence) and
have been encountering similar complaints, so we decided to investigate...
Our own tool is designed to work across the Internet and so certain actions
have more of a performance hit than would be apparent using VSS across a
LAN, though we have now resolved these.

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.

It seems that steps 2-12 are wasted since the initialization of the provider
should tell VS what the capabilities of the provider are. The result is,
though, that adding a new solution to source control takes far longer than
it should.

Given the number of comments on the performance of VSS within VS.NET, I
would hope that MS would do something about this for the next release.

Regards

--
Ewan McNab
Quality Software Components Ltd
http://www.qsc.co.uk
Developers of Team Coherence

[John Saunders]

Ewan,

I'm sitting here doing an "Add Project from Source Control" (as I have been
doing for the past 50 minutes), so I have time to ask:

Was there a publicly-available tool you used to determine which API calls
VSS made? It would be amusing to me to see which brain-dead things it's
doing, instead of simply speculating on what they might be.

--
John Saunders
Internet Engineer
john.s...@surfcontrol.com

"ewan.mcnab" <ewan....@0800dial.com> wrote in message
news:3e2db...@news1.vip.uk.com...

[ewan.mcnab]

Hi John

We are developers of Team Coherence which is an SCC API compliant competitor
to Visual Source Safe :-)

We had been having complaints from users regarding performance within the
VS.NET IDE, but only during initial adding of projects. Basically, we simply
logged calls to our SCCAPI dll to see what was going on. We were able to do
some additional caching to speed up the repetitive calls and performance in
our next release will be far better.

Unfortunately, the SCC API is under NDA and so we can't publish the exact
calls that VS.NET is making. If you are interested in seing how the SCC API
works, though, it is available from MS by signing their NDA.

Cheers

Ewan

"John Saunders" <john.s...@surfcontrol.com> wrote in message
news:e409LGDxCHA.2476@TK2MSFTNGP10...

[John Saunders]

Thanks, Ewan, but I'm not that much of a masochist (only enough of one that
I still use SourceSafe).

--
John Saunders
Internet Engineer
john.s...@surfcontrol.com

"ewan.mcnab" <ewan....@0800dial.com> wrote in message

news:3e328...@news1.vip.uk.com...