VS.NET 2008 - Files remain "Unmodified" after save

[EricAnderson]

Vault: v5.0.1 (18729)
VS.NET 2008

Files remain unmodified after Save (either Ctrl+S or toolbar button press) until the Plugin refreshes itself or I manually select "Refresh source control status" from the File menu.

Searching both the Support forum and KB yielded no help. And I should note that I recreated the situation with "Detect modified files using CRSs" checked and unchecked.

I have recorded a SWF of the incident if you would like to view it.

Any other information you would like?

[Beth]

The client only updates upon a refresh or some action in the client that will cause a refresh. A save in Visual Studio won't cause the client to refresh to change the status. In the Vault GUI client, you can make the refresh happen more often in the Tools - Options - General under the setting "Automatically Refresh Every."

[EricAnderson]

A save in Visual Studio won't cause the client to refresh to change the status.

The concern here is that if you proceed with a "Commit" before the Plugin refreshes, the Plugin will not upload the changed file resulting in a "lost" change.

Would it be possible to add "Visual Studio --> Save" to the list of actions which cause a refresh of the Plugin?

[Beth]

Are you working with Visual Studio integrated with the Vault? In general, the client does catch when edits happen and are saved to disk, but admittedly, I made a few other assumptions about how you are working.

If you are working in an integrated fashion, are you using the Classic or Enhanced Client?

I will need you to capture some Client Side Logging. Setting up logging for the Enhanced or Classic Client as well as for the Vault GUI client are all explained in the link. Once you have logging set, could you recreate the scenario and email the logs? Send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread and the logs.

[EricAnderson]

Hi Beth!

I have emailed you the requested log file.

We are running the Enhanced client in Integrated mode.

Hope this helps!

[Beth]

We worked on this issue offline. The issue involves the Enhanced Client with VS 2008 and doesn't involve the GUI client. The solution was unbound. Binding the solution resolves the issue. A bug was logged on the issue for when the solution file is not bound.

HS: 218681
F: 15154