.NET Framework
- MSB3757: Multiple Code xml elements have been found, this is not allowed. To fix this issue remove any additional Code xml ...
- MSB3773: The SDK "{0}" cannot be referenced alongside SDK(s) {1}, as they all belong to the same SDK product Family "{2}". ...
- MSB3776: The SDK Reference "{0}" is incorrectly formatted. It must be in the following format " , Version= . For example: ...
- MSB3776: The SDK Reference "{0}" is incorrectly formatted. It must be in the following format " , Version= . For example: ...
- MSB3777: "FrameworkIdentity" attributes were found in the SDK manifest file "{0}", however none of the attributes matched ...
- MSB3778: "APPX" attributes were found in the SDK manifest file "{0}" however none of the attributes matched the targeted ...
- MSB3779: The processor architecture of the project being built "{0}" is not supported by the referenced SDK "{1}". Please ...
- MSB3780: The SDK "{0}" cannot be referenced alongside SDK(s) {1}, because only one version of the SDK can be referenced from ...
- MSB3781: The SDK "{0}" depends on the following SDK(s) {1}, which have not been added to the project or were not found. Please ...
- MSB3782: The "{0}" SDK does not support targeting a neutral architecture with "Prefer 32-Bit" enabled for the project. Please ...
- MSB3785: No SDKs were found. SDKReference items will not be resolved. If your application requires these references there ...
- MSB3797: The targeted configuration for the resolved sdk reference "{0}" was empty. Cannot find reference or redist files ...
- MSB3798: The targeted architecture for the resolved sdk reference "{0}" was empty. Cannot find reference or redist files ...
- MSB3811: The assembly "{0}" says it is a satellite assembly, but it contains code. Main assemblies shouldn't specify the ...
- MSB3812: This assembly claims to be a satellite assembly, but doesn't contain any properly named .resources files as manifest ...
- MSB3813: Invalid or unrecognized UltimateResourceFallbackLocation value in the NeutralResourcesLanguageAttribute for assembly ...
- MSB3813: Invalid or unrecognized UltimateResourceFallbackLocation value in the NeutralResourcesLanguageAttribute for assembly ...
- MSB3814: Main assembly "{1}" was built improperly. The manifest resource "{0}" ends in .en-US.resources, when it should end ...
- MSB3815: Satellite assembly "{2}" was built improperly. The manifest resource "{0}" will not be found by the ResourceManager. ...
- MSB3817: The assembly "{0}" does not have a NeutralResourcesLanguageAttribute on it. To be used in an app package, portable ...
- MSB3818: The GenerateResource task doesn't currently support simultaneously running as an external tool and extracting ResW ...
- MSB3819: Cannot find assembly "{0}", which may contain managed resources that need to be included in this app package. Please ...
- MSB3820: The path needed to store build-related temporary files is too long. Try your project in a shorter directory, or ...
- MSB4003: "{0}" is a reserved attribute of the element, and must be spelled with the correct casing. This attribute cannot ...
- MSB4010: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be available. ...
- MSB4011: "{0}" cannot be imported again. It was already imported at "{1}". This is most likely a build authoring error. This ...
- MSB4011: There is a circular reference involving the import of file "{0}". This file may have been imported more than once, ...
- MSB4012: The expression "{0}" cannot be used in this context. Item lists cannot be concatenated with other strings where ...
- MSB4019: The imported project "{0}" was not found. Confirm that the path in the declaration is correct, and that the file ...
- MSB4029: The "{0}" task has an invalid output specification. The "TaskParameter" attribute is required, and either the "ItemName" ...
- MSB4031: The "MSBuildVersion" attribute is deprecated. If the project is authored in the MSBuild 2003 format, please remove ...
- MSB4036: The "{0}" task was not found. Check the following: 1.) The name of the task in the project file is the same as the ...
- MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild ...
- MSB4043: The item meta-data reference "{0}" is invalid because it is qualified with an item name. Item meta-data referenced ...
- MSB4043: The item metadata reference "{0}" is invalid because it is qualified with an item name. Item metadata referenced ...
- MSB4051: Project {0} is referencing a project with GUID {1}, but a project with this GUID was not found in the .SLN file. ...
- MSB4054: The solution file must be opened in the Visual Studio IDE and converted to the latest version before it can be built ...
- MSB4056: The MSBuild engine must be called on a single-threaded-apartment. Current threading model is "{0}". Proceeding, ...
- MSB4058: The "{0}" target is missing its output specification. If a target declares inputs, it must also declare outputs. ...
- MSB4060: The "{0}" task has been declared or used incorrectly, or failed during construction. Check the spelling of the task ...
- MSB4062: The "{0}" task could not be loaded from the assembly {1}. {2} Confirm that the declaration is correct, and that ...
- MSB4062: The "{0}" task could not be loaded from the assembly {1}. {2} Confirm that the declaration is correct, that the ...
- MSB4064: The "{0}" parameter is not supported by the "{1}" task. Verify the parameter exists on the task, and it is a settable ...
- MSB4075: The project file "{0}" must be opened in the Visual Studio IDE and converted to the latest version before it can ...
- MSB4075: The project file must be opened in the Visual Studio IDE and converted to the latest version before it can be built ...
- MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. ...
- MSB4080: The value "{0}" of the "PropertyName" attribute in element contains a "$" character. If you intended to use a property ...
- MSB4081: The value "{0}" of the "ItemName" attribute in element contains an "@" character. If you intended to use an item ...
- MSB4094: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. Multiple items cannot be passed into a parameter ...
- MSB4095: The item metadata %({0}) is being referenced without an item name. Specify the item name by using %(itemname.{0}). ...
- MSB4096: The item "{0}" in item list "{1}" does not define a value for metadata "{2}". In order to use this metadata, either ...
- 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 ...
- 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()), ...