feature request: check encoding on commit

jonne · Post by **jonne** » Thu Sep 29, 2005 4:03 am

Hi,

I have a problem with Visual Studio 2003 and Visual Studio 2005 beta 2. The text editor does not always save the file as the same encoding as it originally was when opening. As far as I can see the bug seems very random. Happends about 20% of the time.

If I use a Visual Studio project and check in there vault warns that the encoding is not the same as it was before. This is really good because then I know to change the encoding and save again.

My feature request is that it would be very useful to have this same functionality in the Vault Client. So if I check in a file with different encoding than the last version it would warn me.

Post by **Tonya** » Thu Sep 29, 2005 10:04 am

Jonne,

If I use a Visual Studio project and check in there vault warns that the encoding is not the same as it was before. This is really good because then I know to change the encoding and save again.

The message being displayed may not be a Vault message, it's likely that it's from Visual Studio.

What type of file and encoding are you using? I would like to reproduce this issue and receive the same message.

Thanks,

Tonya Nunn
SourceGear Support

Guest · Post by **Guest** » Fri Sep 30, 2005 4:47 am

The message being displayed may not be a Vault message, it's likely that it's from Visual Studio.

What type of file and encoding are you using? I would like to reproduce this issue and receive the same message.

This is a known bug in Visual Studio 2003. I have found other users with the same problem. But it is also still in Visual Studio 2005 beta 2, so I guess I will have to live with the bug for a while.

The encoding I use is "Unicode (UTF-8 with signature) - Codepage 65001" and Visual Studio randomly changes it to "Western European (Windows) - Codepage 1252".

In 90% of the projects I use the Vault Client for checking in / out files. I would appriciate some kind of solution to this.

John
jonne@e21online.com

Post by **Tonya** » Fri Sep 30, 2005 1:34 pm

My feature request is that it would be very useful to have this same functionality in the Vault Client. So if I check in a file with different encoding than the last version it would warn me.

The warning message that you are seeing within VS.Net is a Visual Studio message. Vault does not verify if the encoding has changed from before, therefore isn't possible right now to perform in the Vault Client.

I can add this as a feature request to be reviewed.

Thanks,

Tonya