CODEWITHSUNDEEP
gitazure-devopstfvc
arame3333
arame3333

Reputation: 10203

TFVC: Build is looking in the wrong directory

I was having problems with Git in VSTS and so I was instructed to switch to TFVC. The hope was that all I need to do for the build process is switch the "Get Sources" to the new TFVC repository which has the same code.

What I am finding in the build is that it is failing, it is looking for packages in C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise and this directory does not exist as I am not using VS Enterprise, instead I am using Professional and the folder exists for that.

So how can I get the build process to look in the right place?

UPDATE FOR ANSWER: What I found during the migration from Git to TFVC was that some items that appeared to be checked in were not found in the build. One item missing from the build was Automapper and I decided it would do no harm to update the Automapper Nuget package to the latest version. The idea was that if I check in and build again, would Automapper continue to be found missing in the build? I was surprised to find that when I checked, a whole number of other artifacts also appeared for the checkin. So I checked them all in and the build succeeded this time. I do not know why this happened or if anyone would benefit from this answer.

Upvotes: 1

Views: 59

Answers (1)

Marina Liu
Marina Liu

Reputation: 38136

Based on your last post, your build was queued by Hosted VS2017 agent. So the Enterprise VS2017 used to build your project is located on VSTS server not your development machine.

If you need to build project by your development machine, you should setup a private agent on it.

Upvotes: 1

Related Questions