.NET Framework

  1. Method '{0}' is a public virtual method on an unsealed class. The Windows Runtime requires virtual methods on unsealed types ...
  2. Method '{0}' on type '{1}' is marked as a query interceptor method but has {2} parameters. Query interceptors should take ...
  3. Method '{0}' on type '{1}' is not a valid connection provider. It must be public, return an object, and take no parameters. ...
  4. Method '{0}' on type '{1}' us marked as an authorization method but has a return type of '{2}' when no return value is expected. ...
  5. Method '{0}' overrides a virtual method. An override method must be sealed in order to override an inherited virtual method. ...
  6. Method '{0}' returns '{1}', which is not a valid Windows Runtime type. Methods exposed to Windows Runtime must return only ...
  7. Method '{1}' could not be resolved. Either method could not be found or method signature does not match the delegate type. ...
  8. Method '{1}' has {0}, but enclosing type '{2}' does not have ServiceContractAttribute. {0} can only be used on methods in ...
  9. Method '|1' cannot implement partial method '|2' because '|3' already implements it. Only one method can implement a partial ...
  10. Method '|1' has a link demand, but overrides or implements the following methods which do not have a link demand. A security ...
  11. Method {0} is not supported on this proxy, this can happen if the method is not marked with OperationContractAttribute or ...
  12. Method {0} on type {1} is an implementation of the service contract interface {2}. Service Description altering attributes ...
  13. Method {0}.{1} can not be reflected. Parameter '{2}' has invalid accessor: If you are using the Rpc\Literal method, you can ...
  14. Method {0}.{1} can not be reflected. Parameter '{2}' may not be used with Rpc\Literal SOAP messages because it is declared ...
  15. Method, operator, or accessor '%1!ls!' is marked external and has no attributes on it. Consider adding a DllImport attribute ...
  16. Methods decorated with the SuppressUnmanagedCodeSecurity attribute have an implicit LinkDemand placed upon all of their callers. ...
  17. Mex retrival at {0} found no service endpoints that satisfy requirements. Specify an endpoint that matches the issuer and ...
  18. Microsoft .NET Framework 2.0 SP2 LangPack must be installed before you start the installation process. Install Microsoft ...
  19. Microsoft .NET Framework 2.0SP1 LangPack must be installed before you start the installation process. Install Microsoft .NET ...
  20. Microsoft .NET Framework 2.0SP1 must be installed before you start the installation process. Install Microsoft .NET Framework ...
  21. Microsoft .NET Framework 2.0SP2 must be installed before you start the installation process. Install Microsoft .NET Framework ...
  22. Microsoft .NET Framework 3.0 SP2 must be installed before you start the installation process. Install Microsoft .NET Framework ...
  23. Microsoft .NET Framework 3.0SP1 must be installed before you start the installation process. Install Microsoft .NET Framework ...
  24. Microsoft .NET Framework 4 is already a part of this operating system, but it is currently turned off. To enable the .NET ...
  25. Microsoft .NET Framework 4.5 is already a part of this operating system, but it is currently turned off. To enable the .NET ...
  26. Microsoft .NET Framework Assembly Registration Utility version {0} for Microsoft .NET Framework version {0} Copyright (C) ...
  27. Microsoft .NET Framework v2.0 SP1 must be installed before you start the installation process. Install Microsoft .NET Framework ...
  28. Microsoft .NET Framework v2.0 SP2 must be installed before you start the installation process. Install Microsoft .NET Framework ...
  29. Microsoft .NET Framework v3.5 must be installed before you start the installation process. Install Microsoft .NET Framework ...
  30. Microsoft .NET Framework v3.5 SP1 must be installed before you start the installation process. Install Microsoft .NET Framework ...
  31. Microsoft is a registered trademark of Microsoft Corporation. Visual Studio is a registered trademark of Microsoft Corporation. ...
  32. Microsoft is a registered trademark of Microsoft Corporation. Windows is a registered trademark of Microsoft Corporation. ...
  33. Microsoft is a registered trademark of Microsoft Corporation. Windows is a registered trademark of Microsoft Corporation. ...
  34. Microsoft Visual J# Redistributable Package 2.0 is required to develop with Visual J# in Visual Web Developer Express Edition. ...
  35. Microsoft.VisualBasic.ComClassAttribute' cannot be applied to a class that is generic or contained inside a generic type. ...
  36. Microsoft.VisualBasic.ComClassAttribute' is specified for class '|1' but '|1' has no public members that can be exposed to ...
  37. Microsoft.VisualBasic.ComClassAttribute' on class '|1' implicitly declares |2 '|3', which conflicts with a member of the ...
  38. MimeType attribute is specified for property '{0}', which is of type '{1}', but it should only be specified on properties ...
  39. Minimum required version specified in the deployment manifest cannot be lower than the previous minimum required version. ...
  40. Minimum value '{0}' specified for '{1}' in type '{2} is not valid. Minimum value must be always less than the maximum value. ...
  41. Mismatched versions of PresentationCore.dll, Milcore.dll, WindowsCodecs.dll, or D3d9.dll. Check that these DLLs come from ...
  42. Missing 'BaseTypeAttribute' for property '{0}'. Specify either a 'BaseTypeAttribute' or implement 'IBaseTypeProvider' interface ...
  43. Missing change set boundary delimiter. Please make sure that change set boundary delimiter is specified to mark the end of ...
  44. Missing default entity set name. Please make sure that there is a valid default entity set name specified in the ObjectContext. ...
  45. Missing default value for '{0}' in type '{1}'. Default value must be specified because the '{0}' is specified as constant. ...
  46. Mixed mode assembly is built against version '%1' of the runtime and cannot be loaded in the %2 runtime without additional ...
  47. Modifications to tables where a primary key column has property '{0}' set to '{1}' are not supported. Use '{2}' pattern instead. ...
  48. Modifies UPDATE and DELETE statements to detect whether the database has changed since the record was loaded into the DataSet. ...
  49. ModuleResolveEvent returned an incompatible Module. ReflectionOnly assemblies cannot bind to normal Modules, nor vice-versa. ...
  50. More than one '{0}' objects were found in the BindingParameters of the BindingContext. This is usually caused by having multiple ...
  51. More than one condition named "{0}" was found in the condition collection. Only the first condition will be used. Make sure ...
  52. More than one IStreamUpgradeProviderElement was found in the BindingParameters of the BindingContext. This usually is caused ...
  53. More than one MessageEncodingBindingElement was found in the BindingParameters of the BindingContext. This usually is caused ...
  54. More than one method with the specified name and parameters was found for ObjectDataSource '{0}'. Adding the DataObjectMethodAttribute ...
  55. More than one PeerCustomResolverBindingElement was found in the BindingParameters of the BindingContext. This usually is ...
  56. More than one PeerResolverBindingElement was found in the BindingParameters of the BindingContext. This usually is caused ...
  57. More than one SecurityBindingElement found in the binding ('{0}', '{1}) for contract ('{2}', '{3}'). Only one SecurityBindingElement ...
  58. Most changes to configuration settings that you make in the Web Site Administration Tool take effect immediately. For settings ...
  59. Most changes to configuration settings that you make in the Web Site Administration Tool take effect immediately. This requires ...
  60. MSB1020: The logger was not found. Check the following: 1.) The logger name specified is the same as the name of the logger ...
  61. MSB1020: The logger {0} was not found. Check the following: 1.) The logger name specified is the same as the name of the ...
  62. MSB2008: This Visual Studio project system cannot convert "{0}" projects. It can only be used to convert C#, VB, and VJ# ...
  63. MSB2012: Project-to-project references to web projects are no longer supported and therefore cannot be converted. Please ...
  64. MSB2013: The project-to-project reference with GUID {0} could not be converted because a valid .SLN file containing all projects ...
  65. MSB2015: Found an element in the original project file. This cannot be converted to Visual Studio .NET and is being ignored. ...
  66. MSB3011: "{0}" was not found. Either 1) Install the .NET Framework SDK, which will install AL.exe. Or 2) Pass the correct ...
  67. MSB3024: Could not copy the file "{0}" to the destination file "{1}", because the destination is a folder instead of a file. ...
  68. MSB3042: A namespace or class definition was found within a conditional compilation directive in the file "{0}". This may ...
  69. MSB3071: All drive letters from A: through Z: are currently in use. Since the working directory "{0}" is a UNC path, the ...
  70. MSB3082: Task failed because "{0}" was not found, or the .NET Framework {1} is not installed. Please install the .NET Framework ...
  71. MSB3083: The item "{0}" was specified more than once in the "{1}" parameter and both items had the same value "{2}" for the ...
  72. MSB3084: Task attempted to find "{0}" in two locations. 1) Under the "{1}" processor specific directory which is generated ...
  73. MSB3086: Task could not find "{0}" using the SdkToolsPath "{1}" or the registry key "{2}". Make sure the SdkToolsPath is ...
  74. MSB3087: An incompatible host object was passed into the "{0}" task. The host object for this task must implement the "{1}" ...
  75. MSB3091: Task failed because "{0}" was not found, or the .NET Framework SDK {1} is not installed. The task is looking for ...