We have an on-premises version of TFS 2018. We have set up a user to have access to the collection under the "Version Control" tab with the following permissions.
I have then drilled down into the projects under the collection and set some of the files (web.config), to be Read = Deny.
I would have presumed that this setting didn't allow the user to see the contents of the file when opened in Visual Studio. Is this the case or have I misunderstood the setting? If so how can I restrict access to certain files in TFS.
I have a Windows 2012 system with Visual Studio 2010 installed. It worked fine on this system. Today I installed Visual Studio 2015 Community Edition on it. After installation, when I try to open existing solutions with Visual Studio 2010, the loading becomes very slow. Also, I am not able to save any modified files in the solutions. It seems that all the solution folders and files have become read-only. When I tried to change the attribute in Explorer, I was shown "You will need to provide administrator persmissions to change these attributes", even though I already logged in as administrator.
When I tried to save an ordinary text file, I was also not able to because some process is locking it. The same thing happens to C:\ as well.
Also, I notice that if I right click and select "New" from the pop-up menu in Explorer, the only option is "Folder" (this only happens for D:\ and not C:).
What could be the problem?
The local security policy was changed when I installed Visual Studio 2015 Community Edition. In Security Settings -> Local Policies -> Security Options, "User Account Control: Run all administrators in Admin Approval Mode" was changed to "Enabled". All I needed to do was to change it back to "Disabled" and then restart the system. The problems described disappeared after that.
We currently have our Source Control settings set to enforce a Check-In Note called 'Reviewer' is set for every check-in in our projects.
However, for two of my developers, the Reviewer field is not showing up, and they can check in their changes without having to fill in the field!
I've cleared the Cache (as mentioned in many posts, this one in particular) on one of the developer's machines, but this did not correct the problem.
I've grabbed the "devenv /log" output from both developers and compared it to mine, but nothing jumps out at me there either - the versions of Team Foundation assemblies that both are loading into their IDE's are the same as mine, and any 'Power tools' that we load are also identical other than tools that we don't share at all.
We are using TFS 2013 Update 3, and Visual Studio 2012 Update 4, Visual Studio 2013 Update 4. The Developers on my team might typically switch between VS2012 and VS2013 at least once a week.
When you have a custom check-in policy, everyone will need to have that check-in policy installed on their development workstation.
My issue is that I cannot add SourceSafe Database for source control within Visual Studio 2010.
Our team was initially using VSS for source control in Visual Studio 2010. During an evaluation of TFS, I switched my source control to TFS. It will be a few weeks before a decision is made on TFS, so I needed to switch my source control back to VSS. However I'm now unable to add a SourceSafe Database in Visual Studio.
Steps to Reproduce in Visual Studio 2010:
1) Access the 'Open SourceSafe Database' form via Tools->Options->Source Control->Plug-in Settings-->Advanced
or via File->Source Control
2) The list of available database is blank so I choose 'Browse'.
3) I browse to the srcsafe.ini file for my VSS database and select it.
4) I'm promted to confirm the Database Name - Click OK.
5) The database does not appear in the 'Open SourceSafe' Database form. The list of available databases is still blank.
Note that I can add the database fine outside of Visual Studio using VSS directly. However the databases I add via VSS do not appear in the Visual Studio forms.
I'm suspicious that this is related to "down-grading" from TFS to VSS which may not have been heavily tested at MS.
Any assistance is appreciated.
I installed VS2010, then i install VSS, then i have the same problem, cant connect to my VSS it by default opens (TFS)
the suggestion here, to reinstall, dont sound good, did a bit more searching and found this:-
http://social.msdn.microsoft.com/Forums/en/vssourcecontrol/thread/6c927805-bca6-445b-b406-0a0da8fa21d3
and found the easy solution that 'CletusLoomis' is looking for:
simply:-
hanks for your post.
Could you please try the following steps?
Open VS2010, then choose the menu: Tools->Options, then click "Souce Control"
click drop-down box under text"Current souce control plug-in", use "None", rather than "Microsoft Visual Source Safe"
thats it, problem solved!
:)
hope this helps someone else who found this page via google.
To do that you must run Visual Studio 2010 as Administrator. Just click on Icon using right button, Go to Properties, Compatibility, at the botton of screen you should mark Run this program as administrator.
That's all.
Must exist some file that the permission should be granted to all users, but instead of searching for the file, I preffer this solution.
Regards,
Luiz Ricci
My Visual Studio 2010 had very similar symptoms: having selected Visual SourceSafe 2005 in the Options I had the only menu option: Launch Microsoft SourceSafe
While following the steps provided by 'visual' (as of Nov 30 '10 at 8:00) I have found the following registry key, which needs to be switched to 0 to enable the SourceSafe menu options to be displayed in Visual Studio 2010. Once the registry key value has been changed to zero Visual Studio needs to be restarted and .. voila! Now I have an additional menu option Open from source control...
The registry key is as follows (for 32bit OS it would need to be slightly modified): HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SourceSafe\Namespace Extension\DisableOpenFromSourceControl
Now, why it was disabled by default is beyond me.
Your installation of VS might be corrupted. I would recommend uninstalling VSS, VS, and TFS and then reinstalling VS and VSS. Unfortunately, this could take 4+ hours, but it should fix your issue.
I don't believe that my VS installation was corrupted. I do believe there is a bug in VS 2010 which does not allow me to use VSS for source control after having used TFS. Fortunately for me, our team decided to go forward with TFS for our project's source control. I never had to solve the problem. I believe that reinstalling Visual Studio alone would have been enough to solve the issue.
I had the same problem with Windows 7, Visual Studio 2010 and VSS. I noticed several things:
VSS as standalone program does always work on my system.
VSS works perfectly in my projects, if the UAC Level is the lowest, but not with the default UAC Level.
If I open a project file with VSS source control, Visual Studio tries to read the registry. It fails to read/write the keys in the registry with access denied. Therefore I changed the permissions in the registry of the SourceSafe keys to full access for all users. Now, VSS works perfectly on my system with default UAC security level.
I faced the same problem.
I am using Visual Studio 2010 and my projects added to Visual SourceSafe 6.0
The VSS database list was not prompted on my machine as well.
After a number of attempts for over 3 hours. Finally got a solution.
I run the VS2010 using Run As Administrator option. The VSS database list was visble.
I think the issue might be due to Access Rights of Registry in Windows 7.
What a nightmare this has been. Ultimately, you can set in domain or local policy.
Local Security Policy\Security Settings\Local Policies\Security Options\User Account Control: Run all administrators in Admin Approval Mode - Disabled
This means anyone in the administrator group does not have to have approval (The Dreaded Run as Administrator)to be an administrator. Can be set locally as above or domain wide. Solved a lot of problems for us.
Options -> Source Control -> Make sure the "Current Source Control Plugin" is correctly set.
Mine was set to Microsoft Visual Source Safe (Internet), and should have been Microsoft Visual Source Safe.
First, make sure you can view the database by visual source safe explorer.
Then, trying to proceed with these step...
Open Visual studio as Administrator.
Log in visual source safe by the database path. (it still disappears the database in "Available database" list.)
I have a problem that is described here: TFS: cannot set up new build
I use Visual Studio 2008. Unfortunately, the solution provided there, didn't help.
I tried to remove and add again my TFS server - no help. Also, it's not a problem with security policies or lack of proper right, because I can initiate a new build, with the same user through Visual Studio 2005, also installed on my computer.
In addition my colleagues have no problems at all.
If someone else have experienced similar problem - I will appreciate any help !
If your getting the red cross it is likely that it is a permissions problem. From the 'Team Explorer' window within VS2008, right-click on your project node and select the 'Team Project Settings->Group Membership' menu option. From there trace down the group that your user belongs to.
Next, again right-click on your project node in the 'Team Explorer' window, this time selecting the 'Team Project Settings->Security' option. Within this dialog, find the security settings for your user group. Ensure that the 'Allow' checkbox is set for the 'Start a build' property. Confirm any changes and exit.
I have found that it is best to restart IIS on the TFS server to ensure that the chances are picked up.
Good luck !
Here is what I did. I don't know why the problem is fixed, but it's ok ... for now.
I installed the Microsoft Team Foundation Server 2008 Power Tools and exclusively installed the integration of the tools with Visual Studio. Then I did the following instructions again:
I decided to add my user (just me, not from some domain group) in to the permission menu options ... Then, from security option menu I checked the 'start a build' option at my user and restarted the Visual Studio.
After restarting the Source control menu is a little bit different from what it was before, but at least I can start builds now. Hope It's forever :)
Is the server running TFS 2005 or 2008?
Have you tried running the diagnostics in the BPA Tool?
EDIT:
Team Build had many breaking changes between 2005 and 2008. VS 2008 cannot create new build definitions on a 2005 server. Details: http://blogs.msdn.com/buckh/archive/2007/07/27/team-build-compatibility-between-2005-and-2008.aspx