Weird problem with access to source control
Hi,
We've got a strange problem wrt source control. We have two Team Projects, let's call them Project A and Project B. Both projects are worked on by pretty much the same people, so the Contributors group is the same in both projects. Team Explorer and Source Control Explorer work fine, but Workspaces do not. For some reason, some people don't see Project A in their Workspace explorer (they do see Project B). The security settings for both projects are equal, I've checked that. Source control works fine, but since these people cannot see Project A in the Workspace explorer, they are unable to set bindings for that project (we have them bind from "$/" now) and they cannot add solutions to source control.
Any idea what this might be?
Thanks,
Wolfgang
Wolfgang,
This is a known issue related to permission for Contributors for the builds after Beta2.
Workaround:
You wouldn't be able to see the first team project in source tree in "Browser For Folder" dialog brought up from Add/Edit Workspace dialogs. However, you would be able to manually able to type the folder name (i.e. $\Project A) and that would work.
The issue is fixed in the latest build.
Thanks,
Bhavik
Bhavik,
Thanks for your swift reply. Unfortunately, your workaround only fixes half the problem. Is there also a workaround for Contributors to add a new Solution to Source Control?
How are the projects ordered, by the way? Is it alphabetically, so if I create a new bogus Team project called "__Bogus" or something like that will that be the new "invisible" project?
And by "fixed in the latest build" I take it you refer to an internal build (in any case, we have decided not to install another version until Beta3). Will this issue be fixed in Beta3?
Thanks again,
Wolfgang
