Build customization "{0}" uses file extension "{1}". This file extension is currently mapped to {2} "{3}" in one or more project configurations.
If the build customization file is associated with this project, files with this extension (that do not have file-level properties set) may use this build customization instead. Do you still want to associate build customization file "{4}" with this project?
Bug Effectiveness: Supports the team in determining how effective they are in defining bugs that are actionable and help ...
Build customization "{0}" conflicts with {1} "{0}" in project "{2}". Please select a different name for this build customization. ...
Build customization "{0}" conflicts with {1} "{0}". If the build customization file is associated with this project, this ...
Build customization "{0}" uses file extension "{1}". This file extension is currently mapped to {2} "{3}" in one or more ...
Build customization "{0}" uses file extension "{1}". This file extension is currently mapped to {2} "{3}" in one or more ...
Build Customizations Search Path : A semi-colon delimited list of directories to search for Visual C++ build customization ...
Build Data: Team Project : {0} Build Number : {1} Build Uri : {2} Build Definition : {3} Build Controller : {4} Source Get ...
Build definition did not specify a clean snapshot. It is a best practice to use clean snapshot when running the lab workflow. ...
Build definition did not specify a post deployment snapshot. It is a best practice to take post deployment snapshot when ...