TFS 2015 Visual Studio Build - Package .zip not being created

tfs build copy files to drop folder
tfs add folder to source control
add files to tfs without visual studio
copy and publish build artifacts
how to create a project in tfs 2015
$(build.artifactstagingdirectory) location
visual studio tfs project
azure devops copy files to remote server

I'm trying to build my solution and package up the web app into a web deploy (.zip) package to be deployed.

I've added the Visual Studio Build step with the following MSBuild Arguments:

/p:DeployOnBuild=True /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:PackageLocation="$(build.artifactstagingdirectory)\"

And I've set up the Copy and Publish Build Artifacts step to copy all .zip files to the drop folder.

The build completes successfully but nothing is copied to the drop folder because there are no .zip packages that get created.

So when I look on the TFS server, the only thing in the 'a' folder is an empty 'drop' folder. And in the 's' folder is the solution directory with a PrecompiledWeb folder in it. Not sure what that is but it doesn't look like the deployment package (and it's not a .zip).

Any ideas?

I have tried the same on VS2015 MVC web application using VSTS and TFS 2015.2.1 both. I had to do a slight change to the Build arguments in Visual Studio build. That is removing the trailing "\" in /p:PackageLocation="$(build.artifactstagingdirectory)\".

Here is the argument I passed to Visual studio build step

/p:DeployOnBuild=True /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:PackageLocation="$(build.artifactstagingdirectory)"

Then I used Copy and Published Build Artifacts (Deprecated in VSTS you should use Copy task and Publish task instead of this task) as shown below

This gives me output as below.

Adding Files to Source Control—Team Foundation Server, How do I add a project to TFS Visual Studio 2019? I am trying to create a deployment package as a zip file in Visual Studio 2015. For some reason the option is not there on the Package/Publish Web tab under Web Deployment Package Settings.

First suggest you manually remote in the build agent and build the project through MSBuild command line with arguments to see if the project builds properly.

This will narrow down the issue is related to the environment on your build agent or your build definition.

You should directly use /p:PackageLocation=$(build.stagingDirectory

Besides since you have multiple assemblies that are referenced in the web app. Please also double check dependencies that are building in the correct order or referenced correctly.

Adding Content to Source Control, The build completes successfully but nothing is copied to the drop folder because there are no .zip packages that get created. So when I look on the TFS server,  Using TFS 2010 and I have a build project consisting of 2 solutions. One is a MVC solution with web pages the other is a solution containing multiple projects. These are various WFC services. I have added the criteria to publish each project in both solutions. If I build either of them from VS - I get the zip files created.

Make sure the ASP.NET development workload of Visual Studio is installed.

If DeployOnBuild is having no effect, you may need to install the ASP.NET Development "workload" with the VS setup tool.

There are specific .targets files that, if they don't exist, cause these parameters to be silently ignored. Installing this adds those .targets and the parameters become active, allowing the .zip to be created.

For me (VS 2017) the relevant target file (or one of them, anyway) that was missing but is needed is:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\Web\Microsoft.Web.Publishing.targets

If it is missing, you'll need to install as above, and if it is there, then you have a different problem. ;)

Predefined variables, To add a solution to source control in TFS, you'll need to complete these high-​level steps: Connect to a Team Project and Create a Folder Mapping In Visual Studio, on the Team menu, click Connect to Team Foundation Server. The packages folder is not part of the Contact Manager solution, but the  When I tried to publish the output as a package using VS2017, I got all the necessary files in "Publish" folder as well a zip file containing all those files in given location. However I want to have the same using command line.

Copy and Publish Build Artifacts task, If you're using Azure Pipelines, or Team Foundation Server (TFS) 2017 or newer, we recommend that you do NOT use this deprecated task. In the Package location box, enter the path to where you want the package to be created, including the .zip file name; for example, c:\temp\<projectname>.zip. As an alternative, you can click the ellipsis to open a Select Package Location dialog box.

Build and Deploy a Web Application with TFS 2017 using Web , Then I am using Deploy IIS App for extract the .zip Package in the a publish profile created as Web Deploy Package but after the build in the Project using the TFS (because when I publish from the Visual Studio is make the Build and Release in the TFS no using nothing manual from Visal Studio. Support for TFS 2015; 2.1.0 (18 Aug 2015) Support for Visual Studio 2015; Bug fix MSBAI-7; 2.0.0 (30 Apr 2015) Artifactory plugin as a Visual Studio Extension, and used as a "Project template" in the solution. Supporting Black Duck Code Center as part of the build process. 1.0.0 (30 Sep 2014) First release version.

Zip and unzip directory build task, A set of Build tasks Azure Pipelines that enables you to Zip and Unzip a When the 'Unzip to path' is empty, the files will be unziped into a sub  SharePoint package (.wsp) not created windows 6.3 visual studio 2017 René Hézser reported Mar 08, 2017 at 08:26 AM

  • Possible duplicate of TFS 2015 - Build solution, package project. Also building a solution it shouldn't be
  • Which kind of project are you building, ASP .Net Core? Please add related tfs build log.
  • Can you share the build logs? Did you build a Web Application project or WeSite Project?
  • Hi @J.Doe, Build with a WeSite Project through .sln file will not directly generate a .zip file, it will gengerate a publishproj file.