Re: File checkout in Visual Studio .Net creates temp files in VSS

"Bill ***" <Bill***@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote...
>I have a Visual Studio .Net solution that has 10-15 projects (libraries that
> are linked into a single EXE as part of the solution). Originally under
> Visual Studio 6 the SourceSafe integration worked fine. When I ported to
> Visual Studio .Net 2003 things changed slightly. Checkin works fine, but if I
> check out any source file from with Visual Studio, SourceSafe adds and
> immediately deletes a strange temp file to one specific library project (and
> only that project):
>
> Added ~sak1829cea701c58199.tmp
> Deleted ~sak1829cea701c58199.tmp
>
> This clutters up the project history with a lot of garbage add/deletes, and
> I use that history for generating my software release notes. I suspect one of
> my linkages to SourceSafe in the SLN or VCPROJ files is corrupt. Does anyone
> have a suggestion on how I can get rid of these spurious add/deletes? They're
> driving me nuts!

I have the same problem - and so does everyone in my company, judging by my SourceSafe history
scans. It seems these weird temporary "~sak" files are part of how VS 7 integrates with source
control - but I can't work out why they're necessary or why MS would think it was a good idea to
clutter people's histories with them! It also confuses the user, since a dialogue quickly pops up
and then disappears for the creation and deletion of the ~sak file. If you find the solution I'd be
happy to hear it.

Andrew


.