title: Does MS-Build Definition inherit property from projects?
body: <p>I've some <strong>sql projects</strong> with the property "Treat Warnings as Errors" enabled for every build configuration set (Debug, Release, etc.).</p>
  
  <p>Building locally this property works without problem (so every warning is managed as error). </p>
  
  <p>Using instead the MSBuild-Definition tool the same warnings are not managed as errors but just as warnings.</p>
  
  <p>I cannot add the MS Build Argument /p:TreatWarningsAsErrors=True to the Build level because in the same build definition there are other projects (not only sql projects) where the property "Treat Warnings as Errors" isn't enabled, so every build is going to fail.</p>
  
  <p>What I want is to have the possibility to set my Build definition so that they can manage some project as "TreatWarningsAsErrors" and some other not.</p>
  
  <p>I read in some documents that the build definition should inherit its property from the project built.</p>
  
  <p>Is this wrong? Should I just add some configuration to my Build Process Template?</p>
  
  <p>I am using the TfvcTemplate.12.xaml </p>
  
  <p>If you need some other details just ask me.</p>
  
  <p>Hope you can help me</p>
  
  <p>Thanks</p>