I'd like to clear my (as I call it) not checked-in items history of source control in visual studio.
These items are there because in a project I did include the project via adding the actual windows folder to the team foundation server; and there are bin files and resharper files that are never going to be checked-in.
Everytime I have to check-in something, I need to scroll all the way down to my clearly added project files; and that's annoying.
Thanks in advance.
These files should never have been added to source control. Your best bet is to delete from the TFS.
You should only check-in files that need "version control"; Resharper files, bin\ & obj\ folders, *.suo, *.user files, etc. should be removed from TFS.
When adding new files to TFS, it has a filter no to add these to source control. See here on MSDN for more details.
Related
I have a bunch of Word files in VS2015 solution. These files had ben modified by end user and I am trying to update them in TFS source control. What I did was I checked them out in my solution and copied user copies into solution folder in Windows10 File Explorer. I was hoping that the pending changes would include new files copies. However, when I checked them in I had a TFS message reading there were no changes done in those files. Am I missing something? Please, help if you can. Thank you.
Possible duplicate with this question How to have TFS 2010 detect changes done to files outside of Visual Studio?
The best solution is using reconcile in TFS. After you compare a server folder and a local folder, you can reconcile the differences between the folder contents and between files that have conflicting pending changes in your local folder. Detail steps as below:
Open the Source Control Explorer
Right-click on the folder with the changes and choose Compare
Select the files you want to reconcile (press CTRL+A to select all files)
Click on the Reconcile button
Set the options in the Reconcile Folder Differences dialog. Make sure Files that do not have pending changes is set to Check
Out
Click OK
If you have local changes the Check Out dialog will be shown. Set the preferred Lock type
Click Check Out
I'm using Visual Studio Professional 2015
Version 14.0.24720.00 Update 1 with TFS 2013 (30723.00).
Let's say my local TFS workspace is d:\workspace
Some of my existing projects which are not in source control are lying under d:\projects and I want to add them to TFS.
When I copy Solution_A from d:\projects to d:\workspace\solution_a_team\Main, where solution_a_team is the team project folder with a branch named Main, Team Explorer says Detected: x add(s) - where I'm assuming x is the number of files transferred.
What's confusing is that the number x is not consistent. Sometimes all files are detected sometimes only small percentage of files. What am I doing wrong, or what's the best way to check these folders into TFS?
First, please check whether there are some files adding in the excluded changes. There are included changes and excluded changes in the pending changes page.
Also, it's not recommend to just copy files or projects to the workspace folder. It's not the right way to add files in source control.
If you want to add a solution in source control, just open the solution in solution explorer and right click the solution ,in the explorer select "Add solution to source control" and choose the location you want add to. If the solution have added in the source control, there will be a lock icon in front of it.
If you want to manually add files in version control, the simplest way you can Drag the folders or files from Windows Explorer into the folder in Source Control Explorer . More details please refer the link from MSDN: Add files to the server
Moreover, you can also achieve this through TF command, or check in files through windows file explorer directly by TFS Power Tools.
I'm running VS Enterprise 2015. This infernal thing keeps wanting to add my solution's .vssscc file to version control. My .tfignore has this line:
*.vssscc
The other items in .tfignore are working fine, but for some reason this one is not. There are no other .tfignore files in the directory tree. Surely I'm overlooking something, but I'm pulling what's left of my hair out trying to figure out what. Any suggestions?
*.vssscc stands for Visual Studio Solution Source Control File
When a solution is added to source control, a corresponding .vssscc file is created. The text file contains connection information and an exclusion file list, similar to the project hint file. This file is temporary and exists only in the source control database.
As a rule of thumb, we'd recommend letting Visual Studio handle those files. It'll add to source control the files it needs and leave out those not needed.
.vssscc files also manage the solution bindings, so better to have them controlled (by VS) .
Also, visual studio can have problems with the source control bindings if the files it needs are not under source control.
We are experimenting to use Microsoft Team Foundation Server Source Code Control as a replacement for SVN.
Therefore, it would be great if the friction for this transition would be minimal.
For example, in SVN, whenever I create new files in the folder, and then use "Tortoise SVN Check for Modifications", I get a master list of Added Files, Deleted Files, and Edited Files.
I know that in TFS SCC in Visual Studio, the equivalent is the Pending Changes Panel. However, this panel only lists Edited Files. How can I get new files listed in that panel, too, just like SVN does?
The workflow really depends on whether you are using Local Workspaces or the traditional Server Workspaces. As you are coming from SVN, Local Workspaces would probably be a good fit.
Local Workspaces (New to TFS 2012)
Local Workspaces are TFS's attempt at DVCS and actually gives you a much more SVN-Like experience. The pending changes window with local workspaces is divided up into the following areas:
Included Changes - This is effectively files that are already in Source Control that have been changed.
Excluded Changes - These are all files within the workspace that are not in source control. This is like your Added files in SVN.
Server Workspaces
Server Workspaces are the traditional TFS workspace approach. An item is not in Source Control until it is explicitly added.
There is a much more detailed article on the differences here: http://msdn.microsoft.com/en-gb/library/bb892960.aspx
Drag and drop your new files into the right folders in the Source Control Explorer in Visual studio and then there will be asked if there are also files that need to be excluded from the source control. If that is done they are in the Pending changes window. The implementation like SVN is starting from Visual studio 2012 but then still it can give issues and not be in that panel.
I see this is an old question but I believe the answer is in Visual Studio's "Pending Changes Panel" itself. Notice the "Excluded Changes (nnn)" section. Just below that heading you should find "Detected: nnn add(s)". You can see your 'new files' listed there.
For what it's worth, I find the "Pending Changes" an unwieldy feature in that it seems it's never context aware. I find that I often have to "weed through" many, many files that are simply not relevant to the solution/project(s) at hand.
In our source control, we have a dependencies folder. It is not part of any project, but shared by a few. I have to update a couple files in there, but not sure how to go about updating these files and adding check-in notes.
How can I do this? Thanks.
EDIT: I should mention. These are DLLs, so it's not like I can edit them directly.
Go to Team Explorer
Open the Team Project
Double-click the "Source Control" node
This will display the Source Control Explorer, which will let you check out and check back in.
You can manually check out the files, then edit them in your favorite editor, and manually check them back in.