Windows file to TFS - How do I do it? - tfs

We're a small shop and have legacy VB6, Classic .ASP, .NET 1.2 - 3.51. We installed the product successfully, but since depending on the code which needs changing we fire up the respective IDE Visual Studio x. How do we go from no source control to TFS?

You will probably want to look at the TFS 2008 Power Tools. One of the features that is available in the Power Tools is Windows Explorer integration, so you can get/checkout/checkin by right clicking the file(s).
Your other choices are to use the VS2008 / TFS 2008 client to do your SCM operations (which means you need to switch between multiple IDEs), or you could use the TF.EXE command line to do your SCM operations.
If I misread your question and you're asking how do you get your legacy code into TFS, you'll need to go into the TFS 2008 client and do the following:
Map a workspace to a folder on your hard drive (or network).
Copy your source to the folder.
In TFS 2008, click on the "Add Files" button.
Select the folder you just copied everything into.
Add them.
Check in.

Related

Can we have only VS Code instead of Visual studio professional version for connecting TFS?

I am trying to evaluate VS Code instead of VS professional version for my work.
Can I use VS code with TFS for daily operations like?
Create work space?
Get latest source code?
Code checkin?
Shelve set?
Code review request ?
etc?
As jessehouwing mentioned most of that are supporeted except for the Code Review bits.
You need to install Visual Studio Team Services Extension for Visual Studio Code
The following are the current features supported by the extension:
Execute all basic version control actions such as add, delete, rename, move, etc.
View local changes and history for your files
Include and Exclude changes (and move files between the two states)
Merge conflicts from updates
Check-in and update local files
Associate work items to check-ins
Provides an integrated TFVC Output window
Support for a TFS proxy
Supports workspaces created with Visual Studio (via tf.exe) or the JetBrains IDEs and Eclipse (via the Team Explorer Everywhere Command
Line Client)
To start using the TFVC features, review the documentation and
check out the TFVC Source Code Control for Visual Studio Code
video which shows you how to configure and use the TFVC features.
The extension supports TFVC across Windows, macOS and Linux (with
separate configuration instructions for macOS and Linux; see
video).
If you’ve never used the extension before, we also have a
walkthrough to get you started.
Source here : Official Release of TFVC Support for Visual Studio Code

Adding files to Team Foundation Server from web interface

Is it possible to add a new file (or new version of a file) to a TFS project via the web interface without using Visual Studio? There are some code artifacts, such as PS1 scripts, which we may want to keep under source control, but the owners of such files may not have Visual Studio even installed.
No, this functionality is not available in TFS 2013.
This does exist in TFS 2015 (and in Visual Studio Online), but if you are using TFS 2013, you have a few options:
Install the standalone Team Explorer. Despite the name, you do not need to have Visual Studio installed - if you don't, it will install a standalone version that can communicate with a TFS server.
Use the command-line interface. (Also available with the download above.)
Yes it is possible.
In our companies real world example we, have a CI build set up at work that does nothing but code sign powershell files. This was a huge carrot to get the systems engineers to leverage source control. The don't use Visual Studio though. They seem to like using powerGUI which has TFS integration support.
In the TFS 2015 web interface, yes, this is possible.
If you are asking how:
To add a new file, right-click on the folder (in the folder
hierarchy on the left) and there's a menu option to "Add file(s)...".
To edit a file (add a version), open the file contents in the right pane, and
there's an "Edit" button.

Why does TFS Power Tools 2012 not recognise newly uncloaked project?

I have TFS Power Tools 2012 installed on my PC.
I recently uncloaked a project in TFS and performed a get operation to bring the project folder into my private workspace (using server-side for backwards compatability with VS2010).
Whilst in Visual Studio, there is no problem - I can check it out and check back in.
However, Power Tools does not recognise the new folder in windows explorer. In other words, all other projects have the green-arrow icon overlay, but this one doesn't. Right-clicking on the folder also does not bring up the TFS context menu.
Does anyone know what I may have neglected to do? I have tried deleting the folder and doing a "Get specific..." to bring it back in. Hell, I've even done a repair on TFS Power Tools and restarted; the behaviour remains unchanged.
This is not my problem (the rest of my projects do show the icon overlay)...
Possible duplicate here maybe...
I have noticed Power Tools sometimes has conflicts with icon overlays, particularly when they compete with others (like SVN).
It can also conflict when you have multiple workspaces on your PC. As you mentioned, make sure the project is uncloaked in both workspaces.

Visual Studio Team Services (cloud) - Server Workspace

We have several of our projects at my company in source control using Visual Studio Team Services (visualstudio.com). For the life of me I can't figure out how to get the workspace on my machine to flip to a Server workspace type. We don't want multiple checkouts and we want to get latest when we edit a file, and server workspaces (as I understand it) are the only way to accomplish this. Is it even possible to use server workspaces with the "cloud" version of TFS/Visual Studio Team Services?
Thanks!
Connect to your server with Visual Studio
Go to Team Explorer
Go to Settings
This part can be a little tricky so I attach a screen shot:
Under "Team Project Collection" go to Source Control
On the new dialog go to the second tab - Workspace Settings
So as you can see it is pretty obscure and I believe it is on purpose. By default the workspaces are of type "local" and these have their benefits. You may want to check out this article to make an informed decision: http://msdn.microsoft.com/en-us/library/bb892960.aspx

TFS source control without Visual Studio?

Is it possible to use TFS source control without Visual Studio? I have to put some files in some source control, those files are stored in a folder in some server, that is something developed in Oracle forms. I just need to add those files in some source control and I'd like to use TFS for that. Any tips or tools could we use for this?
TFS is likely to be overkill for a few files in a single folder, but if the TFS infrastructure is already in place then it will work.
You will need Team Explorer (or, on non-Windows) Team Explorer Everywhere installed to give you the client tools. But you can perform all source code operations with the tf.exe command line (or equivalent from Team Explorer Everywhere).
Team Foundation Server Power Tools has Windows Shell Extensions that provides integration
with Windows Explorer and the common file dialogs. With this integration, you can perform many source control operations without having to run Visual Studio or a Team Foundation command-line tool.
see this answer but you will need to make sure you have tfs server running as well to connect to. Would it not be simpler to use git/mercurial/svn...{any other free source control system}?
I am one of the lovers of TFS, but I think in your case if you don't need to use Team Explorer or Team Explorer Everywhere (which will need command line used) for none windows I suggest to use SVN sub version (VisualSVN Server) it's open source and it has integrated OS shell (TortoiseSVN ) right click menu which will be easy than using command line
Vlad: That is true, but this important: I have used the "Shell Extensions" for a while only to realize that it does create problems. First of all, the "Shell Extensions" does not report errors during a check-in; it only unexpectedly stops, and the window closes.
Also, the reason I am looking for an external "Source Control Explorer" is that if you delete any file from Window Explorer that was under Source Control by TFS, the Check-In procedure will fail saying that there is a file missing. The correct way to safely delete a file is to do it through "Source Control Explorer"; the check-in then works. Usually not a problem, unless, like me, you have a Java project and have no integration between NetBeans & TFS.

Resources