I was setting up a new build definition today and noticed there is an option 'Copy build output to the following Source Control folder'. I don't believe I have seen this before. It appears to me from searching google that it might be new as of TFS 11 (AKA TFS 2012) which I do not have installed on my system (or any system in my company network to my knowledge). My company uses TFS 2010 right now.
I went to another user who is able to view build definitions and it also was present when the build definitions were viewed.
This is what i see:
My questions:
1) Was this a part of TFS 2010 and I am just not remembering seeing it?
2) If this IS part of TFS 2010, how to enable this option (it is disabled).
3) If this is NOT a part of TFS 2010, how did it get there?
Yes, it is part of TFS 2010, but I have no idea how it got here!
I believe this is for those who use TFS 'as a service' (when you
have no file share to copy it to). According to
how-can-i-copy-build-output-to-the-source-control-folder
I have this in TFS/VS 2010 (SP1):
Related
My team is performing an analysis on which TFS version to upgrade to (from 2010).
One issue that we have faced daily is that TFS 2010 will log pending changes on files that are unchanged. For example, if I edit the JavaScript on HomePage.aspx, while leaving HomePage.aspx.cs and HomePage.aspx.designer.cs unchanged, the later two files will still log as pending changes, resulting with 3 files in the pending changes tab.
This post addresses this issue, and even has a semi-appropriate answer. But I'm wondering, has this issue has been fixed in terms of using TFS 'out of the box' with TFS 2017 or 2018? Do I really need to use TFS Power Tools with the latest version of TFS to get around this annoyance? I see many people saying that Power Tools doesn't solve the issue for all configurations.
That's Visual Studio behavior, not TFVC. I would expect that the behavior will remain the same regardless of the version of TFS you use.
That said, you should upgrade to 2018, period. There's no benefit to upgrading to a version that's already supplanted by a newer major release.
#Daniel is correct. This behavior remains no matter which version of TFS you are using. You could see HomePage.aspx.cs and HomePage.aspx.designer.cs belong to HomePage.aspx, TFS treats them as one file. If you check the history of HomePage.aspx.cs and HomePage.aspx.designer.cs, you'll find no new history produces, as during check-in, TFS detects there is no changes for these two files:
I installed Visual Studio 2015 Enterprise RTM and only seeing "references" from Code Lens. We are using TFS for source control. I expect to see related commits from TFS. Based on this article, I have everything enabled in options:
Here is what I see in VS:
Is there anything wrong with my VS setup?
The TFVC lenses that are part of CodeLens only work when connected to a version of Team Foundation Server that is running the background job that generates the historical data. This means that you need to be running at least TFS 2013 or 2015 in order for this feature to work. Some features require a specific version of Visual Studio.
It is also possible that your server admin has disabled indexing on the server, one can do that using the tfsconfig codeindex command on the application tier.
We are planning to upgrade from Tfs 2012 to Tfs 2013. Can anyone help me understand the difference in process templates between them? We use all three process templates for different projects.
The changes are very minor, except for:
The introduction of Portfolio backlogs.
Test Plans and test Suites are now Work Item Types (TFS 2013 update 3).
The AgileConfig and CommonProcessConfig files have been merged to a single file inside the template
The minor changes:
Git support for the Source Control options
Stackrank type fields are now hidden by default (because Agile task boards are now features of the Standard CAL).
Tag field support through the API.
The easiest way to visualize all differences is by comparing them through the TFS Team Project Manager which can be downloaded here.
TFS 2013 did not work well with our existing workspaces defined on remote network drives. TFS 2012 did work with this configuration.
After working several hours with our System Administrators, we gave up on trying to get the trying to get the existing network drive workspaces to work with the TFS 2013. Converting the workspaces to local drive locations enabled us to work with TFS 2013.
I'm trying to migrate from TFS 2012 Update 2 to TFS 2013.
Following the documentation I installed TFS 2012.2 on the new hardware, backed up/restored the databases, then installed TFS 2013 as an upgrade.
I can see the Team Project and the builds. The problem is when I right click a build to queue up a new one and click on the Parameters tab I just get a blank panel. My best guess is there was an error loading the parameters. Note those builds worked fine in TFS 2012.2.
If I create a new build from scratch and I use their new default template (TfvcTemplate.12.xaml) I still get the same error.
I don't see any errors in the output window or the event log.
It turns out it's a known bug with VS2013 connecting to TFS2013
The VS2013 hotfix has been released. Taken from here.
For future reference, this was fixed in Visual Studio 2013 Update 1 (see KB 2911573).
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.