.NET Framework

  1. The Deployment Package Wizard will now create the Windows Installer Package. Deploy the policy through Group Policy or Systems ...
  2. The Deployment Provider specified in the manifest cannot be reached. Maybe due to network error and/or the deployment provider ...
  3. The depth of the selected item is larger than StaticDisplayLevels + MaximumDynamicDisplayLevels. This could be caused by ...
  4. The derived element {0} at ({1}, {2}) is not a valid restriction of the base all particle at ({3}, {4}) according to Elt:All/Choice/Sequence ...
  5. The derived element {0} at ({1}, {2}) is not a valid restriction of the base choice particle at ({3}, {4}) according to Elt:All/Choice/Sequence ...
  6. The derived element {0} at ({1}, {2}) is not a valid restriction of the base sequence particle at ({3}, {4}) according to ...
  7. The derived key's generation ('{0}') and length ('{1}' bytes) result in a key derivation offset that is greater than the ...
  8. The derived particle cannot have more members than the base particle - All:All,Sequence:Sequence - Recurse Rule 2 / Choice:Choice ...
  9. The derived particle's occurrence range at ({0}, {1}) is not a valid restriction of the base wildcard's occurrence range ...
  10. The derived particle's range is not a valid restriction of the base particle's range according to All:All,Sequence:Sequence ...
  11. The derived sequence particle at ({0}, {1}) is not a valid restriction of the base all particle at ({2}, {3}) according to ...
  12. The derived sequence particle at ({0}, {1}) is not a valid restriction of the base choice particle at ({2}, {3}) according ...
  13. The derived wildcard's 'processContents' must be identical to or stronger than the base wildcard's 'processContents', where ...
  14. The derived wildcard's namespace constraint must be an intensional subset of the base wildcard's namespace constraint, Any:Any ...
  15. The derived wildcard's occurrence range is not a valid restriction of the base wildcard's occurrence range, Any:Any - NSSubset ...
  16. The description for Event ID '{0}' in Source '{1}' cannot be found. The local computer may not have the necessary registry ...
  17. The deserializer cannot load the type to deserialize because type '{1}' could not be found in assembly '{0}'. Check that ...
  18. The deserializer has no knowledge of the type to use during deserialization. Consider adding the type specified as factory ...
  19. The designer cannot process the code at line {0}, please see the Task List for details. The code within the method '{1}' ...
  20. The designer cannot process the code at line {0}: {1} The code within the method '{2}' is generated by the designer and should ...
  21. The designer cannot process the code at line {0}: {1} The code within the method '{2}' is generated by the designer and should ...
  22. The designer cannot process unknown name '{0}' at line {1}. The code within the method '{2}' is generated by the designer ...
  23. The designer cannot process unknown name '{0}'. The code within the method '{1}' is generated by the designer and should ...
  24. The designer could not be shown for this file because none of the classes within it can be designed. The designer inspected ...
  25. The designer could not be shown for this file because none of the classes within it can be designed. The designer inspected ...
  26. The designer has fixed inconsistent type names in a partial class. The partial class name '{1}' has been changed to '{0}'. ...
  27. The designer inspected the following classes in the file: {0}. The base class {0} could not be loaded. Ensure the assembly ...
  28. The designer loader class {0} either does not inherit from DesignerLoader or does not implement IVSMDDesignerLoader. Both ...
  29. The designer transaction '{0}' cannot be committed or canceled because nested transaction '{1}' is still active. Commit or ...
  30. The details of this personal card indicate what data will be sent to the site. You can change the data, name, and picture ...
  31. The details of this personal card indicate what data will be sent to the site. You can change the date, name, and picture ...
  32. The dictionary of type '{0}' cannot be deserialized as a simple dictionary because its key type '{1}' does not have a public ...
  33. The DigitSubstitution property must be of a valid member of the DigitShapes enumeration. Valid entries include Context, NativeNational ...
  34. The directionality of activity delegate argument '{0}' in DelegateArguments dictionary is '{1}'. The expected directionality ...
  35. The directionality of activity delegate parameter '{0}' in DelegateParameters dictionary is '{1}'. The expected directionality ...
  36. The directive is missing a 'VaryByParam' attribute, which should be set to "none", "*", or a semicolon separated list of ...
  37. The DisconnectWebParts method cannot be called after connections have already been activated (in WebPartManager.PreRender). ...
  38. The discovery message cannot be deserialized because the required attribute InstanceId is missing from the AppSequence header. ...
  39. The discovery message cannot be deserialized because the required attribute MessageNumber is missing from the AppSequence ...
  40. The DiscoveryClientBindingElement does not appear first in the BindingElementCollection of the Binding. Please change the ...
  41. The DiscoveryClientBindingElement is present in the BindingElementCollection of the Binding. Please ensure that the Binding ...
  42. The DiscoveryClientChannel failed to create the channel with a discovered endpoint with EndpointAddress='%1' and Via='%2'. ...
  43. The DiscoveryClientChannel failed to create the channel with a discovered endpoint with EndpointAddress='{0}' and Via='{1}'. ...
  44. The DiscoveryClientChannel failed to open the channel with a discovered endpoint with EndpointAddress='%1' and Via='%2'. ...
  45. The DiscoveryClientChannel failed to open the channel with a discovered endpoint with EndpointAddress='{0}' and Via='{1}'. ...
  46. The DiscoveryClientChannel successfully discovered an endpoint and opened the channel using it. The client is connected to ...
  47. The DiscoveryClientChannel successfully discovered an endpoint and opened the channel using it. The client is connected to ...
  48. The DiscoveryServiceExtension cannot be attached to the specified ServiceHostBase because it is already attached to a different ...
  49. The DispatchRuntime.EnsureOrderedDispatch property is set to true, but the DispatchRuntime.ConcurrencyMode is not set to ...
  50. The DisplayIndex for the DataGridColumn with Header '{0}' is out of range. DisplayIndex must be greater than or equal to ...
  51. The distributedTransactionManager attribute for the LocalTransactionManager must specify a valid configured Transaction Manager. ...
  52. The document at the url {0} was not recognized as a known document type. The error message from each known type may help ...
  53. The document was not recognized as a known document type (WSDL, XML Schema, or Discovery document) for the following reason: ...
  54. The Domain Application membership condition is true if the AppDomain where code access security policy resolution is taking ...
  55. The drive you have selected is invalid. The drive is either read-only or does not have enough free disk space for the selected ...
  56. The duration cannot be returned for TimeSpan.MinValue because the absolute value of TimeSpan.MinValue exceeds the value of ...
  57. The Duration property must be greater than TimeSpan.Zero. To terminate the find operation based on the number of results ...
  58. The duration spent while attempting to connect to this server was - Pre-Login initialization={0}; handshake={1}; Login initialization={2}; ...
  59. The duration spent while attempting to connect to this server was - Pre-Login initialization={0}; handshake={1}; Login initialization={2}; ...
  60. The duration spent while attempting to connect to this server was - Pre-Login initialization={0}; handshake={1}; Login initialization={2}; ...
  61. The dynamically dispatched call to method '%1!ls!' may fail at runtime because one or more applicable overloads are conditional ...
  62. The DynamicControl/DynamicField needs to exist inside a data control that is bound to a data source that supports Dynamic ...
  63. The DynamicControlParameter has no Name property, which means that you are setting the primary key. However, the control ...
  64. The DynamicEntity control '{0}' needs to exist in a data control that is bound to a data source that supports Dynamic Data. ...
  65. The DynamicHyperLink control '{0}' could not determine the MetaTable to base the link on. Make sure that the the control ...
  66. The EDMVersion of the item collection {0} is not an EDMVersion that the runtime supports. The supported versions are {1}. ...
  67. The element 'xsl:perform-sort' cannot have 'select' attribute any content other than 'xsl:sort' and 'xsl:fallback' instructions. ...
  68. The element '{0}' in namespace '{1}' is not valid. This either means that element '{0}' is a duplicate element, or that it ...
  69. The element '{0}' is not valid in the locked list for this section. The following elements can be locked: {1}. Multiple elements ...
  70. The element at index {0} in the collection of objects to refresh has a null EntityKey property value or is not attached to ...
  71. The element at index {0} in the collection of objects to refresh is a duplicate of an object that is already in the collection. ...
  72. The element at index {0} in the collection of objects to refresh is in the added state. Objects in this state cannot be refreshed. ...
  73. The element of the Web.config file does not have a 'targetFramework' attribute. Therefore ASP.NET assumes that the Web application ...
  74. The element type '{0}' and the CollectionType '{1}' are not compatible. The IN expression only supports entity, scalar and ...
  75. The element {0} has been attributed with an XmlAnyElementAttribute and a namespace {1}, but no name. When a namespace is ...