vss .vspscc file problem

Question

I converted a vs 2003 project successfully int vs 2005 and have come across a puzzling problem.  When trying to check in a project I receive the following error:

[project].vspscc cannot be checked in because it has different encoding and checked out multiple times.

After successfully upgrading all developers were forced to attach to the new solution as if they were new users, that is, no one was allowed to update his/her local copy.  I assume the "different encoding" would refer to different .net versions but this doesn't seem to add up.  The vss analyze says there are no current problems.  Any advice would be greatly appreciated.

Thanks,

AJL

Answer 1

Hi Ajl,

I suspect you installed VSS2005, too.

VSS2003 didn't recognized the [project].vspscc files as Utf-8, and treated them as Ansi; VS2005 recognized them as Utf-8, and doesn't allow you to checkin new versions when the file is multiple checked out. This is by design.

What you can do is undo checkout of the file in the VSS database and leave the file checked out only once. Then use VS to checkin the changes to your solution. If there aren't changes to this file, VSS2005 will not change automatically the file type in teh VSS database. You can open the file's Properties dialog and manually change the type "Ansi/Mbcs" into "Unicode (Utf-8)".

Alin

 

Answer 2

 

VSS2005 original installation recognizes the [project].vspscc as Utf-8 file and doesn't allow you to checking new versions when the file is multiple checked out.

 

Solution: Install the Visual SourceSafe 2005 Update CTP at:

 

http://support.microsoft.com/kb/939808

Answer 3

Well, the [project].vspscc IS Utf-8 encoded, so there's no wonder VSS2005 recognizes it as such.

VSS2005 GDR CTP will recognize it the same as VSS2005 (if it does something else - that would be a VSS bug).

 

Since I havent't seen anything in the MSDN article or in Richard's blog (http://blogs.msdn.com/richardb/archive/2007/06/06/list-of-bugs-fixed-in-sourcesafe-2005-gdr.aspx) to indicate Richard made any change that will allow checking in files with encoding changed when they were multiple checked out, I just installed the GDR and tried: upgrading to the GDR build will not help you here..

 

Alin

Answer 4

I was receiving the same error: 'file' cannot be checked in because it has different encoding and checked out multiple times. My problem was actually with a web.config file (for the record, it had nothing to do with 2003 going to 2005, the config file was created in 2003 and I was editing it in 2003).

In source safe, I right clicked on the file and selected Properties. I removed the check from the Auto-detect encoding of local file  check box. I was then able to check in my file.

I just wanted to add this comment incase anyone else ever had something similar.

-Flea

---

http://fleasharp.wordpress.com

Answer 5

Thanks for the info, Flea.

---

Catherine Sea
http://www.dynamsoft.com
http://www.scmsoftwareconfigurationmanagement.com