Hi all,
I've been using TFS for about 4 months now on a large project with hundreds of assemblies and thousands of code files all checked into Source Safe.
For the most part, my whole team loves TFS, and don't want to work without it. My team is spread across the globe.
I have two questions:
1) Is there a way to "hide" or set inactive a project in Source Safe? We have a project that should no longer be used, but I don't want to delete it. I just want to hide it. I could set the permissions on that project so that no one can access it, but I was wondering if there was another way to do it.
2) Has anyone else experienced a situation where you checkin your files, including a comment, and Visual Studio indicates that the file is checked it, but no one else can see the changes? When this happens, we have to check out the file, or file set, then check it back in again, then it sees the changes. This is very odd, and has caused a lot of issues with builds because the engineer doesn't know their files are still checked out.
Thanks,
Bill
William G. Oliver | | William Oliver | 1) I assume you're talking about Source Control Explorer (SourceSafe is a whole other product). The only way to hide items is to deny Read permission. You can delete them, but (a) users can turn on "show deleted items" (b) deleted Team Projects will always show up
2) People have reported this, but I've never seen an actual repro. I'd suspect either user error or a problem with the IDE's cache (something that's fixed when you click refresh). In all cases, the History toolwindow should reveal exactly what has & has not been committed.
| | Richard Berg MSFT | Thanks, Richard.
Yes, I was talking about Source Control Explorer :-)
Regarding item 2, we have been having this problem even after closing Visual Studio, then reopening it. We have even gone as far as deleting the workspace and re-creating it, and it still indicates that the files are checked in. You are correct about the history window. It does show that the files were not updated, but the only way we know that is to check the history of the files after each checkin.
I'm wondering if there might be an error being generated when checking in a file, yet the files are being marked as read-only anyway? For example:
begin tran
checkin files
if error rollback else commit
mark files read-only
Is there an error log in TFS that I can check to see if errors are being logged?
Thanks again,
Bill
William G. Oliver | | William Oliver |
|
index > Team Foundation Server - General > TFS and Visual Source Safe 2005