code_junkie

Msbuild task - Build fails because one solution being built in release instead of debug

Nov 13th, 2011
199
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.54 KB | None | 0 0
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <Project DefaultTargets="DesktopBuild" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  3. <!-- TO EDIT BUILD TYPE DEFINITION
  4.  
  5. To edit the build type, you will need to edit this file which was generated
  6. by the Create New Build Type wizard. This file is under source control and
  7. needs to be checked out before making any changes.
  8.  
  9. The file is available at -
  10. $/{TeamProjectName}/TeamBuildTypes/{BuildTypeName}
  11. where you will need to replace TeamProjectName and BuildTypeName with your
  12. Team Project and Build Type name that you created
  13.  
  14. Checkout the file
  15. 1. Open Source Control Explorer by selecting View -> Other Windows -> Source Control Explorer
  16. 2. Ensure that your current workspace has a mapping for the $/{TeamProjectName}/TeamBuildTypes folder and
  17. that you have done a "Get Latest Version" on that folder
  18. 3. Browse through the folders to {TeamProjectName}->TeamBuildTypes->{BuildTypeName} folder
  19. 4. From the list of files available in this folder, right click on TfsBuild.Proj. Select 'Check Out For Edit...'
  20.  
  21.  
  22. Make the required changes to the file and save
  23.  
  24. Checkin the file
  25. 1. Right click on the TfsBuild.Proj file selected in Step 3 above and select 'Checkin Pending Changes'
  26. 2. Use the pending checkin dialog to save your changes to the source control
  27.  
  28. Once the file is checked in with the modifications, all future builds using
  29. this build type will use the modified settings
  30. -->
  31. <!-- Do not edit this -->
  32. <Import Project="$(MSBuildExtensionsPath)MicrosoftVisualStudiov8.0TeamBuildMicrosoft.TeamFoundation.Build.targets" />
  33. <ProjectExtensions>
  34. <!-- DESCRIPTION
  35. The description is associated with a build type. Edit the value for making changes.
  36. -->
  37. <Description>
  38. </Description>
  39. <!-- BUILD MACHINE
  40. Name of the machine which will be used to build the solutions selected.
  41. -->
  42. <BuildMachine>xxxx-test</BuildMachine>
  43. </ProjectExtensions>
  44. <PropertyGroup>
  45. <!-- TEAM PROJECT
  46. The team project which will be built using this build type.
  47. -->
  48. <TeamProject>CFAST</TeamProject>
  49. <!-- BUILD DIRECTORY
  50. The directory on the build machine that will be used to build the
  51. selected solutions. The directory must be a local path on the build
  52. machine (e.g. c:build).
  53. -->
  54. <BuildDirectoryPath>C:Buildbrtcn</BuildDirectoryPath>
  55. <SolutionRoot Condition=" '$(IsDesktopBuild)'!='true' ">$(BuildDirectoryPath)w</SolutionRoot>
  56. <!-- DROP LOCATION
  57. The location to drop (copy) the built binaries and the log files after
  58. the build is complete. This location has to be a valid UNC path of the
  59. form \ServerShare. The build machine service account and application
  60. tier account need to have read write permission on this share.
  61. -->
  62. <DropLocation>\my-filesxx-filesBuild Dropxx</DropLocation>
  63. <!-- TESTING
  64. Set this flag to enable/disable running tests as a post build step.
  65. -->
  66. <RunTest>false</RunTest>
  67. <!-- WorkItemFieldValues
  68. Add/edit key value pairs to set values for fields in the work item created
  69. during the build process. Please make sure the field names are valid
  70. for the work item type being used.
  71. -->
  72. <WorkItemFieldValues>Symptom=build break;Steps To Reproduce=Start the build using Team Build</WorkItemFieldValues>
  73. <!-- CODE ANALYSIS
  74. To change CodeAnalysis behavior edit this value. Valid values for this
  75. can be Default,Always or Never.
  76.  
  77. Default - To perform code analysis as per the individual project settings
  78. Always - To always perform code analysis irrespective of project settings
  79. Never - To never perform code analysis irrespective of project settings
  80. -->
  81. <RunCodeAnalysis>Never</RunCodeAnalysis>
  82. <!-- UPDATE ASSOCIATED WORK ITEMS
  83. Set this flag to enable/disable updating associated workitems on a successful build
  84. -->
  85. <UpdateAssociatedWorkItems>true</UpdateAssociatedWorkItems>
  86. <!-- Title for the work item created on build failure -->
  87. <WorkItemTitle>Build failure in build:</WorkItemTitle>
  88. <!-- Description for the work item created on build failure -->
  89. <DescriptionText>This work item was created by Team Build on a build failure.</DescriptionText>
  90. <!-- Text pointing to log file location on build failure -->
  91. <BuildlogText>The build log file is at:</BuildlogText>
  92. <!-- Text pointing to error/warnings file location on build failure -->
  93. <ErrorWarningLogText>The errors/warnings log file is at:</ErrorWarningLogText>
  94. </PropertyGroup>
  95. <ItemGroup>
  96. <!-- SOLUTIONS
  97. The path of the solutions to build. To add/delete solutions, edit this
  98. value. For example, to add a solution MySolution.sln, add following line -
  99. <SolutionToBuild Include="C:Project FilespathMySolution.sln" />
  100.  
  101. To change the order in which the solutions are build, modify the order in
  102. which the solutions appear below.
  103. -->
  104. <SolutionToBuild Include="....xx1xxxSolutionxxx Solution.sln" />
  105. <SolutionToBuild Include="....xx2Build Solutionsxx xx xx BuildData Port Common Build.sln" />
  106. <SolutionToBuild Include="....xx3Build Solutionsxxx Buildxxx Build.sln" />
  107.  
  108. </ItemGroup>
  109. <ItemGroup>
  110. <!-- CONFIGURATIONS
  111. The list of configurations to build. To add/delete configurations, edit
  112. this value. For example, to add a new configuration, add following lines -
  113. <ConfigurationToBuild Include="Debug|x86">
  114. <FlavorToBuild>Debug</FlavorToBuild>
  115. <PlatformToBuild>x86</PlatformToBuild>
  116. </ConfigurationToBuild>
  117.  
  118. The Include attribute value should be unique for each ConfigurationToBuild node.
  119. -->
  120. <ConfigurationToBuild Include="Debug|Any CPU">
  121. <FlavorToBuild>Debug</FlavorToBuild>
  122. <PlatformToBuild>Any CPU</PlatformToBuild>
  123. </ConfigurationToBuild>
  124. </ItemGroup>
  125. <ItemGroup>
  126. <!-- TEST ARGUMENTS
  127. If the RunTest is set to true then the following test arguments will be
  128. used to run tests.
  129.  
  130. To add/delete new testlist or to choose a metadata file (.vsmdi) file, edit this value.
  131. For e.g. to run BVT1 and BVT2 type tests mentioned in the Helloworld.vsmdi file, add the following -
  132.  
  133. <MetaDataFile Include="C:Project FilesHelloWorldHelloWorld.vsmdi">
  134. <TestList>BVT1;BVT2</TestList>
  135. </MetaDataFile>
  136.  
  137. Where BVT1 and BVT2 are valid test types defined in the HelloWorld.vsmdi file.
  138. MetaDataFile - Full path to test metadata file.
  139. TestList - The test list in the selected metadata file to run.
  140.  
  141. Please note that you need to specify the vsmdi file relative to $(SolutionRoot)
  142. -->
  143. <MetaDataFile Include=" ">
  144. <TestList> </TestList>
  145. </MetaDataFile>
  146. </ItemGroup>
  147. <ItemGroup>
  148. <!-- ADDITIONAL REFERENCE PATH
  149. The list of additional reference paths to use while resolving references.
  150. For example,
  151. <AdditionalReferencePath Include="C:MyFolder" />
  152. <AdditionalReferencePath Include="C:MyFolder2" />
  153. -->
  154. <AdditionalReferencePath Include="....xxxxReference Files" />
  155. <AdditionalReferencePath Include="....xxxxBuild SupportSomeCoolLibrary" />
  156. <AdditionalReferencePath Include="....xxxx1.1Reference Files " />
  157. </ItemGroup>
  158. </Project>
  159.  
  160. <ConfigurationToBuild Include="Debug|Any CPU">
  161. <FlavorToBuild>Debug</FlavorToBuild>
  162. <PlatformToBuild>Any CPU</PlatformToBuild>
  163. </ConfigurationToBuild>
  164.  
  165. MSBuild Projects="$(RootPath)SourceWebsite.csproj"
  166. Targets="ResolveReferences;_CopyWebApplication" Properties="Configuration=$(BuildConfiguration);WebProjectOutputDir=$(DeploymentFolder);OutDir=$(DeploymentFolder)bin" />
Add Comment
Please, Sign In to add comment