tfs2015

We just upgraded to TFS2015 (onsite) and I'm trying to set up a build that will do the same thing as my xaml builds but I can't seem to get the same files built. Here's a picture of the xaml output directory that I use to publish the site. To get this I navigate to the build folder then drill down to the _PublishedWebsites\BOTWSitecoreWeb folder: Here's a picture of the solution explorer: So as you can see BOTWSitecoreWeb is my startup project and it forms the basis for the website. So to publish this website I simply copy the folder: _PublishedWebsites\BOTWSitecoreWeb to my IIS directory.

In Team Foundation Server 2015 in build definition I use my custom variables defined on Variables tab. Is there any way to access them in PowerShell build step like predefined variables can be accessed e.g. "$env:BUILD_DEFINITIONNAME"? Thank you [disclaimer: I work on the new build system] I often advise folks to use the cmdline task or a cmd script to print out the variables (call set on windows, env on *nix). There's docs etc... but actually running it will show exactly what is really available. Add cmdline task (in utility) with tool = cmd and arguments = /k set Variables on the definitions

In order to emulate the "PerProject" option in TFS 2013's XAML build in the new Build 2015 task based builds, I'd like to be able to pass the SolutionName to the msbuild commandline arguments without having to manually set it every time. I'd like to do something like: /p:OutputPath=$(Build.BinariesDirectory)\$(SolutionName)\ Where I'd like MsBuild to infer the $(SolutionName) parameter. But when passing this on the commandline, the new task runner will substitute the $(Build.BinariesDirectory) with the correct target path and leaves $(SolutionName) alone. Unfortunately MsBuild subsequently

I recently upgraded my team's build server to TFS2015 from TFS2013. Everything is going smoothly, except from within my IDE, I can no longer open the Build Explorer . As far as I know, I have not changed any settings within my IDE, but builds now open as if I had selected the right-click context menu for Open in Browser available for completed builds. This behavior started after I finished the TFS upgrade. As far as I know, I am the only one affected on my team. Does anyone know how to convince Visual Studio 2015 to use the Build Explorer window again? The build explorer is now available again

I am using the new VSO scriptable build system with an on premise build agent. The build publishes the following assets to an internal file share. Install Symbols to our internal symbol store. When a build is deleted either manually or based on retention policy the associated assets are not deleted. Should I expect that assets are deleted when the associated build record is deleted? In 2015 RTM and currently in VSO, server drops are deleted when a build is deleted but drops to UNC shares are not. We have work on our backlog to address this. EDIT: In 2015 QU2, this is enabled. Also if you on

We have a build definition in TFS 2015 that have worked fine with Visual Studio 2015 projects and solutions. We have now decided to upgrade to Visual Studio 2017 and thus we would like to target Visual Studio 2017 in the Visual Studio build task. We have installed Visual Studio 2017 on the build agent. Unfortunately the only options available int the Visual Studio build task are 2012, 2013, 2015 and Latest. We have tried latest but it does not find Visual Studio 2017 on the build agent. It won't work with the msbuild task either. I have a similiar issue and resolved by installing VS2017 in my