How to Remove vssver2.scc files from VSS 2005

How to Remove vssver2.scc files from VSS 2005

• ofir

  Can you elaborate on what you mean by "publish"
  
  

• RichMasterSoft

  For those that have this problem, the following may help..

  a) disregard the waffle in this tthread which si oof the point..

  b) The probem is caused by vs 2005 WAP.

  c) This is not fixed in SP1.

  d) The problem is not likely to be fixed because 1. The VSS team dont see it as their problem, the vs stidio team dont see it as their problem, and 3. Knowbody owns WAP problems anyway..

  Hence I suggest that you run a post script after publish to manually delete all the vssver2 stuff which only the VSS team knows about..

  Pity you cannot all talk to on-another!!!

  
  

• netpicker9

  Hi

  I just install Microsoft Visual sourcesafe 2005 but when I get any project from VSS and delete all *.scc files from my working directory now there is no VSS file but when I do binary comparison it mention that several vssver2.scc files doesn’t match but there is no such file in that local working directory can anyone help me please.

  
  
  

• Whoisit

  Ray,

  From the source control point of view I'd advise you AGAINST deleting the vssver.scc / vssver2.scc files.

  There is a good reason vssver2.scc files were marked hidden+read_only+system, and that is that people (myself included) use to think of them as "junk" or unnecessary files written by VSS, and delete them on sight.

  There is a problem with that: VSS keeps in those files enlistment information about the local files that were retrieved from the database (file version, checksums, date/time stamps, etc). If you delete the vssver.scc files, here is what VSS feature you'll be screwing up:

  - correct merge of checked out files during a Get operation (instead of 3-way merge, you'll only be able to do 2-way merge, so you'll have to redo merges you have already done on previous Get operations)

  - scc operations will be slower (checksums will have to be recalculated for every file)

  In addition, deleting vssver2.scc will screw up these features new in VSS2005:

  - checkout local version (so if you have a file that you checkout offline or modified without checking it out with VS first, on checkout you'll only be offered leave/replace options, which lose either your changes or someone else's changes - there will be no merge)

  - synchronizing names of files deleted and renamed in the scc database

  - distinguishing between files deleted locally and new files added on server in web projects

  - scc operations will be slower, Get dialog will not display beforehand what actions will be done for each file (like leave existing version, get newer file, etc).

  Btw, deleting those files won't help you - VSS will recreate them on the next Get/Add/Checkin operation....

  VSS2005 creates vssver2.scc files exactly in the same location where VSS6 created vssver.scc files. Vssver2.scc just replace vssver.scc files.

  If you see these files created in bin folder it means some of the files in .\bin are placed under source control for some reason. This may not be what you want (normally the files in bin should not be controllable). Check your project configuration, you may be able to change it so files in bin don't end up in source control. Also, there was a bug in web projects that caused files in bin to be placed incorrectly under source control (see this thread for more information and a hotfix in Venus side http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=106422&SiteID=1&PageID=1)

  Alin

  
  

• billb59

  Has this problem been resolved

  For some reason, VS2005 is insisting on publishing bin\vssver2.scc even
  though it is not part of the project! Because it is a protected OS file, it
  does not show up in the solution explorer in order to exclude it from the
  project. (And yes, I have Windows explorer set to show protected OS files
  and the VS solution explorer is set to show all files.
  
  This only seems to be a problem when publish is set to "Replace matching
  files with local copies" which results in a publish failed message. I would
  prefer to use "Delete all existing files prior to publish" but I have special
  permissions on a couple of folders that if I delete all prior then I have to
  go reset those permissions every time I publish. Very annoying.
  
  The bin folder is under source control because I have some purchased dll and
  license files of purchased controls that I would like to keep under source
  control for versioning. Not to mention I really do not think that removing
  the bin folder from source control is the answer.
  
  The bin\vssver2.scc file is NOT part of the project and therefore should NOT
  be copied during a publish. Why does VS2005 insist on publishing it
  
  Environment:
  
  Microsoft Visual Studio 2005 - Version 8.0.50727.762 (SP.050727-7600)
  Web Application Project
  Publish set to "Replace matching files..." and "Only files needed to run..."
  Microsoft .NET Framework - Version 2.0.50727
  VSS 2005

  
  
  

• bslim

  > "a) The delete file was your idea!.."

  I must have been drunk if I said somewhere to delete the vssver files...

  > Plase advise how to make VSS 2005 work with vs 2005 without breaking publish..

  Please investigate why you have files in the .\bin folder that are placed under source control (which files are controlled)... Files under source control in a folder cause VSS6/2005 to create those vssver.scc / vssver2.scc in the same folder. You can for instance look in the vssver2.scc with notepad, near the end of the files you should see the names of the controlled files. Depending on which files are controlled you should either restructure your project or patch VS as instructed in previous post (in case the pdb/dll end up controlled in a website)

  Alin

  
  

• Wiz_MDK

  Goto Build->Publish...

  
  

• g e o r g e

  hi,

  I got the solution from ur windows browser click Tools --> folder option and then click on view tab and uncheck option Hide protected operating system files. now u will be able to search *.scc files and then u can also delete them from ur local work location if required.

  
  
  

• Umesh_DB2

  Background..

  An existing installation of Vs 2005..

  Added vss 2005, which created problem..
  The vss 2005 instaltion si side-by-side the default for vss 2005.

  When vss 2005 is run it creates hidden vssver2.scc file in \bin

  These are then published, which creates overwrite problems as they are hidden files..

  Vss 2005 is desigend to work side by side when installed with vs 2005 right

  But will try and delte all the vssver.scc files, but this is not going to work as woill be a maintaince nightmare..

  
  

• Henri20

  vssver2.scc files have hidden, read-only and system attributes.

  You may need to show all files (including system files) to see them in WindowsExplorer.

  Please read the previous posts why you WOULDN'T WANT TO DELETE the vssver2.scc files...

  Alin

  
  

• Tsmedegaard

  a) The delete file was your idea!..

  b) All of the above is interesting, but bottom line this file breaks vs "Publish" operations.

  This IS caused by VSS 2005 update!

  Plase advise how to make VSS 2005 work with vs 2005 without breaking publish..

  
  

• Bernardo Piano

  Build/Publish is not a feature owned by source control.

  You have to post in the forum matching your project type and see if they have any way of excluding certain files from a publish command. If I look in Project/Properties/Publish/ApplicationFiles/ShowAllFiles I see that pdb files are automatically excluded, so there probably is a way to get more files to appear in that list.

  BTW, I've tried this on a C# console application and for me it published only some *.application, *.deploy, *,manifest setup.exe files. You should also make sure you don't have already vssver*.scc files in the target for publish.

  Alin

  
  

• Thymen

  Pat, as I said before, the Publish scenario is not owned by the source control integration team.

  I'll move this thread to the VB/Web projects forum because only the project controls what files gets published or excluded.

  As for vssver2.scc files not being displayed in the SolutionExplorer - this does not happen because the files are hidden/system, but because the web project specifically excludes these files from being displayed. This is done by specifying the file names as registry keys under

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Packages\{8FF02D1A-C177-4ac8-A62F-88FC6EA65F57}\IgnorableFiles. The files listed there (like mssccprj.scc, vssver.scc, vssver2.scc) are not displayed by the project.

  Alin

  
  

• Pedro Felix

  The problem appears to eb that vss 2005 is creating this file as a system hideen file ( which vss file MUST NOT BE)..

  As a result it cannot be excluded from vs 2005 publish list..

  Also vss 6.0d did not create vssver.scc files within \bin...

  They just need to work together..

  
  
• How to Remove vssver2.scc files from VSS 2005