I have included a folder with several sub folders in TFS, which is not a VS solution. Basically it is a bunch of XML files mainly, which are manipulated via some GUI. How can I exclude certain subfolders from check-in while check-in the 'solution'/folder?
You can manually include or exclude files from a check-in: the UI is a bit different if you are using the 2012 TFS client (Team Explorer) or an older version. It is described at this page.
On the Customize which files are ignored by version control section, you see a way to 'permanently' exclude folders or file types from a check-in.
Related
I am working in a group project in visual studio and I need to check-in my work every once in a while to Team Foundation Server. However there are some files in the project that I don't need to check-in to the server and I have to manually exclude them each time I check-in. How do I include some files or even a project into a permanent no include list?
You can use a .tfignore file (VS is a bit variable in picking up changes to this file, it doesn't seem to apply changes to files that are already pending changes). This uses the same format as .gitignore.
I'm new with source control but since we are more than one developer in our company I started introducing git with Visual Studio 2013 Express and the Team Foundation Server. Now when I create a new project and add it to source control it seems that sometimes one random cs source file in the project is excluded from version control. In the Solution Explorer there is no check-in icon infront of the file. Also there is no other icon infront of it and if i publish the repository to the server the file isn't there.
I have no idea why the file is excluded and how to include it.
Is there any way to show linked files after a VSS to TFS migration? Additionally, how do you link files in Visual Studio 2013?
As Edward Thomson wrote, there is no such thing as linked files. Excerpt from How To: Migrate Source Code to Team Foundation Server from Visual Source Safe.
The main issues that you are likely to encounter are due to some differences in the way TFS handles version control in comparison to VSS. For example, because TFS does not support sharing of files, shared files are migrated by copying the version of the file at the time sharing began to a destination folder. Also, because branching in VSS uses sharing, the migration of a branched file results in the file being copied to the destination folder in TFS source control. As TFS does not support pinning, to help you locate items in TFS source control that were previously pinned in your VSS database, the VSSConverter tool labels any file that was pinned with the “PINNED” label.
I have some source code and other artifacts such as images that are not created in Visual Studio 2010. I want to put them into TFS 2010 version control, how can I do this?
TFS does not care what the format of your files is; you can use TFS to store any type of file - whether it was created in Visual Studio or any other program. This is true of all TFS versions.
The comments already somewhat address how to add a file to Source Control using Source Control Explorer; Once you have a workspace mapping, copy files or folders into a mapped folder in your workspace, right-cick on the folder you added the file to in Source Contol Explorer and select the option to Add Items to Folder; This will launch a wizard that you can use to let TFS know that you want to add the selected file(s) or folder(s) to source control - it can be any file on your computer.
After the files are added, check-in yor changes by right-clicking on the file in Source Control Explorer or by using the Pending Changes window (View menu -> Other Windows -> Pending Changes). Almost every source control operation in TFS is a 2-phase commit that involves first letting TFS know what you want to do (like add or delete a file) and then actually committing that change with a check-in.
You can also perform these steps using TF.exe from the command line or the Shell Integration Feature that is installed seperately with Team Foundation Server Power Tools (TFPT). Please note that whilst you can list and view the contents of files in TFS using the Web Access user interface, you cannot check-in or check-out files using that interface. Also, you will not be able to perform any source control changes without Visual Studio or at least a free version of it, named Team Explorer.
The only qualities of files that matter to the behavior of TFS are if the file is a mergable file type or not and what the encoding of the file is; however, in most cases the default setings in TFS will be fine for you. Mergeable file types are files that TFS will enable merging for; Examples of mergable file types are text files; Non-mergeable file types are file types that you would not want to merge, like pictures or Microsoft Excel files. You can read more about Managing File Types on the Microsoft site.
Since the WCF proxy generated *.datasource files give problems with long file paths when checking them into the TFS 2010 source control system, I would like to be able to add them to the list of files that, by default, are not marked as a pending add to be checked-in.
Is it possible to configure file exclusion by extension at TFS project or collection level?
Ah, found out that (at time of writing) this is a recognized wish on the backlog of the Visual Studio team:
https://connect.microsoft.com/VisualStudio/feedback/details/419915/allow-tfs-to-exclude-specific-file-extensions-from-being-add-to-source-control
That is a pitty ...
Well, i'll investigate the File Pattern exclusion policy to be deployed for this purpose: http://social.msdn.microsoft.com/Forums/en-AU/tfsversioncontrol/thread/03ca91cf-4332-43bb-a358-96d8fe8633dd