Hi all,
I have a strange problem on my Notebook using VS2005 and clearcase. SourceControl works fine, when I'm in the office. When I work at home, Visual Studio asks me if I want to work temporarily disconnected and it also performs disconnected checkouts of the files that I modify.
So far so good, but when I'm back in the office and connect to source control, Visual Studio adds strange temporary 0KB project files to source control, e.g.
~sak9acba8c901c641b9.csproj
Did anybody experience this problem and maybe knows a solution I didn't have this problem using VS2003...
Best Regards
Bernd Ritter
VS2005 adds strange temporary project files to source control, after having worked disconnected
WholesaleElectric
Bernard, VS2002, 2003 and 2005 create those temporary files to detect some capabilities of the source control provider. It looks like you're using a Clearcase provider that only supports MSSCCI 1.1 functions (when the provider supports MSSCCI 1.2 or later, VS doesn't create those temporary files).
The best solution for you is to check with Clearcase if they have an updated source control plugin supporting SccWillCreateSccFile/SccIsMultiCheckoutEnabled MSSCCI 1.2 functions. If such provider is not available, you can set the following registry value, which will prevent VisualStudio from creating those temporary files:
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\SourceControl] "DoNotCreateTemporaryFilesInSourceControl"=dword:00000001
Note: If this registry key is set to dword:00000000, it is equivalent to the key being nonexistent, and Visual Studio still attempts to create the temporary files. However, if the registry key is set to dword:00000001, Visual Studio does not attempt to create the temporary files. Instead it assumes that the source control plug-in does not support the mssccprj.scc file and does not support shared checkouts.
John, you are probably using VSS 6.0c or older if you see these temporary files created. VSS 6.0d implements MSSCCI 1.2 and VSS 2005 implements MSSCCI 1.3, and VS doesn't create those temporary files when one of these providers is used. You should upgrade your scc provider (you can upgrade for free to VSS 6.0d by installing VisualStudio 6 SP6)
Alin
TABARRY
Not just that. I saw lots of tmp files added whenever files are checked in. When I looked at the file history in vss, lots of tmp files added and deleted immediately. This is not good. Since deleted files are not physically deleted in vss, they take up space.
I remember we had a policy in a previous company which dictated that all should use vss explorer instead of use vss ide addin.
Treblent
The "Shared checkout" term is indeed specific to VSS, but other providers may call it differently. It's about the provider's capability of allowing a file to be checked out multiple times by different users in the same time.
The other setting is more important (whether the provider can create the mssccprj.scc files) because this influences where will VisualStudio store the project binding strings (in the project files, or will let the provider to persist them in mssccprj.scc). If the provider can create the mssccprj.scc files helps when branching the projects, etc.
Alin
Shawn Kovalchick
Hi Alin,
thanks for your answer!
But what exactly do you mean by "shared checkouts" Is this something specific to Visual Source Safe
Best Regards
Bernd