.NET Framework

  1. Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. ...
  2. Connection Timeout Expired. The timeout period elapsed while attempting to create and initialize a socket to the server. ...
  3. Connection Timeout Expired. The timeout period elapsed while making a pre-login handshake request. This could be because ...
  4. Connection was not accepted because the SecurityContext contained tokens that do not match the current security settings. ...
  5. Connections cannot be created until the pipe has started listening. Call Listen() before attempting to accept a connection. ...
  6. Consider app.config remapping of assembly "{0}" from Version "{1}" {2} to Version "{3}" {4} to solve conflict and get rid ...
  7. Consider applying Windows.Foundation.Metadata.DeprecatedAttribute["{0}", {1}, {2} Or System.ObsoleteAttribute["{0}",{4} to ...
  8. Consider changing config settings in web.config file in your application or site root directory to enable SOAP 1.1 protocol ...
  9. Consider changing the type 'Task' in the method signature to one of the following types instead: Windows.Foundation.IAsyncAction, ...
  10. Considered "{0}", which existed but had a processor architecture "{1}" which does not match the targeted processor architecture ...
  11. Constraints for override and explicit interface implementation methods are inherited from the base method, so they cannot ...
  12. Constraints for this type parameter do not match the constraints on the corresponding type parameter defined on one of the ...
  13. Construct makes an indirect reference to project '|1', which contains '|2'. Add a project reference to '|1' to your project. ...
  14. Constructor {0} is obsolete. The Windows Runtime does not support deprecation on non parameterized constructor and hence ...
  15. ContainerName must be specified either by setting DefaultContainerName in the ObjectContext or by setting DefaultContainerName ...
  16. Contains a list of categories associated with the table header (read by screen readers). The categories can be any string ...
  17. Content model validation resulted in a large number of states, possibly due to large occurrence ranges. Therefore, content ...
  18. Content not valid. The conceptual side Member or Property '{0}' specified as part of this MSL does not exist in MetadataWorkspace. ...
  19. Context 1$x is disconnected. No proxy will be used to service the request on the COM component. This may cause corruption ...
  20. Context 1$x' is disconnected. Releasing the interfaces from the current context (context 2$x). This may cause corruption ...
  21. Context 1$x' is disconnected. Releasing the interfaces from the current context (context 2$x).This may cause corruption or ...
  22. Context cached at the channel cannot be set or retrieved when the context management is disabled at the channel layer. Ensure ...
  23. Context channel received a message with context which does not match the current context cached at the channel. Ensure service ...
  24. Context protocol was unable to parse the context header. Nodes disallowed by the context header schema were found inside ...
  25. ContextBindingElement of binding {0}:{1} is configured with ContextExchangeMode.HttpCookie but the configuration of this ...
  26. Contract does not allow Session, but Binding '{0}' does not support Datagram or is not configured properly to support it. ...
  27. Contract requires TwoWay (either request-reply or duplex), but Binding '{0}' doesn't support it or isn't configured properly ...
  28. ContractDescription '{0}' has zero IsInitiating=true operations; a contract must have at least one IsInitiating=true operation. ...
  29. ContractNamespaceAttribute attribute maps CLR namespace '{2}' to multiple data contract namespaces '{0}' and '{1}'. You can ...
  30. control must contain an IButtonControl with ID {1} in every item template, this maybe include ItemTemplate, EditItemTemplate, ...
  31. Control with ID '{0}' being registered through RegisterAsyncPostBackControl or RegisterPostBackControl must implement either ...
  32. Control with ID '{0}' cannot be registered through both RegisterAsyncPostBackControl and RegisterPostBackControl. This can ...
  33. Controls if the print preview will be rendered with anti-aliasing. Using AntiAlias provides a more accurate display of the ...
  34. Controls whether designers should use snap lines. If true, snap lines will be used as guides. If false, grid lines will be ...
  35. Controls whether the button should be displayed as partially pushed or not, but only if the style of the button is ToggleButton. ...
  36. Controls whether to prompt the user when a new file is about to be created. It is only applicable if 'ValidateNames' is set ...
  37. Controls whether to prompt the user when an existing file is about to be overwritten. It is only applicable if 'ValidateNames' ...
  38. ControlTemplate must be associated with a Control by setting the Control.Template property before it is used to template ...
  39. Conversion failed because the {0} data value overflowed the type specified for the {0} value part in the consumer's buffer. ...
  40. Conversion failed because the {0} data value was signed and the type specified for the {0} value part in the consumer's buffer ...
  41. Conversion failed for command parameter[{0} '{1}' because the data value was signed and the type used by the provider was ...
  42. Correlation parameter type mismatch. {0} property of '{1}' on {2} is of type {3}. The expected type here is {4}. All method/event ...
  43. Correlation value specified does not match the already initialized correlation value on declaration {0} for activity {1}. ...
  44. Corrupt .resources file. Unable to read resources from this file because of invalid header information. Try regenerating ...
  45. could not be resolved in the current scope or context. Make sure that all referenced variables are in scope, that required ...
  46. Could not compile workflow expressions because file '{0}' has an incorrect format. Workflows in this project may still run, ...
  47. Could not compose Service Principal Name (SPN) for Windows Integrated Authentication. Possible causes are server(s) incorrectly ...
  48. Could not create key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
  49. Could not create Windows user token from the credentials specified in the config file. Error from the operating system '{0}' ...
  50. Could not delete key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
  51. Could not delete value 2 from key 3]. { System error 4].} Verify that you have sufficient access to that key, or contact ...
  52. Could not deserialize compound property '{0}' on object of type '{1}'. The property is readonly and the getter method returned ...
  53. Could not deserialize object. Serializer for type '{0}' threw an exception during deserialization. Exception was thrown with ...
  54. Could not deserialize object. The type '{0}' could not be resolved. Attribute values starting with '{' and ending with '}' ...
  55. Could not detect ASP.NET installation or ASP.NET is disabled, skipping the {0} component since it depends upon ASP.NET to ...
  56. Could not detect configuration section {0} in file {1}. Configuration cannot complete since it depends on modifying this ...
  57. Could not detect configuration section {0} is IIS metabase. Configuration cannot complete since it depends on modifying this ...
  58. Could not detect IIS installation or IIS is disabled, skipping the {0} component since it depends upon IIS to function properly. ...
  59. Could not detect MSDTC installation on this machine. The WS-AT protocol requires a correctly installed MSDTC service. Check ...
  60. Could not detect the .NET Framework. If you believe this message to be an error, check your .NET Framework installation to ...
  61. Could not detect the Microsoft.Web.Administration assembly for managing the applicationHost.config file, skipping the {0} ...
  62. Could not detect the WOW64 sublayer, skipping the {0} component since it depends upon WOW64 to function properly. If you ...
  63. Could not detect the WOW64 sublayer. If you believe this message to be an error, check your WOW64 installation to make sure ...
  64. Could not detect WAS installation or WAS is disabled, skipping the {0} component since it depends upon WAS to function properly. ...
  65. Could not determine the core reference assembly. Please make sure mscorlib.dll and System.Runtime.dll is referenced using ...
  66. Could not determine whether '%1' is a multifile assembly. The assembly manifest may be corrupt. Assuming a non-multifile ...
  67. Could not establish a connection to the database. If you have not yet created the SQL Server database, exit the Web Site ...
  68. Could not find a base address that matches scheme {0} for the endpoint with binding {1}. Registered base address schemes ...
  69. Could not find a manifest resource entry called "{0}" in assembly "{1}". Please check spelling, capitalization, and build ...
  70. Could not find a property named '{0}' on the type specified by the DataObjectTypeName property in ObjectDataSource '{1}'. ...
  71. Could not find a row that matches the given keys in the original values stored in ViewState. Ensure that the 'keys' dictionary ...
  72. Could not find an implementation of the query pattern for source type '%1!ls!'. '%2!ls!' not found. Are you missing a reference ...
  73. Could not find an implementation of the query pattern for source type '%1!ls!'. '%2!ls!' not found. Are you missing a reference ...
  74. Could not find an implementation of the query pattern for source type '%1!ls!'. '%2!ls!' not found. Consider explicitly specifying ...
  75. Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "{0}" was correctly ...