Microsoft KB Archive/317992

= FIX: You receive an error message when you check in certain types of binary files in Visual SourceSafe =

Article ID: 317992

Article Last Modified on 8/18/2005

-

APPLIES TO


 * Microsoft Visual SourceSafe 6.0C, when used with:
 * Microsoft Visual Studio .NET 2002 Professional Edition

-



This article was previously published under Q317992



SYMPTOMS
When you check in certain types of binary files, you may receive the following error message:

The character encoding for the file FileName has changed. For example, it may have changed from text to binary, or from ANSI text to Unicode text. Because your source control provider for this file may not be able to merge files with different types or encodings correctly, you may need to manually change the file type directly in the source control store to match the new encoding you have just saved.



CAUSE
The file type in Visual SourceSafe is set to text, even though the file type is binary.



RESOLUTION
To resolve this issue, follow these steps:  Copy the file into your working directory. Your Visual SourceSafe Administrator must roll back the file to the previous version. To roll back the file, follow these steps:  In the Visual SourceSafe explorer, right-click the file that you want to roll back, click Show History. Select the previous version of the file, and then click Rollback.  Your Visual SourceSafe Administrator must change the file type to binary. To change the file type, follow these steps:  In the Visual SourceSafe explorer, right-click the file that you want to change to binary, click Properties</li> On the General tab, select Binary from the File Type list.</li></ol> </li> Check out the file again from the Visual Studio .NET integrated development environment (IDE), and ensure that you click Overwrite.</li> Copy the backup of the file from step 1 to your working directory, and overwrite the existing file.</li> Check the file back in to the Visual SourceSafe database.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in Visual Studio .NET 2003.

<div class="moreinformation_section">

Steps to Reproduce Behavior

 * 1) Create a new database project in Visual SourceSafe.
 * 2) Add a query, and do not add or edit a table.
 * 3) Add the solution and the project to source control.
 * 4) Check out the query from Visual SourceSafe, and then modify the query.
 * 5) Check in the query to the Visual SourceSafe database.

Keywords: kbbug kbfix kbpending kbvs2002sp1sweep KB317992

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.