Enhanced client doesn't seem to recognize binary file change

[gsmalter]

If I have a DDL in source control that is part of a VS solution, and I check it out in VS using the enhanced client, then copy over it with a newer DLL using Windows File Explorer, when I come back to VS, the status is listed as Unmodified. This remains true even if I do a save all and hit refresh.

If I go to the standalone Vault client, it correctly recognizes that the status is Edited. So, I close VS, do it in the standalone client, reopen VS and everything is fine. But this is inconvenient. I'm just afraid of what would happen if I used VS to check it in (like it would see that it was unmodified and do a no-op).

I'm pretty sure this used to work.

[Beth]

When VS can tell that you modified something while it was open, but not using VS, it should prompt you to reload the file.

If the DLL in your solution explorer?

What happens if you go to File - Vault Source Control - Refresh Source Control Status?