TFS 2017 does not create targets for counterfeiting

I have a TFS 2017 Update 2 on-prem update server with VS 2017 Enterprise installed. Our assembly contains the Unit-Testing project, which contains the Fakes assembly and runs locally on dev machines. When you build on TFS, the build fails with

The type or namespace name 'Fakes' does not exist in the namespace 'Our.Product' (are you missing an assembly reference?)

(i.e. skips / fails to generate file Our.Product.Assembly.Fakes.dll

)

I have additional signatures suggested here .

What puzzles me is that there is no mention of fakes in the build log (other than the error itself and the paths in which MSBuild looks for the file), even with debug verbosity. He is not trying to create an assembly of fakes.

Are other steps needed? We are using vNext assembly definitions.

Update: This is the build step that works now, before /tv:15.0 /p:VisualStudioVersion=15.0

there was.

enter image description here

+3


source to share


1 answer


Refresh

Using the latest version for msbuild arguments such as /tv:15.0 /p:VisualStudioVersion=15.0

may fix this problem.




First, try using the RDP Build Service Account to the Remote Build Agent and manually start the build to see if the build is generated.

It will narrow if it's related to your environment in the build agent. Make sure this is the same as your local machines.

If the assembly is also generated, the issue might be related to the assembly definition settings. Check if you are using the correct version of msbuild. For vNext build also enable verbose debug mode withsystem.debug=true

+3


source







All Articles