CODEWITHSUNDEEP
asp.netmsbuildtfsbuildwebdeploy
Captain Kirk
Captain Kirk

Reputation: 63

TFS Build Definition use msbuild arguments generate files in staging directory

In the build definition, I have those parameters in the msbuild arguments: /p:DeployOnBuild=true /p:WebPublishMethod=FileSystem /p:PackageLocation=$(build.stagingDirectory)\DeployPackages\ /p:PackageAsSingleFile=false /p:SkipInvalidConfigurations=true /p:AutoParameterizationWebConfigConnectionStrings=False /p:GenerateProjectSpecificOutputFolder=true

All the files required are place in the DeployPackages folder, but list of folder and subfolder to get to the code is to big. Is there a way to reduce the number of folders? _work\5\a\DeployPackages\Archive\Content\d_C\tfsbuild_work\5\s\Main\AdService\obj\DEVE\Package\PackageTmp\

and it's the PackageTmp folder that contains the file I need to copy to our server.

thanks

Upvotes: 0

Views: 1623

Answers (2)

PatrickLu-MSFT
PatrickLu-MSFT

Reputation: 51183

Update

To reduce the folder path and structure you could use other argument instead of $(build.stagingDirectory) in package location. Such as 

/p:PackageLocation="$(BuildConfiguration)"\DeployPackages\XX.zip

or

/p:PackageLocation="$(build.artifactstagingdirectory)\DeployPackages\XX.zip

Besides if you got any long path issue, the most effective and easy way still is spending some time tweaking your file/folder structure.

For example: instead of \xx\Build\Drop\ProjectName, just use \xx\Build\Drop (or \xx\Builds) since the project name is also in the build name.

Upvotes: 0

Eddie Chen - MSFT
Eddie Chen - MSFT

Reputation: 29976

You can use this arguments:

/p:outdir="$(build.artifactstagingdirectory)\DeployPackages"

Upvotes: 0

Related Questions