I have a visual studio project which contains 3 different projects within single solution in Visual Studio 2019.
TestMainApp
TestSubApp1
TestSubApp2
I created a project on DevOps with the name TestApp and have pushed this solution on DevOps repository but only One project TestMainApp is pushed on the repository and remaining two are excluded.
Can some please explain how to push all the projects on DevOps repository. I have already pushed sigle project based solution on DevOps and was no problem at all.
Related
I have been working on TFS 2017 update 3 from past couple of years and now I have started working in new team where they are using TFS 2015.
In TFS 2017 Web, all the Build Definitions we had we used to keep\save them into their respective folders as their was option of Manage Folder present under Build Tab but here in TFS 2015 Web, I don't the see the option of Manage Folders and have to keep\save all the Build Definitions under one tab.
Is there any extension available in the marketplace or way by which I keep all the Build Definition in a more organized way in TFS 2015?
I am afraid Manage tfs2015 doesnot support Manage Folders feature. And I failed to find an extension that was available on the marketplace to achieve this.
You need to upgrade tfs2015 to a newer version in order to use the Manage Folders feature.
You can check out below document for more information:
Upgrade your deployment to the latest version of Azure DevOps Server
How can I connect to on-premises TFS using Visual Studio Code? Is that possible the same way as in Visual Studio?
If you need to use Git, all you need is Visual Studio Code. Git is a built-in feature.
In order to also use TFVC you'll need to install an extension. You'll need Visual Studio Code and the Azure Repos Extension and a recent version of Team explorer and/or Team Explorer Command Line Client.
To edit Azure Pipelines (available in Azure DevOps Server 2019), you'll need to also install this Azure Pipelines extension.
The naming is a bit confusing, but these Azure DevOps extension also work with recent version of Team Foundation Server and Azure DevOps Server (new name).
First you need to install the official Azure DevOps Extension for Visual Studio Code which released by Microsoft.
It supports both TFVC and GIT version control type.
Clone your Git repository
With Git, the extension uses the remote origin of your repository to
determine how to connect to Team Services (or your Team Foundation
Server), in most cases you will need to have a Git repository already
cloned locally. If you intend on cloning an existing repository, do so
before proceeding. If you do not have a Git repository cloned locally
but already have a Team Services account (or a Team Foundation Server
instance), you may create a local repository (via git init) and once
you set the "origin" remote for that local repository, the extension
will detect the change to the remote and attempt to contact the Team
Services account (or Team Foundation Server).
Create your TFVC workspace
With TFVC, the extension uses information about the current workspace
to determine how to connect to Team Services (or your Team Foundation
Server). Workspaces can be created using the Visual Studio IDE,
Eclipse or with the JetBrains IDEs (e.g, Android Studio, IntelliJ).
Note: At this time, you will need to have a local TFVC workspace already available on your local machine. More information about the
difference between the two types (and how to determine which one
you're using) can be found here.
You could also take a look at below videos to help get you started using the extension quickly:
Set up the Team Services extension for Visual Studio Code - If
you haven't used the extension before, this video will show you how
to set it up, create a personal access token and get up and running.
Walkthrough of the Team Services extension for Visual Studio
Code - This is a walkthrough of most of the features of the Team
Services extension.
TFVC Source Code Control for Visual Studio Code - This video shows
you how to set up the TFVC support on Windows and demonstrates much
of the functionality available for Team Foundation Version Control.
Above is for Windows machine, if you are working on Mac, please take a look at this answer.
Note:
VS Code will leverage your machine's Git installation, so you need to install Git first before you get these features. Make sure you install at least version 2.0.0.
You need Team Foundation Server 2015 Update 2 or later.
We migrated from TFS 2015 to Azure DevOps. The XAML builds also ported over to Azure. But we need to migrate them to Azure build pipelines as the XAML builds are still running on On premises TFS Server. We have hundreds of builds and cant manually create new pipeline for each build one at a time. Can some one help please?
XAML builds are still supported with Azure DevOps Service (with some limitations), see official response from Microsoft, in my answer here.
We're currently in the process of migrating from TFS to Azure DevOps and we're not planning on upgrading any of our legacy XAML builds (we're creating vNext builds going forward), as they were successfully migrated into Azure.
I figured out a way ( I am not done yet)..
we can call the api and export the build defs into json files
Use the Json files to port them over to the new Build defs. (Porting involves creating new builds programatically and using Azure Api .. + the data from Json files we just exported).
We have a Team Project we created in 2013. The web site of the project allows Git Repos to be created, but in Visual Studio 2017 the Git repos we created are always Offline and exhibiting other odd behaviors (loading TFVC's interface in Visual Studio even when connecting to a Git repo within it for example). I used Fiddler to check out the traffic and noticed that this particular project is missing the SourceControlGitEnabled = true flag. A project we created a year and a half later DOES include the SourceControlGitEnabled flag and works properly.
Is there a TFS Team Project setting we can alter/enable or do I have to create a new Project with Git as the repo and migrate everything to it?
When you create a new repo in the Team Project in TFS2013, there should be a warning as below:
Note that some versions of Visual Studio will only provide full Team
Explorer integration with a repository that has the same name as the
team project. Users may need to manually clone this new repository to
use it in Visual Studio.
This maybe the limitation of TFS2013 with GIT, either manually clone this new repository to use it in Visual Studio or create a new Project with Git as the repo and migrate everything to it, both should be work.
Is there any way to check in code from Xcode to TFS 2015 on-premises installation? Even if TFS is just acting as a go between for Xcode and Git? The main thing we'd like to be able to do is for iOS code to be checked in to TFS with changesets recorded, and work items/bugs available.
Any suggestions? We are not looking to move to VS Team Services / VS Online.
you have 2 options.
The best option is to create a new TFS Team Project with Git for source control. Or you can add a Git repo so an existing Team Project. This is a standard Git repo, but hosted in TFS. It works just like any other hosted Git repo. Clone the repo and off you go.
If you cannot use Git inside TFS and you must use TFVC then you can use git-tf. This is effectively a bridge between a local git repo and a centralized TFS TFVC repo. This article should get you started
Both VSTS and TFS 2015 include full support for Git-based source control projects. You can follow MSDN article Share your code in Git using Xcode to push your project to TFS.
After pushing your project to TFS, you'll have full history and work item available: