VSS Keyword Expansion Not Working From Visual Studio

Here's a weird problem:

We are using VSS 2005 and development happens in VS 2010. I tried experimenting with the keyword expansion feature today in the VSS 2005, and came across something weird.

After adding a couple of keywords ($Author: $ and $History: $) I tried checking in the file. The file was checked in correctly, but the keyword wasn't expanded. Checked it out, confirmed the keyword spellings etc and checked it in again. Still no luck.

Just on a hunch I checked out the file again, and this time checked it in using the VSS explorer. Voila! The keyword expansion happens!!

This means when I check in the files from within Visual Studio, the keyword expansion feature does not work. The keyword expansion only works when files are checked in through the VSS Explorer.


Has anyone come across this problem? Is there a work around?

And please don't advise on a different versioning tool, I don't want to debate the VSS vs other versioning tools here.

.

When this happens, the first thing I do is disable other extensions in Visual Studio and try it again. Have you tried that approach yet? Disable all other extensions except for the one required for VSS.

Can you please explain how this can be done?

.

Quote:

---

Originally Posted by honeybee

Can you please explain how this can be done?

.

---

Click on Extension Manager.


Click on Disable when you see the installed extension.

http://imgur.com/a/DqbSU/ <-- Screen scrapes.

Thanks, only the nuGet Package Manager shows up there, and I need it to be enabled.

.

Just check if that extension is interfering with the VSS expansion feature. I found that by disabling Productivity Tools, I was able to get my XSL debugging feature working. With productivity tools enabled, XSL debugging often crashes.