使用Release Management Client（Update 2）附带的发布模板，我们尝试使用TFS Build and Release Management Server 2013 Update 2进行自动部署。
在我们决定开始使用标记化的Web.Config（Web.config.token）来帮助我们管理部署之前，一切都很顺利。
看起来很简单，在Release Template Components中创建变量，并将匹配的__ VARIABLES__放在重复的Web.config.token中。
将Build Template设置为Process Build Tokens并点击go。
构建似乎没有实际处理令牌文件，我们留下了原始的Web.config。我有什么想法吗？
它说它正在处理令牌，但它实际上并没有这样做。 构建日志：
Overall Build Process
Overall build process
Update build number
Run on agent (reserved build agent {Redacted} Build - Agent 2)
Initialize environment
Get sources from Team Foundation Version Control
Associate the changesets that occurred since the last good build
Compile, Test and Publish
Run optional script before MSBuild
Run MSBuild
Built {Redacted}.sln for default targets.
Built ${Redacted}.csproj for default targets.
Built $/{Redacted}/.nuget/NuGet.targets for target(s) _DownloadNuGet.
Built $/{Redacted}.Database.sqlproj for default targets.
MSBuild Log File
Run optional script after MSBuild
Process the release
Get the Build Directory
If ProcessReleaseTokens is set
Initialize tokens
Prepare folder to search
Find all .token files
Process each .token file
Rename files
Assign
Remove read-only flag from x.y
Copy x.y.token to x.y
If ReleaseBuild is set
Try to release the build
Get the build details
Initialize release build variables
Get the Release Management install directory
Verify the Release Management install directory
Get the Release Management install directory (x64)
Get the Team Project Collection instance
If ConfigurationsToRelease is not set
Copy binaries to drop
Process each ConfigurationsToRelease
Release the build
Run the Release Management build process for the current configuration
Microsoft.TeamFoundation.Release.Build starting process...
Processing using the following parameters:
TeamFoundationServerUrl: {Redacted}
TeamProjectName: {Redacted}
TeamProjectWithCollection: {Redacted}
BuildDefinitionName: {Redacted}
BuildNumber: {Redacted}
TargetStage:
Creating the release and waiting for deployment result...
Release was created and deployment was successful.
If a Release Build error cccurs
Skipped due to successful completion
Run optional script before Test Runner
Run VS Test Runner
Run optional script after Test Runner
Get Impacted Tests
Publish Symbols
Perform Final Actions On Agent
Copy binaries to drop
Reset the Environment