I am automating a TFS branching process with DotNet core 2.2. We are using TFS 2018.
How can I create a new branch in TFS source control using C#?
I have been able to queue a build a do some other operations.
Microsoft.TeamFoundation.VersionControl.Client.VersionControlServer has a method for CreateBranch but I have not been able to instantiate a VersionControlServer. Old documentation shows this is done with TfsTeamProjectCollection but I can't find any libraries with that class.
A lot of the MSDN documentation goes to obsolete or deprecated references.
UPDATE
I have found that TfsTeamProjectCollection is in MicrosoftTeamFoundationServer.ExtendedClient if I install version 14.83.0, but the current version is 16.143.2.
When I drop back to this old version I get runtime errors associated with versions of other packages. If I downgrade them there are several build errors so I will need to refactor. I can't downgrade, and shouldn't have to.
What has replaced this?
Update
For the test from my side, It works properly with .net framework project.
But not able to do with .net Core, it's even not able to restore related Nuget packages.
Yes, it's using namespace Microsoft.TeamFoundation.VersionControl.Client and Assembly: Microsoft.TeamFoundation.VersionControl.Client
Sample code for your reference:
var server = new TfsTeamProjectCollection(accountUri, new VssBasicCredential(string.Empty, personalAccessToken));
var vcServer = server.GetService<VersionControlServer>();
var changesetId = vcServer.CreateBranch("$/Demo/Main","$/Demo/Dev/Branch", VersionSpec.Latest, null, "Branch Comment", null, null, null);
You could see the official documentation for this class at: VersionControlServer Class
To get this Microsoft.TeamFoundation.VersionControl.Client.dll, it has been been moved into a Nuget package--Microsoft.TeamFoundationServer.ExtendedClient.
Take a look at this similar question here: Where can I find Microsoft.TeamFoundation.VersionControl.Client.dll in Visual Studio 2015 installation?
You can use MicrosoftTeamFoundationServer.ExtendedClient NuGet package, then you will have all the classes and methods:
var tfs = new TfsTeamProjectCollection(new Uri("tfs-server-url"));
tfs.Authenticate();
var versionControl = tfs.GetService<VersionControlServer>();
versionControl.CreateBranch("sourcePath","targetPath", VersionSpec.Latest);
Related
We installed the free version of TFS 2017 and created a new project. We now have source code with history. The PM decided they wanted to switch from Agile to Scrum so a lot of commands were run to try to do this. These commands came from a blog found on the internet. The supervisor then decided that it should NOT have been switched to scrum and said we needed to switch back to Agile. So similar commands were run to try to do that. Now the Project Management portion of our project is broken. We can't run queries and the work items are corrupted. I want to try to just install a new instance of free TFS 2017 and copy/move the source code (TFS, NOT GIT) to the new instance and start over with the PM stuff. Can we do this or is it a lost cause.
Actually we do not suggest OPs to do the process template change in a single team project. Take a look at this MS documentation (here) ...
You can change the process a team project uses from a system process
or inherited process to an inherited process. You can only change team
projects to use another process that inherits from the same system
process. That is, you can change an Agile-based team project to any
process you created from the Agile system process as well as to the
Agile process. Whereas, you can't change a Scrum-based team project to
an Agile-derived inherited process.
There is no need to set up a totally new TFS instance, you could simply create a new team project based on Agile and then move your source code and workitems to that new team project.
Since you are not care about the history info about your original team project, it's more easier to achieve this, simply remove your old workspace mapping and map to the new team project.
To move workitems you can export them to Excel, create a new Excel connection to , that is connected to the new team project, and then copy the workitems and pushing them from the new Excel file into the new project.
If you insist on moving the code to new TFS server, you just need to back up your local code and directly check in them as pending changes in the newly created team project on new TFS server.
More details please refer the answer from Andrew Clear in this similar question: Visual Studio Team Services: How to migrate from Agile to Scrum process template
If you want to only move Source code from one Team Project Collection to another Team Project Collection, one of the crude workarounds is the following, when you are ONLY requiring SRC code moves.
Create a workspace and check out all SRC from the source Team Project in the source TPC.
Create a new Team Project in the new TFS instance.
Remove the binding files from the SRC dumped out in (1), or better yet just move it on the disk to a new directory and remove all SRC binding files.
Then add the source (from the above step 3) into the new Team Project you created in the target TPC you created in (2) above (or it could also be into an existing Team Project you already had in the target TPC).
Once again this is ONLY if you don’t care about the other things such as WITs and Reports from the older Team Project, and you only care about the Source Code.
In addition, you can use the following tool Timely Migration.
I want to upload android source code on TFS using visual studio and my server side is written using C#
how to create repository for android on TFS
UPDATE1:
Please read Get Started documents first:
Get Started with Git and Team Services
Get Started with TFVC
UPDATE2:
If you just want to isolate the documents from the source code, you can create a new folder under the project, or create a new branch to store the documents, of cause you can create another repository, it's based on your requirements. Please see this article for details.
Do you have any special requirements? If not, nothing different with other projects. Assuming you are using TFVC, just try following below steps:
Connect from Visual Studio or Team Explorer
Create a team project
Add repositories
Configure your workspace and check in the source files/changes.
You can create the repository individually for client and server projects as needed.
If you just want to upload the existing source code to TFS, you just need to Put an existing solution under version control
Please see the overview documents for more information.
If you are using Android Studio, you can install the Team Services Plugin for Android Studio with Git repositories used. See here fro more info.
I'm new to using TFS 2015 ALM with the integrated source control. Previously I've used the ALM with a non Microsoft SCM product.
I am used to creating the ALM project which has no linkto SCM.
Now, when creating a new TFS project I am prompted to create a new source control project. I cannot figure out how to use an existing source control project. surely the ALM is not directly linked to an SCM project of the same name, there must be a way of configuring the SCM project used.
A TFS project will always be created with one Source Control repository. You're free to use it or not.
It is possible to create a Process Template that doesn't initialize a Source Control repository, but none of the default process templates are configured this way. I'd not recommend removing this option from the Process Template as it makes upgrades and migration harder.
I have an TFS server installation that through time has gone through upgrades from TFS 2005 to TFS 2008 and then to TFS 2010.
During the lifetime of the installation a lot of projects have been created and different project templates have been used. MSF Agile 4.0, 4.1, 4.2 and 5.0. and a few MSF CMMI ones.
What I would like to do is "replace" the project template used for all these projects to use a new one common one: Microsoft Visual Studio Scrum 1.0.
I am aware that TFS project templates are used as templates for creating new projects and cannot modify the tfs projects definitions after creation.
Uptil now only the version control and build server part of TFS have been used and there are no existing work item types.
Additionally all projects and build scripts are depending on the source code paths stay the same.
As I see it I have the following options:
Create new TFS projects using the correct project template and then move/branch the source code to the new project.
All code is moved to a temporary team project.
The old project is deleted
New project with the original name and correct process template is created
Code is moved to the new team project
Temporary team project is deleted
All the build definitions needs to be to recreated which is not an option.
The source code move/branch will "mess up" the versioning history
By messing up the versioning history I mean that when you move source code it will behind the scenes do a delete + source rename on the original location and the history will still be located in the old project. This will make searching in the history difficult and if I actually delete the old project I will loose all the history before the source code move.
This is really not an option for me since there is years of code change history that is needed to for supporting the different applications being built.
Use the TFS migration tools to migrate to another TFS project
This has the same downsides as the first solution
Replace/import work item types, install new reports, create new SharePoint sites
For each tfs project
Delete existing work item definitions using "witadmin deletewitd"
Import each work item definition from the new process template using "witadmin importwitd"
Import work item categories using "witadmin importcategories"
Delete old reports in project folder in report server
Upload the report definitions from the new process template
Modify data sources used for the reports using the report manager to point to the correct shared data sources (TfsReportDS and TfsOlapReportsDS)
Modify the report parameter ExplicitProject default value to "" (empty string) and disable prompt user option.
Export the documents in the old SharePoint site using stsadm
Delete the old SharePoint site
Recreate the sharepoint site using the TFS2010 Agile Dashboard site template
Activate site feature "Team Foundation Server Scrum dashboard"
In TFS Project Settings -> Project Portal Settings: Enable "team project portal" and ensure the url is correct. Enable "reports and dashboards refer to data for this team project"
And finally..
Process the Warehouse
Process the Analysis Database
Even though that this involves a lot of small steps this looks more appealing because
this option will not force me to move the source code and my existing build definitions will be intact.
My question:
Are there other ways to achieve the replacement of work item types that I haven't mentioned?
And/or am I missing any steps in last solution?
Given that you aren't using any existing work item types, your final proposal looks like the best option.
After deleting the old reports and exporting the SharePoint documents (you could also use Windows Explorer instead of stsadm), there are actually two commands in 'tfpt' that will help you. This will reduce it from 14 steps down to 5 or 6 steps.
tfpt addprojectreports Add or overwrite reports for an existing team project
tfpt addprojectportal Add or move portal for an existing team project
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
Your first option is IMHO your best shot.
You can branch the sources from the old team project to the new team project. With TFS 2010 you can see the history also from the branched location. So you don't loose functionality in here.
The Build is just an msbuild file which is stored in source control. The only thing you have to do is actually copy the build definitions. You can do that either manually, or you can create a little app that does that for you.
I am in the process of learning about using the TFS SDK to fully control what Team Foundation does programmatically like:
Creating new Workitems(is this the same as creating change requests?)
Creating new team projects
Creating a new Source code branch,etc.
I am developing a Windows app that can include all these tasks so it can be automated.
I know I have to use VersionControlServer.CreateBranch() to create a source branch. And, is it true that we cannot create new Team Project using the SDK? What about in VS 2010 SDK? I know how to manage workitems programmatically.
Anyone has suggestions on how to create new change requests?
If you take a look at the TFS SDK it has examples on creating work items, working with version control etc.
To create a new Team Project then you must use Visual Studio to do that - however in VS 2008 SP1 with the latest version of the TFS Power Tools installed you can make use of the new tfpt createteamproject command to script this process (though all those dependancies need to be installed on the machine running the application that you are thinking about building)