.NET Framework

  1. The metadata specified in the connection string could not be loaded. Consider rebuilding the web project to build assemblies ...
  2. The metadata stored by the ObjectContext is different than the metadata stored by the ObjectContext's connection. This can ...
  3. The MetadataExchangeClient can only get metadata from http and https MetadataLocations. It cannot get metadata from '{0}'. ...
  4. The MetadataExchangeClient can only get metadata from http or https addresses when using MetadataExchangeClientMode HttpGet. ...
  5. The MetadataExchangeClient instance could not be initialized because no Binding is available for scheme '{0}'. You can supply ...
  6. The MetadataExchangeClient was not supplied with a MetadataReference or MetadataLocation from which to get metadata. You ...
  7. The MetadataResolver cannot recieve an empty contracts argument to the Resolve or BeginResolve methods. You must supply at ...
  8. The method 'First' can only be used as a final query operation. Consider using the method 'FirstOrDefault' in this instance ...
  9. The method 'Skip' is only supported for sorted input in LINQ to Entities. The method 'OrderBy' must be called before the ...
  10. The method '{0}' can be called only if the corresponding RuntimeTransactionHandle object is registered as an execution property. ...
  11. The method '{0}' has a parameter named '{1}' which is the same as the default return value name. Consider using another name ...
  12. The method '{0}' has the return value named '{1}' which is the same as a parameter name. Windows Runtime method parameters ...
  13. The method '{1}' in type '{0}' is marked IsOneWay=true and declares one or more FaultContractAttributes. One-way methods ...
  14. The method result type '{0}' is not supported for this method argument. A method that produces an instance of a DbExpression-derived ...
  15. The method specified by the PreApplicationStartMethodAttribute on assembly '{0}' cannot be resolved. Type: '{1}', MethodName: ...
  16. The Method with name '{1}' in Type '{0}' could not be invoked because the application does not have permission to invoke ...
  17. The method {0} does not have a request element. You can use a RoutingStyle of SoapAction on the XML Web service, use the ...
  18. The methods 'Single' and 'SingleOrDefault' can only be used as a final query operation. Consider using the method 'FirstOrDefault' ...
  19. The methods {0} and {1} use the same request element . When the RoutingStyle of the XML Web service is RequestElement, request ...
  20. The methods {0} and {1} use the same request element and the methods {0} and {4} use the same SOAPAction '{5}'. Each method ...
  21. The methods {0} and {1} use the same SOAPAction '{2}'. When the RoutingStyle of the XML Web service is SoapAction, SOAPAction ...
  22. The mode '{0}' requires at least one 'incsdl' or 'inssdl' argument. Verify that at least one .csdl or .ssdl file is in the ...
  23. The MSBuild cache file "{0}" is inaccessible. Ensure you have access to the directory and that this file is not deleted during ...
  24. The MSBuild task is skipping the remaining targets and projects because the StopOnFirstFailure parameter was set to true. ...
  25. The MSDN Express Library contains additional product documentation for all Visual Studio Express Editions. You can choose ...
  26. The MSDTC transaction manager's WS-AtomicTransaction protocol service '{0}' is disabled and cannot unmarshal incoming transactions. ...
  27. The MSDTC transaction manager's WS-AtomicTransaction protocol service is disabled and cannot unmarshal incoming transactions. ...
  28. The MSDTC TransactionBridge failed during recovery. This is a fatal condition, so the MSDTC service was terminated.%r Exception: ...
  29. The MSDTC TransactionBridge failed during recovery. This is a fatal condition, so the MSDTC service was terminated.%r Exception: ...
  30. The MSDTC WS-AT protocol failed at the beginning of recovery. As a result, WS-AT functionality will be disabled.%r Protocol ...
  31. The MSDTC WS-AT protocol failed at the beginning of recovery. As a result, WS-AT functionality will be disabled.%r Protocol ...
  32. The MsmqIntegrationBinding validation failed. The service cannot be started. The {0} binding does not support the method ...
  33. The multiplicity '{0}' on End '{1}' in the conceptual side Association '{2}' doesn't match with multiplicity '{3}' on end ...
  34. The name '%1!ls!' is not in scope on the left side of 'equals'. Consider swapping the expressions on either side of 'equals'. ...
  35. The name '%1!ls!' is not in scope on the right side of 'equals'. Consider swapping the expressions on either side of 'equals'. ...
  36. The name '{0}' is ambiguous. '{0}' is defined in both the '{1}' namespace and the '{2}' namespace. To disambiguate, either ...
  37. The name of the class that contains the Main method that you want called on program startup. The (Not set) option is valid ...
  38. The name of the parameter on the Select Command that accepts a sort expression, if any. This is only supported when using ...
  39. The name of the policy being imported for contract '{0}:{1}' is invalid:'{2}'. It should be either '{3}', '{4}' or '{5}'. ...
  40. The name of the project's primary output file (also known as the program image). This property reflects the current value ...
  41. The name of the query string field for the current page index. The pager will use the query string when this property is ...
  42. The name of your SMTP server. The default is localhost , which means that ASP.NET will use an SMTP server on the local computer. ...
  43. The name of your SMTP server. The default is localhost , which means that ASP.NET will use an SMTP server on the local computer. ...
  44. The namespace '%2!ls!' in '%1!ls!' conflicts with the imported type '%4!ls!' in '%3!ls!'. Using the namespace defined in ...
  45. The namespace '{0}' is a system namespace and is implicitly referred by every schema. You cannot specify an explicit reference ...
  46. The namespace alias qualifier '::' always resolves to a type or namespace so is illegal here. Consider using '.' instead. ...
  47. The namespace of element '{0}'is not valid with respect to the wildcard's namespace constraint in the base, Elt:Any - NSCompat ...
  48. The native component calling into the CLR through this ComCallWrapper has performed an illegal cast on this IUnknown or IDispatch ...
  49. The navigation property '{0}' on entity of type '{1}' must implement IEnumerable in order for Entity Framework to be able ...
  50. The NavigationProperty '{0}' on the type '{1}' is the source of a generated property '{2}' which conflicts with a member ...
  51. The necessary size to buffer a sequence message has exceeded the configured buffer quota. Because of this the reliable session ...
  52. The negative value '{0}' is returned when calling provider's '{1}' method. The method should return non-negative integer. ...
  53. The negotiation RequestSecurityTokenResponse has a different context from the authenticator RequestSecurityTokenResponse. ...
  54. The network adapter identified by "{0}" cannot be used by the UDP transport because it does not appear to be connected to ...
  55. The network adapter identified by "{0}" is not suitable for multicast because it does not support multicast, it is receive ...
  56. The new base type you have selected does not support activity containment. All child activities of your custom activity will ...
  57. The non-composable function import '{0}' is mapped to the composable store function '{1}'. Non-composable function imports ...
  58. The NT service '{0}' failed to start because it could not publish the listening endpoint. See inner exception for more information. ...
  59. The NT service '{0}' failed to start because the listening endpoint cannot be created. See inner exception for more information. ...
  60. The NT service failed to start; the listening endpoint could not be published.%r Error Code: %1%r Process Name: %2%r Process ...
  61. The NT service failed to start; the listening endpoint could not be published.%r Error Code: %1%r Process Name: %2%r Process ...
  62. The number of activities in this ID space has exceeded Int32.MaxValue. Refactor some portion of the workflow into a new Activity ...
  63. The number of bytes available is inconsistent with the HTTP Content-Length header. There may have been a network error or ...
  64. The number of calls to this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics ...
  65. The number of calls to this endpoint that are in progress. http://msdn.microsoft.com/en-US/library/System.ServiceModel.D ...
  66. The number of calls to this endpoint that failed authorization per second. http://msdn.microsoft.com/en-US/library/Syste ...
  67. The number of calls to this endpoint that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceMo ...
  68. The number of calls to this endpoint that failed validation or authentication per second. http://go.microsoft.com/fwlink/?LinkId=222657 ...
  69. The number of calls to this endpoint that failed validation or authentication per second. http://msdn.microsoft.com/en-U ...
  70. The number of calls to this endpoint that failed validation or authentication. http://go.microsoft.com/fwlink/?LinkId=222656 ...
  71. The number of calls to this endpoint that failed validation or authentication. http://msdn.microsoft.com/en-US/library/S ...
  72. The number of calls to this endpoint that returned faults per second. http://msdn.microsoft.com/en-US/library/System.Ser ...
  73. The number of calls to this endpoint that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.D ...
  74. The number of calls to this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.Calls.aspx ...
  75. The number of calls to this operation per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostic ...