Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 7 years ago.
Improve this question
I would like to disable multiple check-outs for our TFS projects. Here is how I expect it to work:
Bob checks out File1.cs.
Joe double-clicks on File1.cs in his Visual Studio Solution Explorer and tries to modify it buts sees an error message saying that someone already has that file checked-out so he cannot check it out.
I've tried setting it up like this in Visual Studio for both Bob and Joe:
Within Team->Team Project Collection Settings->Source Control...->Workspace Settings Tab I changed the default workspace type from "Local (recommended)" to "Server".
Within Team->Team Project Settings->Source Control...->Check-out Settings Tab I changed Enable multiple check-out to be unchecked.
Within Source Control Explorer->Workspace Combobox->Workspaces...->Edit...->Advanced->Location I changed "Local" to "Server".
Still, however, Bob and Joe can both check-out the same file at the same time. Is there some other configurations options that need to be set?
The issue (as pointed out by Edward Thomson) was that step 3 had not been performed on all of the users' workspaces.
You can also uncheck Enable file merging and multiple checkout in Team Project Collection Settings.
But you have to do this to any type of file you want.
http://msdn.microsoft.com/en-us/library/ms252452(v=vs.100).aspx
Related
i am wondering if there is a way to incorporate a checklist in a pull-request.
The reviewer shall check some things mentioned on that checklist and enter some result, like 'done' or 'not applicable' or 'found an issue'.
It would be very nice if a not fully answered checklist could block a pull request.
A direct approach could be to paste the checklist as one or several comments.
This one seems tedious, and does not block the PR from completion...
Another approach could be to create a template work-item related to the pullrequest, containing the checklist, or one work-item for each entry in the checklist. Once again tedious and non blocking...
We are using:
Microsoft Visual Studio Team Foundation Server
Version 16.122.27409.2
--> TFS 2018 Update 1
Assume you are using TFS 2017 and later version, then you can achieve that by applying Branch Policies.
Navigate to Admin -> Version Control
(http://server:8080/tfs/DefaultCollection/{Project}/_admin/_versioncontrol)
Select the specific Repository and Branch --> Enable Protect
this branch --> Enable Check for comment resolution -->
Required
Create a pull request, paste the checklist as one or several
comments, Markdown is supported for comments, you can copy the
checklist like below format as a checkbox:
- [ ] check 1
- [ ] check 2
Thus the policy will block pull requests from being completed while any comments are Active. So, you can change the state of the checklist comments to Closed once they are all checked.
This question already has an answer here:
Is there a git style amend option in TFVC?
(1 answer)
Closed 5 years ago.
For my project I use VS Team services, linked to Visual Studio 2015.
When I want to check in a new commit, I can do this:
In solution explorer, right click on project
Source Control -> Check In
Enter a comment, click 'Check In'
Now I would like to amend my previous commit, since it wasn't finished completely when I checked it in, in GIT this is possible with the git commit --amend function.
How to do this in VS Team Services? Preferably from Visual Studio itself.
You can't really, there are 2 approaches you can take with TFVC:
Make a second commit and don't worry about it, this is my approach for small typos, etc.
Rollback the changeset, and check it in. Then rollback the rollback and make additional changes and check in again. This is my approach if I totally stuff something up.
Related Question/Answer.
All you can ammend in TFVC is the Check in Comment, this can be done by viewing the change set in VS, editing the comment and pressing "Save".
This question already has answers here:
How to ignore files/directories in TFS for avoiding them to go to central source repository?
(6 answers)
Closed 8 years ago.
Using tfs online I have a mapping to C:\Work
There I have some directories I don't want to be versioning controlled and I keep them out of source control. Problem is VS 2013 show them as detected changes. This are temporary folders (like EmailPickup) that I want to never 'watch' on those folders. Is there any way to do that so Visual Studio stop suggesting me there are detected changes to include ?
found a simple way to doing it.
On the detected changes modal (Promote Candidate Changes is the title) you can right click and ignore by extension and / or folder.
This question already has answers here:
VS2012 return to a normal TFS checkin window?
(5 answers)
Closed 9 years ago.
The TFS Pending Changes has moved from its own window to a tab in the Team Explorer.
The pending changes are now displayed as a treeview that reflects the structure of the solution.
How can I display the pending changes as a flat list/grid that can be sorted by various columns?
It's possible to add "TF.exe Checkin" as an external tool, see answer for a similar question.
However it pop-ups after some delay, which is annoying.
I found that if you have only a few recently checked-out files that you want to check-in together, using pending changes tree view is quicker. However if you need to check-in some of many check-out files, "TF.exe Checkin" list is more convenient.
Alternatively try TeamPilgrim Free VS extension -
a replacement for Visual Studio 2012's Team Explorer inspired by the Visual Studio 2010's Team Explorer by Stanley Goldman
After experimentation, I've found it's a link on that page, Show all included changes:
#G_P added this as a comment to a different answer, but I think it deserves an answer slot of its own.
The TeamPilgrim extension includes a replacement pending changes window/tab.
http://visualstudiogallery.msdn.microsoft.com/79e9baa7-ea8b-4335-86ba-ae929bf67222
There is a "pending changes" filter on the Visual Studio 2012 Solution explorer. It will display all your files that are checked out the same as the Team Explorer, but without all the extra garbage about Notes or Work Items.
http://blogs.msdn.com/b/visualstudioalm/archive/2012/08/14/showing-files-with-pending-changes-or-files-that-are-open-in-visual-studio-2012-solution-explorer.aspx
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I have two build processes setup in TFS 2010. One build starts when any developer checks code into TFS. The second build runs every night at 12:30am. I can see the builds have a priority of Normal in the queue. However no queued build ever is run until I change the priority to high. They will sit in the queue forever until the priority is changed.
It appears there is a normal priority build in the queue that is stuck. However I cannot find it. I can select Any Build Definition, Any Status, and Any Build Controller and not see anything but these builds queued up. I can run them all and the next day I have queued builds again. I say this because I see the Build Service is configured for port 9192, which leads me to believe there is or was another Build Service on port 9191.
Any idea how to resolve this issue?
I had this same problem where only builds that were "Above Normal" or High priority would actually build.
I tried restarting the build service, controller, and agents with no effect. There were no errors in the Event Log.
It turned out that there were 2 rows in the tbl_BuildQueue table for build definitions that I had recently deleted. Changing the status of those rows from 2 (Queued) to 16 (Cancelled) fixed the problem for me.
Here are some links that helped me figure this out:
http://networkprogramming.wordpress.com/2010/10/27/default-controller-cannot-be-deleted-because-there-are-builds-in-progress/
http://blog.hinshelwood.com/ghost-team-foundation-build-controllers
I ended up removing a normal priority record from the table tbl_BuildQueue. This appears to have resolved the problem.
Deleting rows from 'tbl_BuildQueue' fixed it for me.
I had a similar issue with builds not... building! Had to restart the controller/build agent which seemed to fix it.
While you're in there, the Build Configuration checks the Event Log for errors, anything showing up?