.NET Framework

  1. MSB4186: Invalid static method invocation syntax: "{0}". {1} Static method invocation should be of the form: $([FullTypeName]::Method()), ...
  2. MSB4192: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project ...
  3. MSB4193: MSBuild.exe could not be launched as a child node as it could not be found at the location "{0}". If necessary, ...
  4. MSB4196: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be overridden. ...
  5. MSB4210: "{0}" is attempting to import itself, directly or indirectly. This is most likely a build authoring error. The import ...
  6. MSB4212: Invalid static method invocation syntax: "{0}". The type "{1}" is either not available for execution in an MSBuild ...
  7. MSB4214: The "{0}" task has been defined, but cannot be used due to the fact that the identity defined in the UsingTask declaration ...
  8. MSB4215: The "{0}" task could not be loaded. "{1}" is an invalid value for the task host parameter "{2}". Valid values are: ...
  9. MSB4216: Could not run the "{0}" task because MSBuild could not create or connect to a task host with runtime "{1}" and architecture ...
  10. MSB4217: Task host node exited prematurely. Diagnostic information may be found in files in the temporary files directory ...
  11. MSB4218: Failed to successfully launch or connect to a child MSBuild.exe process. Verify that the MSBuild.exe "{0}" launches ...
  12. MSB4219: The TaskFactory "{0}" does not implement ITaskFactory2. The attributes "{1}" and/or "{2}" on the UsingTask declaration ...
  13. MSB4221: Could not run the "{0}" task because MSBuild could not create or connect to a task host with runtime "{1}" and architecture ...
  14. MSB4222: ToolsVersion "{0}", defined at "{1}", contains sub-toolset "{2}" which sets MSBuildBinPath or MSBuildToolsPath. ...
  15. MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. ...
  16. MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform ...
  17. MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested ...
  18. MSB6002: The command-line for the "{0}" task is too long. Command-lines longer than 32000 characters are likely to fail. ...
  19. MSB6007: The "{0}" value passed to the Environment property is not in the format "name=value", where the value part may be ...
  20. MSB8002: Specified platform toolset ({0}) is not compatible with the targeted .NET Framework version ({1}). Please set TargetFrameworkVersion ...
  21. MSB8003: Could not find {0} variable from the registry. TargetFrameworkVersion or PlatformToolset may be set to an invalid ...
  22. MSB8004: {0} Directory does not end with a trailing slash. This build instance will add the slash as it is required to allow ...
  23. MSB8006: The Platform for project '{0}' is invalid. Platform='{1}'. This error may also appear if some other project is trying ...
  24. MSB8007: The Platform for project '{0}' is invalid. Platform='{1}'. You may be seeing this message because you are trying ...
  25. MSB8008: Specified platform toolset ({0}) is not installed or invalid. Please make sure that a supported PlatformToolset ...
  26. MSB8009: .NET Framework 2.0/3.0/3.5 target the v90 platform toolset. Please make sure that Visual Studio 2008 is installed ...
  27. MSB8010: Specified platform toolset (v90) requires Visual Studio 2008. Please make sure that Visual Studio 2008 is installed ...
  28. MSB8011: Failed to register output. Please try enabling Per-user Redirection or register the component from a command prompt ...
  29. MSB8012: {0}({1}) does not match the {2}'s OutputFile property value ({3}). This may cause your project to build incorrectly. ...
  30. MSB8017: A circular dependency has been detected while executing custom build commands for item "{0}". This may cause incremental ...
  31. MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or ...
  32. MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project ...
  33. MSBUILD : error MSB1013: The response file was specified twice. A response file can be specified only once. Any files named ...
  34. MSBUILD : error MSB1015: MSBuild does not run on this version of the operating system. It is only supported on Windows 2000, ...
  35. MSBUILD : error MSB1020: The logger was not found. Check the following: 1.) The logger name specified is the same as the ...
  36. MSBUILD : error MSB1027: The /noautoresponse switch cannot be specified in the MSBuild.rsp auto-response file, nor in any ...
  37. MSBUILD : error MSB1032: Maximum CPU count is not valid. Value must be an integer greater than zero and no more than 1024. ...
  38. MSBUILD : error MSB1036: There is an invalid extension in the /ignoreprojectextensions list. Extensions must start with a ...
  39. MSBUILD : error MSB1037: Specify one or more parameters for the console logger if using the /consoleLoggerParameters switch ...
  40. MSBUILD : error MSB1048: Solution files cannot be debugged directly. Run MSBuild first with an environment variable MSBUILDEMITSOLUTION=1 ...
  41. MSBUILD : error MSB4192: The project file "{0}" is in the ".vcproj" or ".dsp" file format, which MSBuild cannot build directly. ...
  42. MSBuild is creating a temporary VC project file "{0}" for the project "{1}", with project references replaced by assembly ...
  43. MTOM message not valid. One or more MIME parts in the message does not contain correctly formatted content and/or boundary ...
  44. Multiple accessors are not supported with rpc\literal SOAP, you may use the following attributes: XmlArray, XmlArrayItem, ...
  45. Multiple definition of element '{0}' causes the content model to become ambiguous. A content model must be formed such that ...
  46. Multiple initializations of '|1'. Fields and properties can be initialized only once in an object initializer expression. ...
  47. Multiple items are dragged and dropped. DragDropHelper.SetDragDropMovedViewElements should have been called to indicate the ...
  48. Multiple link-local only interfaces detected. Please specifiy the interface you require by using the ListenIpAddress attribute ...
  49. Multiple overloads of '{0}.{1}' have the same overload name, '{2}', specified by using Windows.Foundation.Metadata.OverloadAttribute. ...
  50. Multiple schemas with targetNamespace='{0}' returned by {1}.{2}(). Please use only the main (parent) schema, and add the ...
  51. Multiple supporting token authenticators with the token parameter type equal to '{0}' cannot be specified. If more than one ...
  52. Multiple types with the name '{0}' exist in the EdmItemCollection in different namespaces. Convention based mapping requires ...
  53. Multiple validator attributes are not currently supported. The property '{0}' has more than one validator attribute associated ...
  54. Multiple versions of the same assembly were loaded into one context of an application domain. This might lead to runtime ...
  55. Multiplicity conflicts with the referential constraint in Role '{0}' in relationship '{1}'. Because all of the properties ...
  56. Multiplicity conflicts with the referential constraint in Role '{0}' in relationship '{1}'. Because one/all of the properties ...
  57. Multiplicity is not valid in Role '{0}' in relationship '{1}'. Because all the properties in the Dependent Role are nullable, ...
  58. Multiplicity is not valid in Role '{0}' in relationship '{1}'. Because the Dependent Role properties are not the key properties, ...
  59. Multiplicity is not valid in Role '{0}' in relationship '{1}'. Because the Dependent Role refers to the key properties, the ...
  60. Multiplicity is not valid in role '{0}' in relationship '{1}'. Valid values for multiplicity for Principal Role are '0.1' ...
  61. must be a non-abstract type with a public parameterless constructor in order to use it as parameter '{1}' in the generic ...
  62. Must complete Convert() operation or call Decoder.Reset() before calling GetChars() or GetCharCount(). Decoder '{0}' fallback ...
  63. Must complete Convert() operation or call Encoder.Reset() before calling GetBytes() or GetByteCount(). Encoder '{0}' fallback ...
  64. must contain either a single ServiceKnownTypeAttribute that refers to a method or a set of ServiceKnownTypeAttributes, each ...
  65. must have either a TimeSpan for its Duration or a TimeSpan for the KeyTime of its last KeyFrame. This '{0}' has a Duration ...
  66. Must have one or more fields to databind. (Application may have autogenerated fields from an empty DataSource. To clear items, ...
  67. Must specify binding flags describing the invoke operation required (BindingFlags.InvokeMethod CreateInstance GetField SetField ...
  68. MustInherit' cannot be specified for partial type '|1' because it cannot be combined with 'NotInheritable' specified for ...
  69. MustOverride' cannot be specified on '|1' because it is in a partial type that is declared 'NotInheritable' in another partial ...
  70. Name of type parameter '|1' does not match '|2', the corresponding type parameter defined on the partial method declaration ...
  71. Name/value pairs in markup extensions must have the format 'Name = Value' with each pair separated by a comma. '{0}' does ...
  72. NameScopeProperty found within the content of a FrameworkTemplate, on a '{0}' object. Name scopes within templates are not ...
  73. Namespace or type specified in the Imports '|1' doesn't contain any public member or cannot be found. Make sure the namespace ...
  74. Namespace or type specified in the project-level Imports '|1' doesn't contain any public member or cannot be found. Make ...
  75. Navigation Properties are not supported on derived entity types. Entity Set '{1}' has a instance of type '{0}', which is ...