you'll find some remarks here with our wishes in bold.
removing a folder from visual studio deletes the files from the repository. When a single file is removed, VS ask if we want to remove it or delete it. It would be great to have the same for folders, or not to delete the file from repository by default as VS may not give Fortress the opportunity to ask. We all made the error and commited the action (see below). We're not used to fortress yet, but deleting a file requires some warning.
The SHIFT key from VS 2005 Fortress Pending checking, doesn't work as expected (often selects from the first item). The result is that many files that should not have been checked in have been checked in.
Once again a dialog appears, but the problems is that it shows the full path, and all the time it's truncated. I think the path of the ckeck in dialog should either be relative to the top most file/sln; or that the column should be set to the largest item name. (I had 10 files to check in, didn't count the 3 unexpected). You have to resize the column for each check in...
When you link a fortress item/bug to a checkin, the modified files appear under the item(
). This is great for the company, however I do not want this information to be shown to customers; even if they cannot acces the source code. Would it be possible for this information to be filtered for WEB only users ?The files modified were: Repository Path Version
Last wish, I would like the "SourceCode control tab" to be removed from the tabs for WEB users. I would have liked that they do not know our source code lies here. Just like the admin tab is hidden from them and non-admin users.
Last question Do you have a roadmap of your product. Even if it's not a commitment it would be interesting to know.
Anyway we really like Fortress and really hope you will take some, if not all, features into account for the next release.
Xavier