Visual Studio 2013
- MSB4098: MSBuild is invoking VCBuild to build this project. Project-to-project references between VC++ projects (.VCPROJ) ...
- MSB4107: Expected an item list at position {1} in condition "{0}". Did you forget the opening parenthesis after the '@'? ...
- MSB4108: Expected an item list at position {1} in condition "{0}". Did you forget to close a quote inside the item list expression? ...
- MSB4110: Expected a property at position {1} in condition "{0}". Did you forget the opening parenthesis after the '$'? To ...
- MSB4112: The targets in this project have been disabled by the host and therefore cannot be built at this time. This may ...
- MSB4115: The "{0}" function only accepts a scalar value, but its argument "{1}" evaluates to "{2}" which is not a scalar ...
- MSB4116: The condition "{1}" on the "{0}" target has a reference to item metadata. References to item metadata are not allowed ...
- MSB4121: The project configuration for project "{0}" was not specified in the solution file for the solution configuration ...
- MSB4126: The specified solution configuration "{0}" is invalid. Please specify a valid solution configuration using the Configuration ...
- MSB4127: The "{0}" task could not be instantiated from the assembly "{1}". Please verify the task assembly has been built ...
- MSB4130: The condition "{0}" may have been evaluated incorrectly in an earlier version of MSBuild. Please verify that the ...
- MSB4131: The "{0}" parameter is not supported by the "{1}" task. Verify the parameter exists on the task, and it is a gettable ...
- MSB4137: Invalid value specified in the configuration file at "{0}". Property name or tools version name is an empty string. ...
- MSB4141: MSBuildToolsPath is not specified for the ToolsVersion "{0}" defined at "{1}", or the value specified evaluates ...
- MSB4142: MSBuildToolsPath is not the same as MSBuildBinPath for the ToolsVersion "{0}" defined at "{1}". If both are present ...
- MSB4151: An error occurred while building project "{0}", target "{1}". Please see innerException for detailed information. ...
- MSB4161: Project "{0}" was loaded and unloaded during the current build. Reloading a project during the build can result ...
- MSB4164: The value "{0}" of metadata "{1}" contains an item list expression. Item list expressions are not allowed on default ...
- MSB4166: Child node "{0}" exited prematurely. Shutting down. Diagnostic information may be found in files in the temporary ...
- MSB4168: The item "{0}" of type "{1}" does not define a value for the metadata in the expression "{2}". This expression is ...
- MSB4176: The "{0}" task factory could not be instantiated from the assembly "{1}". Please verify the task assembly has been ...
- MSB4180: The "{0}" logger could not be instantiated from the assembly "{1}". Please verify the logger assembly has been built ...
- MSB4186: Invalid static method invocation syntax: "{0}". Static method invocation should be of the form: $([FullTypeName]::Method()), ...
- MSB4186: Invalid static method invocation syntax: "{0}". {1} Static method invocation should be of the form: $([FullTypeName]::Method()), ...
- MSB4192: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project ...
- MSB4193: MSBuild.exe could not be launched as a child node as it could not be found at the location "{0}". If necessary, ...
- MSB4196: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be overridden. ...
- MSB4210: "{0}" is attempting to import itself, directly or indirectly. This is most likely a build authoring error. The import ...
- MSB4212: Invalid static method invocation syntax: "{0}". The type "{1}" is either not available for execution in an MSBuild ...
- MSB4214: The "{0}" task has been defined, but cannot be used due to the fact that the identity defined in the UsingTask declaration ...
- MSB4215: The "{0}" task could not be loaded. "{1}" is an invalid value for the task host parameter "{2}". Valid values are: ...
- MSB4216: Could not run the "{0}" task because MSBuild could not create or connect to a task host with runtime "{1}" and architecture ...
- MSB4217: Task host node exited prematurely. Diagnostic information may be found in files in the temporary files directory ...
- MSB4218: Failed to successfully launch or connect to a child MSBuild.exe process. Verify that the MSBuild.exe "{0}" launches ...
- MSB4219: The TaskFactory "{0}" does not implement ITaskFactory2. The attributes "{1}" and/or "{2}" on the UsingTask declaration ...
- MSB4221: Could not run the "{0}" task because MSBuild could not create or connect to a task host with runtime "{1}" and architecture ...
- MSB4222: ToolsVersion "{0}", defined at "{1}", contains sub-toolset "{2}" which sets MSBuildBinPath or MSBuildToolsPath. ...
- MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. ...
- MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform ...
- MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested ...
- MSB6002: The command-line for the "{0}" task is too long. Command-lines longer than 32000 characters are likely to fail. ...
- MSB6007: The "{0}" value passed to the Environment property is not in the format "name=value", where the value part may be ...
- MSB8002: Specified platform toolset ({0}) is not compatible with the targeted .NET Framework version ({1}). Please set TargetFrameworkVersion ...
- MSB8003: Could not find {0} variable from the registry. TargetFrameworkVersion or PlatformToolset may be set to an invalid ...
- MSB8004: {0} Directory does not end with a trailing slash. This build instance will add the slash as it is required to allow ...
- MSB8006: The Platform for project '{0}' is invalid. Platform='{1}'. This error may also appear if some other project is trying ...
- MSB8007: The Platform for project '{0}' is invalid. Platform='{1}'. You may be seeing this message because you are trying ...
- MSB8008: Specified platform toolset ({0}) is not installed or invalid. Please make sure that a supported PlatformToolset ...
- MSB8009: .NET Framework 2.0/3.0/3.5 target the v90 platform toolset. Please make sure that Visual Studio 2008 is installed ...
- MSB8010: Specified platform toolset (v90) requires Visual Studio 2008. Please make sure that Visual Studio 2008 is installed ...
- MSB8011: Failed to register output. Please try enabling Per-user Redirection or register the component from a command prompt ...
- MSB8012: %s ('%s') does not match the %s's OutputFile property value '%s' ('%s') in project configuration '%s'. This may ...
- MSB8012: {0}({1}) does not match the {2}'s OutputFile property value ({3}). This may cause your project to build incorrectly. ...
- MSB8017: A circular dependency has been detected while executing custom build commands for item "{0}". This may cause incremental ...
- MSB8019: This build is consuming a component "{0}" that is not packaged because the component is not coming from a Windows ...
- MSB8020: The build tools for {0} (Platform Toolset = '{1}') cannot be found. To build using the {1} build tools, please install ...
- MSB8027: Two or more files with the name of {0} will produce outputs to the same location. This can lead to an incorrect ...
- MSB8028: The intermediate directory ({1}) contains files shared from another project ({0}). This can lead to incorrect clean ...
- MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could lead to issues ...
- MSB8030: The linker switch "Minimum Required Version" requires "SubSystem" to be set. Without "SubSystem", the "Minimum Required ...
- MSB8031: Building an MFC project for a non-Unicode character set is deprecated. You must change the project property to Unicode ...
- MSB8032: The Platform or PlatformToolset is not available from a 64bit environment. Consider building from 32bit environment ...
- MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or ...
- MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project ...
- MSBUILD : error MSB1013: The response file was specified twice. A response file can be specified only once. Any files named ...
- MSBUILD : error MSB1015: MSBuild does not run on this version of the operating system. It is only supported on Windows 2000, ...
- MSBUILD : error MSB1020: The logger was not found. Check the following: 1.) The logger name specified is the same as the ...
- MSBUILD : error MSB1027: The /noautoresponse switch cannot be specified in the MSBuild.rsp auto-response file, nor in any ...
- MSBUILD : error MSB1032: Maximum CPU count is not valid. Value must be an integer greater than zero and no more than 1024. ...
- MSBUILD : error MSB1036: There is an invalid extension in the /ignoreprojectextensions list. Extensions must start with a ...
- MSBUILD : error MSB1037: Specify one or more parameters for the console logger if using the /consoleLoggerParameters switch ...
- MSBUILD : error MSB1048: Solution files cannot be debugged directly. Run MSBuild first with an environment variable MSBUILDEMITSOLUTION=1 ...
- MSBUILD : error MSB4192: The project file "{0}" is in the ".vcproj" or ".dsp" file format, which MSBuild cannot build directly. ...
- MSBuild could not locate the Code Analysis tool at '{0}'. If MSBuild is being run from within the "Visual Studio Command ...
- MSBuild error {0} has ended this build. You can find more specific information about the cause of this error in above messages. ...