UI Translation

Visual Studio 2010

  1. The _ATL_MIN_CRT preprocessor definition is no longer supported in ATL. The setting Minimize CRT Use in ATL' has been removed ...
  2. The _vti_pvt folder does not exist. Creating _vti_pvt. After this folder is created, re-install Windows SharePoint Services ...
  3. The {0} '{1}' contains a set of TablixMembers with FixedData set to true in the TablixColumnHierarchy which is incompatible ...
  4. The {0} '{1}' contains an invalid {2} (Expected: {3}; Actual {4}). The {2} of inner or nested DataRegions must be the same ...
  5. The {0} '{1}' contains an invalid {2} Name, '{3}'. The name must be greater than 0 and less than or equal to {4} characters. ...
  6. The {0} '{1}' contains an invalid {2}. There is a {3} with an invalid {4} at level {5}. If there is a {3} with a {4} in this ...
  7. The {0} '{1}' has an inconsistent number of {2}Cells within the {2}Row. Each {2}Row must have the same number of {2}Cells. ...
  8. The {0} '{1}' has an incorrect number of TablixCells. The number of TablixCells in a TablixRow must equal the number of innermost ...
  9. The {0} '{1}' has an incorrect number of TablixRows. The number of TablixRows must equal the number of innermost TablixMembers ...
  10. The {0} '{1}' has an incorrectly set {2} properties within the {3}. All TablixMembers with FixedData set to true must be ...
  11. The {0} '{1}' has an incorrectly set {2} property within the {3}. Only the outermost TablixMembers in a hierarchy can have ...
  12. The {0} '{1}' has an incorrectly set {2} property. {2} is not allowed to be set on row TablixMember, unless it is also set ...
  13. The {0} '{1}' has an incorrectly set {2} property. {2} is not allowed to be set on the first column TablixMember when Tablix.GroupBeforeRowHeaders ...
  14. The {0} '{1}' has an invalid set of TablixCells. The combined value of the ColSpan properties of the TablixCells within a ...
  15. The {0} '{1}' has an invalid TablixCell. The {2} of the TablixCell is invalid. The TablixCell cannot span columns under TablixMembers ...
  16. The {0} '{1}' has an invalid TablixHeader. The {2} of the TablixHeader is invalid. The TablixHeader can only span one column. ...
  17. The {0} '{1}' has an invalid TablixHeader. The {2} of the TablixHeader is invalid. The TablixHeader can only span one row. ...
  18. The {0} '{1}' has an invalid TablixMember. The child TablixMember with Group name '{2}' is not a dynamic TablixMember and ...
  19. The {0} '{1}' has an invalid {2}. A {2} that is dynamic (i.e., has a Group specified) or has dynamic descendants must have ...
  20. The {0} '{1}' has an invalid {2}. The CellContents for this {2} must be omitted because it is covered by a span from another ...
  21. The {0} '{1}' has an invalid {2}. The {2} has an invalid {3}, '{4}'. Child {2} elements of Static {2} elements must be Dynamic ...
  22. The {0} '{1}' has an invalid {2}. The {2} has an invalid {3}, '{4}'. Non-Static {3} elements must contain at least 1 {5}. ...
  23. The {0} '{1}' has an invalid {2}. The {2} must have the same value set for the {3} property as those following or preceding ...
  24. The {0} '{1}' has an {2} with an invalid {3}. The {3} can be an integer between -90 an 90, inclusive, or the values 'RightAngle' ...
  25. The {0} '{1}' is bound to a data source using the {2} data extension. The data extension returned an invalid database collation ...
  26. The {0} 2.0 and {0} 3.5 compilers are no longer supported. Templates will always be compiled with the version 4 compiler ...
  27. The {0} and {1} Work Item fields were filtered out of the available columns list because there are user defined columns already ...
  28. The {0} connection string appears to contain sensitive data (for example, a password), which is required to connect to the ...
  29. The {0} control '{1}' does not have a naming container. Ensure that the control is added to the page before calling DataBind. ...
  30. The {0} definitions in the signature and implementation are not compatible because a CLI type representation is being hidden ...
  31. The {0} definitions in the signature and implementation are not compatible because a type representation is being hidden ...
  32. The {0} definitions in the signature and implementation are not compatible because an abbreviation is being hidden by a signature. ...
  33. The {0} definitions in the signature and implementation are not compatible because the abbreviations differ: {1} versus {2} ...
  34. The {0} definitions in the signature and implementation are not compatible because the abstract member '{1}' was present ...
  35. The {0} definitions in the signature and implementation are not compatible because the abstract member '{1}' was required ...
  36. The {0} definitions in the signature and implementation are not compatible because the accessibility specified in the signature ...
  37. The {0} definitions in the signature and implementation are not compatible because the field {1} was present in the implementation ...
  38. The {0} definitions in the signature and implementation are not compatible because the field {1} was present in the implementation ...
  39. The {0} definitions in the signature and implementation are not compatible because the field {1} was required by the signature ...
  40. The {0} definitions in the signature and implementation are not compatible because the implementation defines a struct but ...
  41. The {0} definitions in the signature and implementation are not compatible because the implementation defines the {1} '{2}' ...
  42. The {0} definitions in the signature and implementation are not compatible because the implementation is an abstract class ...
  43. The {0} definitions in the signature and implementation are not compatible because the implementation says this type may ...
  44. The {0} definitions in the signature and implementation are not compatible because the implementation says this type may ...
  45. The {0} definitions in the signature and implementation are not compatible because the implementation type is not sealed ...
  46. The {0} definitions in the signature and implementation are not compatible because the implementation type is sealed but ...
  47. The {0} definitions in the signature and implementation are not compatible because the order of the fields is different in ...
  48. The {0} definitions in the signature and implementation are not compatible because the respective type parameter counts differ ...
  49. The {0} definitions in the signature and implementation are not compatible because the signature declares a {1} while the ...
  50. The {0} definitions in the signature and implementation are not compatible because the signature defines the {1} '{2}' but ...
  51. The {0} definitions in the signature and implementation are not compatible because the signature has an abbreviation while ...
  52. The {0} definitions in the signature and implementation are not compatible because the signature is an abstract class but ...
  53. The {0} definitions in the signature and implementation are not compatible because the signature requires that the type supports ...
  54. The {0} definitions in the signature and implementation are not compatible because the signature says this type may use nulls ...
  55. The {0} definitions in the signature and implementation are not compatible because the signature says this type may use nulls ...
  56. The {0} name '{1}' contains invalid characters. The name cannot: - contain any of the following characters: / ? : \ " < > ...
  57. The {0} {1}' contains a definition for the {2} {3}'. This field is missing from the returned result set from the data source. ...
  58. The {0} {1}' contains a definition for the {2} {3}({4})'. The data extension returned an error during reading the field property. ...
  59. The {0} {1}' contains a different number of ChartSeries elements than the number of StaticSeries elements. If the {0} contains ...
  60. The {0} {1}' contains a different number of DataPoints per ChartSeries element than the number of StaticCategory elements. ...
  61. The {0} {1}' contains a wrong number of DataCells per DataRow element. {2} DataCells per DataRow element are expected, because ...
  62. The {0} {1}' contains a wrong number of DataRow elements. {2} DataRow elements are expected, because there must be as many ...
  63. The {0} {1}' contains a {2} grouping level with both of the following: static and non-static groups. Multiple groups on the ...
  64. The {0} {1}' contains at least one PlotType setting, which is different from the default setting "Auto". The PlotType will ...
  65. The {0} {1}' has a CategoryGrouping with both or neither of the following: DynamicCategories and StaticCategories. CategoryGrouping ...
  66. The {0} {1}' has a ChartData element that contains a collection of {3} DataPoint element(s), which is different from the ...
  67. The {0} {1}' has a ColumnGrouping with both or neither of the following: DynamicColumns and StaticColumns. ColumnGrouping ...
  68. The {0} {1}' has a RepeatWith property. Data regions, subreports, and rectangles that contain a data region or subreport ...
  69. The {0} {1}' has a RowGrouping with both or neither of the following: DynamicRows and StaticRows. RowGrouping must have exactly ...
  70. The {0} {1}' has a SeriesGrouping with both or neither of the following: DynamicSeries and StaticSeries. A SeriesGrouping ...
  71. The {0} {1}' has a {2} using aggregates without explicit scopes and the {3} is omitted. Aggregates without an explicit scope ...
  72. The {0} {1}' has an Action that has more than one of the following: Hyperlink, BookmarkLink or Drillthrough. Action must ...
  73. The {0} {1}' has an incorrect number of {2}. The number of {2} must equal the number of innermost TablixMembers (TablixMembers ...
  74. The {0} {1}' has an incorrect number of {2}. The number of {2} must equal the number of levels in the TablixColumnHierarchy ...
  75. The {0} {1}' has an incorrect number of {2}. The number of {2} within TablixCornerRow at index: {3} must equal the number ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)