Tfs workspace not updating
But for those that have to experience it with Team Foundation Server 2010, you might hear that it’s easier to call it a day than continue working.
Before going further, it’s important to discuss and understand what’s allowed the improvement: the local workspace.
Click the save button to update the workspace with your filter changes.
If the workspace is shared with co-workers, then they automatically receive the saved changes as well.
A Team Foundation Server workspace contains a set of working folder mappings.
These mappings represent the location of client-side folders on a local disk and the corresponding repository folders.
It is this folder that is specified as the Local Project Path, when defining your Version Control Configurations.
In TFS, the TFS workspace is used to map a local working folder on your PC to a Source Control Folder within a TFS project.' workspaces for Enterprise Architect version control, as 'local' workspaces do not support the application of checkout locks to files.
Enterprise Architect relies on the presence of checkout locks to ensure that Packages can only be checked out exclusively and that a given Package is not already checked-out in some other project (for instance, in a Private Model deployment).
Therefore, Enterprise Architect must enforce serialized editing of its version controlled Packages.
As a consequence, it is important that TFS is configured to use 'exclusive checkouts' for XML files.A workspace is a critical feature of Team Foundation Server since it’s what allows the differentiation between the changes that have been made against the data stored on the server and your working copy of files.