.NET Framework

  1. The execution of an InstancePersistenceCommand was interrupted because the instance key was not associated to an instance. ...
  2. The execution of an InstancePersistenceCommand was interrupted because the instance owner registration for owner ID '{0}' ...
  3. The execution of an InstancePersistenceCommand was interrupted because the instance owner registration has become invalid. ...
  4. The execution of an InstancePersistenceCommand was interrupted by a key collision. The instance key with value '{0}' could ...
  5. The execution of an InstancePersistenceCommand was interrupted by a key collision. The instance key with value '{1}' could ...
  6. The execution of this query requires the APPLY operator, which is not supported in versions of SQL Server earlier than SQL ...
  7. The existing object in the ObjectContext is in the {0} state. Changes can only be applied when the existing object is in ...
  8. The existing object in the ObjectContext is in the {0} state. Original values can be changed when the existing object is ...
  9. The expression defining a projection to be passed to the Select query builder method. Query results will be read-only if ...
  10. The expression for newly added argument '{0}' contains Activity '{1}', which can idle during execution. To enable dynamic ...
  11. The expression passed to the GroupBy query builder method. It requires the Select property to be defined. Query results will ...
  12. The expression passed to the OrderBy operator used for ordering groups after a GroupBy has been performed during the Select ...
  13. The expression prefix '{0}' was not found in config. You will need to add an definition to your config file for the page ...
  14. The expression prefix '{0}' was not found in config. You will need to add an definition to your config file for the page ...
  15. The expression prefix '{0}' was not recognized. Please correct the prefix or register the prefix in the section of configuration. ...
  16. The expression to the left of the logical operator "{0}" must return a Boolean result. Currently it evaluates to type "{1}". ...
  17. The expression to the right of the logical operator "{0}" must return a Boolean result. Currently it evaluates to type "{1}". ...
  18. The ExtendedProtectionPolicy.CustomServiceNames list specified on the WCF transport is not a subset of the list of custom ...
  19. The ExtendedProtectionPolicy.PolicyEnforcement values do not match. IIS has a value of {0} while the WCF Transport has a ...
  20. The ExtendedProtectionPolicy.ProtectionScenario values do not match. IIS has a value of {0} while the WCF Transport has a ...
  21. The extension '{0}' is not registered with WCF/WF handler. Please either remove relativeAddress '{1}' in '{2}' from configuration ...
  22. The extension method '{0}' can only be used with message instances that contain an '{1}' instance in the message's properties ...
  23. The external dictionary does not contain definitions for all the required strings. The {0} string is not available in the ...
  24. The facet '{0}' with a value '{1}' is outside the range {2}-{3} specified by the facet description. The column '{4}' in the ...
  25. The feature you are attempting to use, '%1!ls!', has not been implemented. Please refrain from using it until a later time. ...
  26. The feature you are attempting to use, '%1!ls!', may not be fully implemented by the compiler and/or runtime. Proceed at ...
  27. The field '{0}' could not be found on the target object. Make sure that the field is defined as an instance variable on the ...
  28. The file %1 was created for %2 operating system languages. Please contact your administrator to obtain the file appropriate ...
  29. The file %1 was created for %2 operating system languages. Please contact your administrator to obtain the file appropriate ...
  30. The file %1 was created for %2 operating system. Please contact your administrator to obtain the file for your operating ...
  31. The file %1 was created for %2 operating system. Please contact your administrator to obtain the file for your operating ...
  32. The file %1 was created for %2 processor type. Please contact your administrator to obtain the file for your processor type, ...
  33. The file %1 was created for %2 processor type. Please contact your administrator to obtain the file for your processor type, ...
  34. The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network ...
  35. The file '{0}' does not have any class definitions in it. Add a class definition. If you have verified that there is at least ...
  36. The file '{0}' does not support code parsing or generation because it is not contained within a project that supports code. ...
  37. The file '{0}' may have come from a location that isn't fully trusted. It could present a security risk by opening the file ...
  38. The file 2][3 is being held in use{ by the following process: Name: 4], Id: 5], Window Title: '[6]'}. Close that application ...
  39. The file containing the saved state for the {0} assembly, located at {1}, could not be read, and the file might have been ...
  40. The file does not contain a valid card. Select a different file, and try again. If this is a managed Information Card, contact ...
  41. The file format is not compatible with current targeting framework. To convert the file format, please explicitly save the ...
  42. The file name '{0}' is invalid because the same file name is already referenced by the configuration hierarchy you have opened. ...
  43. The file name specified in 'CompileWith' property is invalid. Please make sure that file extension is '{0}'. Also a file ...
  44. The file named "{0}" does not have a known extension. Managed resource files must end in .ResX, .restext, .txt, .resources, ...
  45. The file named "{0}" does not have a known extension. Managed resource files must end in .ResX, .restext, .txt, or .resources. ...
  46. The file {0} is not part of any project in the solution so it cannot be opened. Add the file to a project and try again. ...
  47. The filename used with the %1 switch cannot be over 200 characters long. If a directory was not specified this total length ...
  48. The filename used with the /CreateUnattend switch cannot be over 200 characters long. If a directory was not specified this ...
  49. The filter control '{0}' does not specify a context type name and a table name and this information could not be inferred ...
  50. The filter control '{0}' has an invalid context type name '{1}'. Make sure its ContextTypeName property contains a valid ...
  51. The filter control '{0}' has an invalid data field name '{1}'. Make sure its DataField property contains a valid field name. ...
  52. The filter control '{0}' has an unknown context type name '{1}' that is not registered with any model. Make sure its ContextTypeName ...
  53. The filter control '{0}' is associated with a context type but is missing the table name. Make sure its TableName property ...
  54. The filter control '{0}' is associated with a table but is missing the context type name. Make sure its ContextTypeName property ...
  55. The first operand of an overloaded shift operator must have the same type as the containing type, and the type of the second ...
  56. The first parameter of type '{0}' specified in the content does not match the type '{1}' specified as the return value for ...
  57. The first step in securing your site is to identify users (authentication). The method for establishing a user's identity ...
  58. The following assemblies are installed SDK assemblies but could not be shown in the customize toolbox dialog because they ...
  59. The following assembly could not be resolved: '{0}'. The assembly is excluded from the target framework profile{1}. If this ...
  60. The following assembly has dependencies on a version of the .NET Framework that is higher than the target and might not load ...
  61. The following code example is the Web.config file that is created by the Web Site Administration Tool within a restricted ...
  62. The following code is the Web.config file that is generated by the Web Site Administration Tool after specifying that the ...
  63. The following command compiles the application /MyApp in-place. The effect is that no more compilations will be needed when ...
  64. The following command does *not* rely on the IIS metabase, as it explicitly specifies the physical source directory of the ...
  65. The following component was installed, but some errors did occur. If you canceled during setup, the component might have ...
  66. The following components were installed, but some errors did occur. If you canceled during setup, the component might have ...
  67. The following device filters are not valid as specified: {0} Equality Comparison device filters must have a defined Compare ...
  68. The following device filters are not valid as specified: {0} Equality Comparison device filters must have a defined Compare ...
  69. The following error occurred while determining how to marshal the parameters of member '%1$s' of type '%2$s': %3$s This is ...
  70. The following error was encountered while attempting to parse this project's Web.config file: {0} Please correct this condition ...
  71. The following error was encountered while attempting to parse this project's Web.config file: {0} Please correct this condition ...
  72. The following exception occurred in the DataGridView: {0} To replace this default dialog please handle the DataError event. ...
  73. The following exception occurred in the DataGridView: {0} To replace this default dialog please handle the DataError event. ...
  74. The following exception was thrown by the web event provider '%1' in the application '%2' (in an application lifetime a maximum ...
  75. The following exception was thrown by the web event provider '%1' in the application '%2' (in an application lifetime a maximum ...