<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
  <file datatype="xml" source-language="en" target-language="zh-Hans" original="../ExtensionResources.resx">
    <body>
      <trans-unit id="ActivationArgumentsInvalidArgumentCount">
        <source>The Microsoft Testing Platform activation-argument payload has an invalid argument count.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload has an invalid argument count.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsInvalidArgumentLength">
        <source>The Microsoft Testing Platform activation-argument payload has an invalid argument length.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload has an invalid argument length.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsInvalidFileKey">
        <source>The Microsoft Testing Platform activation arguments contain an invalid file payload key.</source>
        <target state="new">The Microsoft Testing Platform activation arguments contain an invalid file payload key.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsInvalidFileReference">
        <source>The Microsoft Testing Platform activation arguments contain an invalid file payload reference.</source>
        <target state="new">The Microsoft Testing Platform activation arguments contain an invalid file payload reference.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsInvalidInlinePayload">
        <source>The Microsoft Testing Platform activation arguments contain an invalid inline payload.</source>
        <target state="new">The Microsoft Testing Platform activation arguments contain an invalid inline payload.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsMissingPayload">
        <source>The launch activation does not contain Microsoft Testing Platform arguments.</source>
        <target state="new">The launch activation does not contain Microsoft Testing Platform arguments.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsPayloadAuthenticationFailed">
        <source>The Microsoft Testing Platform activation-argument payload failed authentication.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload failed authentication.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsPayloadReadFailed">
        <source>The Microsoft Testing Platform activation-argument payload could not be read.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload could not be read.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsPayloadTooLarge">
        <source>The Microsoft Testing Platform activation-argument payload is too large.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload is too large.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsPayloadTruncated">
        <source>The Microsoft Testing Platform activation-argument payload is truncated.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload is truncated.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsTrailingData">
        <source>The Microsoft Testing Platform activation-argument payload contains trailing data.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload contains trailing data.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="AmbiguousAppxManifestApplication">
        <source>The packaged app manifest declares multiple applications and none uniquely matches the executable '{0}'. Candidate Application User Model IDs: {1}.</source>
        <target state="translated">打包应用部件清单声明了多个应用程序，而没有一个与可执行文件 '{0}' 唯一匹配。候选应用程序用户模型 ID: {1}。</target>
        <note />
      </trans-unit>
      <trans-unit id="AppxManifestApplicationExecutableMismatch">
        <source>The packaged app manifest declares no application for the executable '{0}', so it describes a different application and activating it would target the wrong Application User Model ID. Declared application executables: {1}.</source>
        <target state="translated">打包的应用清单未为可执行文件“{0}”声明任何应用程序，因此它描述的是另一个应用程序，激活它将针对错误的 Application User Model ID。已声明的应用程序可执行文件: {1}。</target>
        <note>Do not localize the technology name {Locked="Application User Model ID"}. {0} is an executable path. {1} is a comma-separated list of executable paths.</note>
      </trans-unit>
      <trans-unit id="InvalidAppxManifestMissingIdentity">
        <source>The packaged app manifest does not declare a valid &lt;Identity Name="..." Publisher="..." /&gt; element.</source>
        <target state="translated">打包应用部件清单未声明有效的 &lt;Identity Name="..." Publisher="..." /&gt; 元素。</target>
        <note />
      </trans-unit>
      <trans-unit id="PackagedAppExtensionDescription">
        <source>Registers a packaged MSIX test host and activates it by Application User Model ID (Windows build), delivering Microsoft Testing Platform arguments through argv for packagedClassicApp/win32App hosts (including classic AppContainer hosts) or launch activation for windowsApp/UWP hosts. When opted in through TESTINGPLATFORM_PACKAGEDAPP_LAUNCHER=always, it also deploys a non-packaged (loose-layout) Windows test host to an isolated directory and launches it from there. Enabled only for a packaged layout by default, so an unpackaged app is left on the default launch path. End-to-end AppContainer execution additionally requires controller-pipe authorization. See https://github.com/microsoft/testfx/issues/10486.</source>
        <target state="needs-review-translation">注册已打包的完全信任 MSIX 桌面测试主机，并通过 Application User Model ID 激活它(Windows 版本)，并且(当通过 TESTINGPLATFORM_PACKAGEDAPP_LAUNCHER=always 选择加入时)将非打包(松散布局) Windows 测试主机部署到隔离目录并从该目录启动它。默认情况下仅对打包布局启用，因此未打包的应用保留在默认启动路径上。不支持真正的 UWP/AppContainer 主机。请参阅 https://github.com/microsoft/testfx/issues/9933。</target>
        <note>Do not localize the environment variable name or its value {Locked="TESTINGPLATFORM_PACKAGEDAPP_LAUNCHER"}{Locked="always"}, nor the technology names {Locked="Microsoft Testing Platform"}{Locked="MSIX"}{Locked="Application User Model ID"}{Locked="Windows"}{Locked="packagedClassicApp"}{Locked="win32App"}{Locked="windowsApp"}{Locked="UWP"}{Locked="AppContainer"}.</note>
      </trans-unit>
      <trans-unit id="PackagedAppExtensionDisplayName">
        <source>Packaged app test host launcher</source>
        <target state="translated">打包应用测试主机启动器</target>
        <note />
      </trans-unit>
      <trans-unit id="PackagedAppLaunchNotSupported">
        <source>Cannot launch the packaged Windows app '{0}' (found '{1}'). Registering and activating a packaged (MSIX) app requires the Windows build of this extension, which ships for net8.0-windows10.0.19041.0 and later. Target 'net8.0-windows10.0.19041.0' (or a later net*-windows Target Framework Moniker at platform version 10.0.19041.0 or higher) so NuGet selects that asset. The current build only launches non-packaged (loose-layout) test hosts. See https://github.com/microsoft/testfx/issues/9933.</source>
        <target state="translated">无法启动打包的 Windows 应用“{0}”(找到了“{1}”)。注册和激活打包(MSIX)应用需要此扩展的 Windows 版本，该版本随 net8.0-windows10.0.19041.0 及更高版本提供。目标为 "net8.0-windows10.0.19041.0"(或在平台版本 10.0.19041.0 或更高版本上，为更高 net*-windows 目标框架名字对象)，以便 NuGet 选择该资产。当前版本仅启动非打包(松散布局)测试主机。请参阅 https://github.com/microsoft/testfx/issues/9933。</target>
        <note />
      </trans-unit>
      <trans-unit id="PackagedAppNoApplicationToActivate">
        <source>Cannot activate the packaged Windows app '{0}' (found '{1}'): its manifest declares no &lt;Application&gt;, so there is no Application User Model ID to activate.</source>
        <target state="translated">无法激活打包的 Windows 应用“{0}”(找到了“{1}”)：其清单未声明 &lt;Application&gt;，因此没有要激活的应用程序用户模型 ID。</target>
        <note />
      </trans-unit>
      <trans-unit id="PackagedAppRegistrationFailed">
        <source>Failed to register the packaged Windows app layout '{0}'. Registering an unsigned build-output layout requires Developer Mode (or sideloading) to be enabled. Error: {1}</source>
        <target state="translated">注册打包的 Windows 应用布局“{0}”失败。要注册未签名的生成输出布局，需要启用开发人员模式(或旁加载)。错误: {1}</target>
        <note />
      </trans-unit>
    </body>
  </file>
</xliff>