/Release/Silverlight3/Infrastructure/TestFramework/Properties/UnitTestMessage.resx

# · MSBuild · 214 lines · 155 code · 0 blank · 59 comment · 0 complexity · 8582104ec915fc356c19f2d8f756dd5b MD5 · raw file

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <root>
  3. <!--
  4. Microsoft ResX Schema
  5. Version 2.0
  6. The primary goals of this format is to allow a simple XML format
  7. that is mostly human readable. The generation and parsing of the
  8. various data types are done through the TypeConverter classes
  9. associated with the data types.
  10. Example:
  11. ... ado.net/XML headers & schema ...
  12. <resheader name="resmimetype">text/microsoft-resx</resheader>
  13. <resheader name="version">2.0</resheader>
  14. <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
  15. <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
  16. <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
  17. <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
  18. <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
  19. <value>[base64 mime encoded serialized .NET Framework object]</value>
  20. </data>
  21. <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
  22. <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
  23. <comment>This is a comment</comment>
  24. </data>
  25. There are any number of "resheader" rows that contain simple
  26. name/value pairs.
  27. Each data row contains a name, and value. The row also contains a
  28. type or mimetype. Type corresponds to a .NET class that support
  29. text/value conversion through the TypeConverter architecture.
  30. Classes that don't support this are serialized and stored with the
  31. mimetype set.
  32. The mimetype is used for serialized objects, and tells the
  33. ResXResourceReader how to depersist the object. This is currently not
  34. extensible. For a given mimetype the value must be set accordingly:
  35. Note - application/x-microsoft.net.object.binary.base64 is the format
  36. that the ResXResourceWriter will generate, however the reader can
  37. read any of the formats listed below.
  38. mimetype: application/x-microsoft.net.object.binary.base64
  39. value : The object must be serialized with
  40. : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
  41. : and then encoded with base64 encoding.
  42. mimetype: application/x-microsoft.net.object.soap.base64
  43. value : The object must be serialized with
  44. : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
  45. : and then encoded with base64 encoding.
  46. mimetype: application/x-microsoft.net.object.bytearray.base64
  47. value : The object must be serialized into a byte array
  48. : using a System.ComponentModel.TypeConverter
  49. : and then encoded with base64 encoding.
  50. -->
  51. <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
  52. <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
  53. <xsd:element name="root" msdata:IsDataSet="true">
  54. <xsd:complexType>
  55. <xsd:choice maxOccurs="unbounded">
  56. <xsd:element name="metadata">
  57. <xsd:complexType>
  58. <xsd:sequence>
  59. <xsd:element name="value" type="xsd:string" minOccurs="0" />
  60. </xsd:sequence>
  61. <xsd:attribute name="name" use="required" type="xsd:string" />
  62. <xsd:attribute name="type" type="xsd:string" />
  63. <xsd:attribute name="mimetype" type="xsd:string" />
  64. <xsd:attribute ref="xml:space" />
  65. </xsd:complexType>
  66. </xsd:element>
  67. <xsd:element name="assembly">
  68. <xsd:complexType>
  69. <xsd:attribute name="alias" type="xsd:string" />
  70. <xsd:attribute name="name" type="xsd:string" />
  71. </xsd:complexType>
  72. </xsd:element>
  73. <xsd:element name="data">
  74. <xsd:complexType>
  75. <xsd:sequence>
  76. <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
  77. <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
  78. </xsd:sequence>
  79. <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
  80. <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
  81. <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
  82. <xsd:attribute ref="xml:space" />
  83. </xsd:complexType>
  84. </xsd:element>
  85. <xsd:element name="resheader">
  86. <xsd:complexType>
  87. <xsd:sequence>
  88. <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
  89. </xsd:sequence>
  90. <xsd:attribute name="name" type="xsd:string" use="required" />
  91. </xsd:complexType>
  92. </xsd:element>
  93. </xsd:choice>
  94. </xsd:complexType>
  95. </xsd:element>
  96. </xsd:schema>
  97. <resheader name="resmimetype">
  98. <value>text/microsoft-resx</value>
  99. </resheader>
  100. <resheader name="version">
  101. <value>2.0</value>
  102. </resheader>
  103. <resheader name="reader">
  104. <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  105. </resheader>
  106. <resheader name="writer">
  107. <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  108. </resheader>
  109. <data name="CompositeWorkItem_Invoke_NoRemainingWorkItems" xml:space="preserve">
  110. <value>There are no remaining test work items</value>
  111. <comment>Happens if the work item queue is expected to be non-empty.</comment>
  112. </data>
  113. <data name="LogException" xml:space="preserve">
  114. <value>Exception: Type "{0}" Message "{1}"</value>
  115. <comment>Exception log text.</comment>
  116. </data>
  117. <data name="LogIgnore" xml:space="preserve">
  118. <value>Ignoring "{0}"</value>
  119. <comment>Ignore log text.</comment>
  120. </data>
  121. <data name="LogIncorrectExceptionType" xml:space="preserve">
  122. <value>Incorrect exception type "{0}" received. Was expecting a "{1}" type.</value>
  123. <comment>Incorrect exception log text. {0} = the type received, {1} = the type expected.</comment>
  124. </data>
  125. <data name="LogNoException" xml:space="preserve">
  126. <value>No Exception was observed. Was expecting a "{0}" type exception.</value>
  127. <comment>No exception observed. {0} = the type expected.</comment>
  128. </data>
  129. <data name="TagAttribute_ctor_EmptyTag" xml:space="preserve">
  130. <value>Tag cannot be empty!</value>
  131. <comment>A TagAttribute's Tag property cannot be empty.</comment>
  132. </data>
  133. <data name="TagAttribute_ctor_ReservedCharacter" xml:space="preserve">
  134. <value>The tag "{0}" contains the invalid character "{1}"!</value>
  135. <comment>{0} = the tag, {1} = the invalid character used in the tag</comment>
  136. </data>
  137. <data name="TagAttribute_ctor_ReservedTag" xml:space="preserve">
  138. <value>Tag "{0}" is reserved!</value>
  139. <comment>{0} = the tag</comment>
  140. </data>
  141. <data name="TagManager_ExpressionEvaluator_EmptyTagExpression" xml:space="preserve">
  142. <value>tagExpression cannot be empty!</value>
  143. <comment>A tag expression cannot be empty.</comment>
  144. </data>
  145. <data name="TagManager_ExpressionEvaluator_ExpectedEndOfTagExpression" xml:space="preserve">
  146. <value>Expected end of tag expression "{0}" at position {1}!</value>
  147. <comment>{0} = the tag expression, {1} = the position</comment>
  148. </data>
  149. <data name="TagManager_ExpressionEvaluator_ExpectedTag" xml:space="preserve">
  150. <value>Tag expected in expression "{0}" at position {1}!</value>
  151. <comment>{0} = the tag, {1} = the position</comment>
  152. </data>
  153. <data name="TagManager_ExpressionEvaluator_InvalidTagExpression" xml:space="preserve">
  154. <value>Invalid tag expression "{0}" (expected "{1}" at position {2})!</value>
  155. <comment>{0} = the invalid expression, {1} = the expected, {2} = the position</comment>
  156. </data>
  157. <data name="TagTestRunFilter_TaggingInUse" xml:space="preserve">
  158. <value>Tag expression "{0}" is in use.</value>
  159. <comment>A message that tag expressions are in use. {0} = tag expression</comment>
  160. </data>
  161. <data name="TestClassHelper_ExclusiveClassesInUse" xml:space="preserve">
  162. <value>Exclusive classes are in use</value>
  163. <comment>A message that exclusive classes are in use.</comment>
  164. </data>
  165. <data name="TestMethodHelper_ExclusiveMethodsInUse" xml:space="preserve">
  166. <value>Exclusive methods are in use</value>
  167. <comment>A message that exclusive methods are in use.</comment>
  168. </data>
  169. <data name="TestMethodManager_CompleteMethod_UnVerifiedBug" xml:space="preserve">
  170. <value>The known issue could not be verified. A failure will be recorded. If this bug has been fixed, please mark the Fixed attribute value to True.</value>
  171. <comment>When a known issue and its result are mismatched.</comment>
  172. </data>
  173. <data name="UnitTestCompositeWorkItem_ctor_NoTestHarness" xml:space="preserve">
  174. <value>No TestHarness is available.</value>
  175. <comment>A message that no TestHarness instance is present.</comment>
  176. </data>
  177. <data name="UnitTestContext_FeatureNotSupported" xml:space="preserve">
  178. <value>The "{0}" functionality is not supported within this unit test system.</value>
  179. <comment>Message that a feature is not supported. {0} = a string representation of the feature.</comment>
  180. </data>
  181. <data name="UnitTestHarness_Initialize_UnitTestHarnessInitialize" xml:space="preserve">
  182. <value>Initialization of UnitTestHarness</value>
  183. <comment>Log message for unit test harness initialization</comment>
  184. </data>
  185. <data name="UnitTestHarness_RunNextStep_NoCompositeWorkItemsExist" xml:space="preserve">
  186. <value>No composite work items exist to be cleared.</value>
  187. <comment>A message that no work items exist.</comment>
  188. </data>
  189. <data name="UnitTestHarness_TestAssembliesNotActionable" xml:space="preserve">
  190. <value>No test classes were selected to be in the test run.</value>
  191. <comment>Either
  192. - unit test provider found no tests
  193. - no test classes</comment>
  194. </data>
  195. <data name="UnitTestSystem_Run_NoTestHarnessInSettings" xml:space="preserve">
  196. <value>Test harness was not specified on test harness settings object. If a test harness settings object was passed in, please verify that it contains a reference to a test harness.</value>
  197. <comment>No test harness was instantiated and provided in the test settings.</comment>
  198. </data>
  199. <data name="WorkItemTest_EnqueueWorkItem_AsynchronousFeatureUnavailable" xml:space="preserve">
  200. <value>Test bug: A test cannot use Test Task objects, such as callbacks and conditionals, or the PumpMessages feature, unless marked with the [Asynchronous] attribute.</value>
  201. <comment>When a test author attempts to use task callback features when they are not permitted.</comment>
  202. </data>
  203. </root>