tfs2017

问题 We have Team Foundation Server 2017 setup on our internal server which we build our .NET code in our sandbox environment, but would like to be able to push out new build definitions or updates remotely (to our client - production server) either manually or in an automated manner? 回答1: Yes, you can export and import the build definitions in TFS 2017. In you case, if you have the permission to access and create build definitions from the remote server, then you can export/import the build

问题 I have TFS 2017 Express on my server machine and Visual studio Community 2017 RC as well. I keep getting this error message when I browse to "Pending Changes" option in Team Explorer in Visual Studio An item with the same key has already been added. I dont have any pending changes on my PC and none of the PCs that are connected to the same server. What is the issue? 回答1: From the time of your post I assume you have been able to overcome this issue. But for the others like me who run into the

问题 We are moving the TFS-server out of our development-domain to a new domain. The users in the development-domain should still be able to authenticate to the TFS-Server, either with their developement-domain credentials or a new set of credentials from the new domain. One problem is that we cannot create a trust between the domains. What is the best solution here? I've found some links where they use TFS-proxy server but they are not clear if the domains are trusted or not. Or is it possible to

问题 We have to upgrade TFS version from 2012 to 2017. The problem we are facing is we have some team projects in TFS 2017 lower environment and some team projects are in 2012 production instance. We want to migrate 2012 team projects and 2017 team projects to a new TFS 2017 production instance under one team project collection. We need some help in defining the upgrade/migration strategy keeping this scenario in consideration. Please let us know if someone can lend help. 回答1: It supports to move

问题 I have a project where it is needed to change some files during build process. I have to use Powershell to do this. I have already configured all required steps to do this. All steps work on my client pc. The Build server has the same configuration. Vs 2015 (for TF Powertools 2015) and VS 2017 installed. When I queued a Build, the build fails at the point where he tries to get the Workspace. Maybe this is because, the build agent creates only local workspaces? At this point the required

问题 I've installed TFS 2017 in Windows server 2016. I just want to know the following where are the installation logs stored in server? Where are the transaction/history logs stored in server? Correct me if am wrong, is it possible to backup history of logs and attach to TFS upgrade [in case of TFS version upgrade]? 回答1: The installation log file generally store in temp folder. Typically this folder is : C:\Users\{name}\AppData\Local\Temp And the Configuration logs stored in: C:\ProgramData

问题 Using the Microsoft.TeamFoundationServer.Client (15.112.1) to connect to a TFS 2017 Update 2 server we can get details about an existing PR like this: var connection = new VssConnection(collectionUri, credentials); var client = connection.GetClient<GitHttpClient>(); var pr = await client.GetPullRequestByIdAsync(pullRequestId); Also, we can create new PR like this: var pr = await client.CreatePullRequestAsync( new GitPullRequest { SourceRefName = "master", TargetRefName = "develop", Title = "

问题 We recently upgraded from TFS 2010 to TFS 2017. We have build notifications set up for certain projects that send an email whether a build succeeds or fails with details of the build. Previously this email included a list of any unit tests that failed as well as a list of associated changesets. However, after the upgrade to TFS 2017 neither of these are included in the build notification emails. As far as I'm aware we didn't do any modification to the alert templates for TFS 2010 to get the

问题 We are running on-premises TFS 2017. I would like to create a release definition for our QA team which will create a Docker container running Windows 7, and deploy our release build to it automatically. Once the deployment is done the QA team should be able to log onto the container to test the app. No manual running of a MSI installer or Setup.exe. Ideally each queued release will create its own container with its own copy of the released build. Is this possible? Or recommended? All our

问题 My company has a on-premise TFS 2017 instance. I know how to install and update extensions through the web interface, but it's pretty tedious. I'm wondering if there's a quicker way to do it with tfs-cli . 回答1: Took me awhile to figure this out for some reason. At first I thought tfs-cli could only be used to publish extensions to the Visual Studio Marketplace, but that's not the case. Here's how to do it for on-prem TFS: Generate a personal access token You can follow the instructions here.