CODEWITHSUNDEEP
c#visual-studiotfs
ruffen
ruffen

Reputation: 1719

Visual studio linked files with TFS - automated build does not work

I have two Visual Studio solutions, one for WebApi and one for WP7 development, I am linking some dto files from WP7 solution to WebApi solution, this works great.

I just added the solutions to Team Foundation Service preview, and tried to get it to build. Since the linked files doesnt get added to source control, I cant build the project, because it cant find the linked files.

I tried adding the WP7 solution to the same directory in TFS, but no luck.

Edit- More information: I get: CSC: Source file '....\TennisTracker.Client.Ui\TennisTracker.Client.Core\Models\GameDto.cs' could not be found

Then I add the client solution under "Edit build definition - Process - 1. Required - Items to build. I get this: C:\a\src\TennisTracker.Client\TennisTracker.Client.Ui\TennisTracker.Client.Ui.csproj (140): The imported project "C:\Program Files (x86)\MSBuild\Microsoft\Silverlight for Phone\v4.0\Microsoft.Silverlight.WindowsPhone71.Overrides.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

In the error console, in visual studio, it gives me this error: Error: API restriction: The assembly 'file:///C:\Users\markka\AppData\Local\Temp\VSTFSBuild\ae65cc1a-850e-4112-8c34-96674d8c79f3\2052550994\nunit.core.interfaces.dll' has already loaded from a different location. It cannot be loaded from a new location within the same appdomain.

The workspace is set to the entire directory, containing both solutions

Upvotes: 1

Views: 847

Answers (1)

Dave Hogan
Dave Hogan

Reputation: 3221

Under the build definition you can define the workspaces which you can point / setup paths to the other project.

Best thing to do is post up the build error output and I can then hopefully let you know the exact path you need to setup

Upvotes: 2

Related Questions