.NET Framework

  1. Binding validation failed because the TransportBindingElement's ManualAddressing property was set to true on a binding that ...
  2. Binding validation failed because the URI represents a subqueue and the ReceiveErrorHandling parameter is set to Move. The ...
  3. Binding validation failed because the WSHttpBinding does not support reliable sessions over transport security (HTTPS). The ...
  4. Binding validation failed. The client cannot send a message. The specified dead letter queue does not exist or cannot be ...
  5. Binding validation failed. The client cannot send messages. A conflict in the binding properties caused this failure. The ...
  6. Binding validation failed. The client cannot send messages. A conflict in the binding properties is causing the failure. ...
  7. Binding validation failed. The client cannot send messages. The CustomDeadLetterQueue property is set, but the DeadLetterQueue ...
  8. Binding validation failed. The client cannot send the message. The DeadLetterQueue is set to Custom, but the CustomDeadLetterQueue ...
  9. Binding validation failed. The service or the client cannot be started. A conflict in the binding properties caused this ...
  10. Binding validation failed. The service or the client cannot be started. The ExactlyOnce property is set to false and ReceiveContext ...
  11. Binding validation failed. The service or the client cannot be started. The ExactlyOnce property is set to true and the Durable ...
  12. Binding {1}:{2} is configured with ContextExchangeMechanism.HttpCookie which is not compatible with the transport type {0}. ...
  13. Bindings for operation {0} cannot specify different use and style values. Binding {1} specifies use {2} and style {3} while ...
  14. BindingSource cannot be its own data source. Do not set the DataSource and DataMember properties to values that refer back ...
  15. binds a critical delegate of type {1} to transparent or safe-critical method {2} in violation of secure delegate binding ...
  16. binds a transparent or safe-critical delegate of type {1} to critical method {2} in violation of secure delegate binding ...
  17. Bitmap object does not directly support the device-independent bitmap format. Either specify auto-conversion or perform a ...
  18. BitmapImage has not been initialized. Call the BeginInit method, set the appropriate properties, and then call the EndInit ...
  19. Bitmaps that are icons cannot be made transparent. Icons natively support transparency. Use the Icon constructor to create ...
  20. blocked the use of type '{1}' in XAML. If you want to load this type, change '{0}'.GetXamlType to return a non-null value ...
  21. blocked the use of type '{1}' in XAML. If you want to serialize this type, change '{0}'.GetXamlType to return a non-null ...
  22. Bookmark scopes require a host that supports key management. The host you are using does not support key management. If you ...
  23. Both Ends on the EdmRelationshipAttribute for relationship '{0}' have the same Role name '{1}'. The ends of a relationship ...
  24. Both If-Match and If-None-Match HTTP headers cannot be specified at the same time. Please specify either one of the headers ...
  25. Both the Endpoint and the EndpointConfigurationName properties are set in activity '{0}' with OperationName='{1}'. However, ...
  26. Both {0} and {1} use the message name '{2}'. Use the MessageName property of the WebMethod custom attribute to specify unique ...
  27. BoundField {0} contains a control that isn't a TextBox. Override OnDataBindField to inherit from BoundField and add different ...
  28. Buffer supplied to MQReceiveMessage for reading the message body was too small. The message cannot be removed from the queue, ...
  29. BuildManager returned an invalid compiled string '{0}'. Make sure appropriate build providers are registered in the conf ...
  30. By clicking "I accept the terms of the License Agreement" and proceeding to use the product, I indicate that I have read, ...
  31. By submitting this report, you will help Microsoft fix problems. Microsoft will treat this report as confidential and anonymous. ...
  32. By submitting this report, you will help Microsoft improve setup. Microsoft will treat this report as confidential and anonymous. ...
  33. ByRef parameter '{0}' cannot convert from '{1}' to '{2}' when assigning back to the matching argument because the conversion ...
  34. Byte array is too large. The maximum size byte array that can be encrypted by this public key implementation is {0} bytes. ...
  35. c: custom. Both session state data and the stored procedures are stored in a custom database. The database name must be specified. ...
  36. Cache Settings are immutable since the extension is already added to the workflow instance or the host extensions collection. ...
  37. Caching protocol has refused the server response. To allow automatic request retrying set request.AllowAutoRedirect=true. ...
  38. Calculating signature with key {0} using signature description {1}, hash algorithm {2}, and asymmetric signature formatter ...
  39. Call to BeginEdit() with shouldApplyChangesImmediately=true cannot be nested inside another EditingScope or another call ...
  40. Callback method {0} is not supported, this can happen if the method is not marked with OperationContractAttribute or if its ...
  41. CallbackBehaviorAttribute can only be run as a behavior on an endpoint with a duplex contract. Contract '{0}' is not duplex, ...
  42. Callbacks are not supported on CommandField when the select button is enabled because other controls on your page that are ...
  43. Callbacks are not supported on TemplateField because some controls cannot update properly in a callback. Turn callbacks off ...
  44. Calling Response.Redirect on a postback can have unpredictable results on mobile devices and gateways. Use RedirectToMobilePage ...
  45. Calling TransactionManager.Reenlist is not allowed after TransactionManager.RecoveryComplete is called for a given resource ...
  46. Calling Validate method of ExceptionValidationRule is not supported. Validation results for ExceptionValidationRule are set ...
  47. callstack information is not captured by default for performance reasons. Please enable captureAllocatedCallStack config ...
  48. Can find neither a device capability named '{0}' nor a public non-static method on the page named '{0}' that returns a System.Boolean ...
  49. Can not bind selected property. Property binding is not supported for non Dependency Properties, selecting multiple activities ...
  50. Can not determine default value for optional parameter '{1}' of type '{2}', specified in method '{0}'. A default value is ...
  51. Can not set {0} as the remaining arguments parameter for parameter set {1} because that parameter set already has a parameter ...
  52. Can't continue with the creation of this connection because at least one of the Web Parts or connection points has disappeared ...
  53. CancellationHandlerActivity, CompensationHandlerActivity, FaultHandlersActivity, FaultHandlerActivity can not contain FaultHandlersActivity, ...
  54. Cannot accept MaxRange because it is less than MinRange. Specify a MaxRange value that is greater than or equal to the MinRange ...
  55. Cannot accept MinRange {0} because it is not the same type as MaxRange {1}. Verify that the MaxRange and MinRange values ...
  56. Cannot access protected member '%1!ls!' via a qualifier of type '%2!ls!'; the qualifier must be of type '%3!ls!' (or derived ...
  57. Cannot access protected member '{0}' via a qualifier of type '{1}'; the qualifier must be of type '{2}' (or derived from ...
  58. Cannot access the delegate type '{0}' for the '{1}' event. '{0}' has incorrect access level or its assembly does not allow ...
  59. Cannot add a DataRelation or Constraint that has different Locale or CaseSensitive settings between its parent and child ...
  60. Cannot add an instance of {0} to the designer because it would create a circular dependency. Make sure that the type does ...
  61. Cannot add element to property '{0}', because the property can have only one child element if it uses an explicit collection ...
  62. Cannot add or insert the item '{0}' in more than one place. You must first remove it from its current location or clone it. ...
  63. Cannot add outgoing headers to message as MessageVersion in OperationContext.Current '{0}' does not match with the header ...
  64. Cannot add service description with targetNamespace='{0}': binding with name='{1}' already present in the description collection. ...
  65. Cannot add service description with targetNamespace='{0}': message with name='{1}' already present in the description collection. ...
  66. Cannot add service description with targetNamespace='{0}': portType with name='{1}' already present in the description collection. ...
  67. Cannot add service description with targetNamespace='{0}': schema with targetNamespace='{1}' already present in the description ...
  68. Cannot add service description with targetNamespace='{0}': service with name='{1}' already present in the description collection. ...
  69. Cannot add stream upgrade element '{0}'. Another stream upgrade element already exists in the binding '{1}'. There can only ...
  70. Cannot add the '{0}' behavior extension to '{1}' endpoint behavior because the underlying behavior type does not implement ...
  71. Cannot add the behavior extension '{0}' to the service behavior named '{1}' because the underlying behavior type does not ...
  72. Cannot add the message encoding element '{0}'. Another message encoding element already exists in the binding '{1}'. There ...
  73. Cannot add the transport element '{0}'. Another transport element already exists in the binding '{1}'. There can only be ...
  74. Cannot append to this file because its size is unknown. The file must be cast-able to an IStorageItem in order to append. ...
  75. Cannot apply a context that has been marshaled across AppDomains, that was not acquired through a Capture operation or that ...