TFS 2013 New Application Wizard from Solution File

Trying to utilize the New .Net Application Wizard for a .sln file in source control that we have in place. The solution file has two projects, one of which is a dependency of the other. Our build order and dependencies are setup correctly in the solution, but when we go to the wizard to add the applications, after detecting the two applications giving us the checkboxes, selecting the class library that is the first in the build order references a relative path in source control (based on the location in the team projects) and gives us a Server 500 error. I've seen this very relative path mentioned in the Event Viewer on the server for the ASP.Net error when Buildmaster failed.

My question is thus:

Is the issue with our solution file, with the TFS extension (or Windows-SDK extension) or should we just avoid using this wizard altogether?

Any help is much appreciated.

Product: BuildMaster
Version: 4.1.4

It's likely an issue with the WindowsSDK extension. It might be easiest to just create a Standard Application and add the following actions (the same as the recipe would):

Get Source

Apply Label (%APPNAME%-%RELNO%.%BLDNO%)
Get Labeled (%APPNAME%-%RELNO%.%BLDNO%)
Optional: Write Assembly Version
Optional: Install NuGet Packages (if any)

Build

Build MSBuild Project
Create Build Artifact

Deploy

Deploy Build Artifact

You may want to build each project independently and capture each into separate artifacts as opposed to the Solution, that's up to you.

Okay, we're still figuring out how to setup the dependencies though as required deployables, as we're having trouble with building.

I assume this might be a good bug to post to github for that particular recipe, correct?

We're relatively new to this environment, so thanks for the patience.

Sure, feel free to post that to GitHub. What types of projects are these? Typically you don't need to worry about dependencies if you get the source for the whole solution and just build the .csproj as MSBuild will handle that for you in the same way as if you built it in Visual Studio.