I'm using Microsoft Visual Studio .NET 2003 Enterprise Developer Tool(Visual Source Safe 6.0d). As per my knowledge, In VSS there is a provision for admin to provide the access(r/w access or checkin / checkout access) to the given specific user for a perticular folder(that is having no. of different types of files) in a project. But I want to know, Is there any provision at Admin level to provide the access for a specific file (that is in a folder) to any given user.
There is no file-based security setting support in VSS, as far as I know
Related
I am given a sharepoint location from my organization. I have to save my Visual Studio project onto this location and use it as a repository/TFS/AzureDevOps like integration where my team members can access the project, map them to their space and work on the project.
Please help on this
Agree with #Daniel Mann. SharePoint is used to share and manage content, knowledge, and applications to empower teamwork, quickly find information, and seamlessly collaborate across the organization. SharePoint isn't designed to be a source control tool for code. Based on my knowledge, it won't integrate with any IDEs, and it does not have customized GUI to manage source control code, etc.
There are many version control tools, like Azure DevOps Services, which can host unlimited free private repos and start free.
I've searched MSDN and this site (as well as a pile of web searches) and not found anything obvious ... I do see a similar question here about using an existing source control folder -- and the note that TFS apparently stores some project settings there (and thus needs one whether you use it or not).
We're using a non-TFS source control tool -- and I don't want newcomers "accidentally" storing source versions in TFS. So, I'd like to disable the creation of a TFS 2010 source control "tree" when I create a new Team Project in VS 2010.
There may be other solutions to this problem, though, and I'm open to suggestion. For example, if TFS really does need to store some internal data -- how about a way to simply prevent any source code checkins (that is, let TFS use the source control project as needed, but prevent users from adding files)?
TFS has extensive permissions settings.
You should be able restrict check in / access to source tree by permission.
I'm trying to configure Visual Studio 2010 with team foundation server.
I'm getting following screen
I can add only windows users into user groups
Now, I need to create windows user for every remote user or is there any way get it work?
How can I give access permissions to remote users?
This set of users is specifically meant to have root control access to your TFS configuration. Only provide the names of people that need to be admin for your TFS farm.
Regular remote users are configured in the TFS system itself, not here. When a TFS administrator creates a collection he can delegate the administrative rights to another (group of) person(s). These persons can create TFS projects in that collection and assign roles for administrator, contributor or reader at project level.
See How to add new users to TFS 2010 for more details.
We have single server with VSTS 2010.
can we install one VSTS and use with two different users in the same time ?
what is happen is this :
User_B can open projects from User_A but it time he need to change something
jump windows and asked to save the project..(*.sln file)
It sounds like what you are doing is probably a license violation.
Also, this is really not the best way to go about multi-user software development. If you have more than 1 developer working on the same project - you need some form of Source Control. There are plenty of best-of-breed free/open-source version control systems (subversion, git, mercurial, to name a few) you can use.
Developers should each develop on their own machine, and then check-in changes to a source control system.
Currently most of the development in the company I work for is controlled via VSS. I've installed Team Foundation Server for the development at our site.
There is a future project that will involve new developement, but referencing older code bases hosted in VSS. My preference would be to use TFS for the new development, but I'm unsure if a VS2010 solution can have projects using different source control providers.
You'll need to change the source control provider manually (unbind - change SCC provider - bind) each time.
No Visual Studio does not allow for mixing source control providers within a solution at the same time.