tfs2015

I'm having troubles with NuGet package restoring during a TFS Build 2015. Since some packages require NuGet 3.x client, I've configured the new scriptable build to use a custom NuGet location where I've placed the executable of NuGet Command-Line 3.x beta . Whenever I run a build, all packages can't be restored and NuGet throws the "Unable to find version..." error: Unable to find version '1.1.10' of package 'Microsoft.Bcl'. Unable to find version '4.0.10' of package 'System.Threading'. Unable to find version '1.1.37' of package 'System.Collections.Immutable'. Unable to find version '1.0.0' of

We have just installed TFS 2015 (Update 1) on-premise and are trying to create a Continuous Integration/Build system using the new TFS Build system. The build works fine, and gives me a green light, but when I look at the default build it has only built the binaries from the bin directory, and there seems to be no easy way to deploy the app on-premise to a local server. There are two deploy options for a filesystem copy, and a powershell script, and it would certainly be easy enough to use them to copy files to a new server, but since the build only built the binaries, I don't see a tool to

We are currently testing whether we can replace our current build server (TeamCity) with TFS 2015 Build. Does anyone know of TFS 2015 has built-in Nuget Server like TeamCity. Thx Harshil Lodhi Package Management (NuGet with npm and maven coming soon) is currently only available for VSTS. The on-premises support for Package Management will come in the next version of TFS. Source - TFS Feature Timeline for 2016 VSTS and TFS now provide built-in support for Maven Package Management to compliment its support of NuGet and npm. https://blogs.msdn.microsoft.com/visualstudioalm/2017/05/22/visual

How to step up TFS 2015 Update 2 to delete artifacts when build is deleted? Is this possible? EDIT: Add retention screen shot I am using the default retention policy but it is NOT deleting artifacts from the drive. EDIT: Add Copy and Publish Build Artifacts EDIT: Add Working Folder I added a powershell to display all environment variables and it said my workingFolder = E:TfsBuilds\Agent1_WorkPlace\5\s Do you a powershell to set workingFolder to default? Here is the file structure i have: PatrickLu-MSFT If you specify build retention policies , retention policies will delete the items below:

I have some embedded C software stored under TFS and also have a corresponding TFS build definition that successfully checks out the code and builds it using the relevant compilers. So just to be clear, although this is TFS, I'm not building a .NET application. Now that I have the build working, I'm trying to provide overall software versioning support which should be linked to the build process. My current aim is as follows: The source code that is being built has a header file that has #defines for three variables, Major Version, Minor Version and Build Number. This header file is then used

We have just upgraded from TFS 2010 to TFS 2015 and I'm recreating a XAML-Build-Definition in the "vNext" build/workflow-format. In the old Build it was possible to output all files (the DLLs) flat in one single directory, without their original directory structure. Is this still possible with the new TFS 2015 Build framework? I have the following Publish Build Artifact -Settings: Artifact Type: File Share Path: \\server\tfslib\$(Build.DefinitionName)\$(Build.DefinitionName)_$(Build.BuildNumber) The problem is that the original solution directory structure is preserved in the output directory

We have an old server machine with TFS 2012 installed on it. It has the 'DefaultCollection' of project collection. We want to copy (not move, i.e. leaving the collection in place) the 'DefaultCollection' collection to another machine which has TFS 2015 installed. How can we do that please? Thanks, ashilon It depends a bit on how complicated your TFS installation is, but here are the steps for a simpler one server setup without Sharepoint: Detatch the collection from your current TFS 2012 using the Team Foundation Server Administration Console. This will copy the configuration into the