xamarin-macios/msbuild/Xamarin.Localization.MSBuild/MSBStrings.resx

1432 строки
49 KiB
Plaintext
Исходник Обычный вид История

2020-03-14 00:46:28 +03:00
<?xml version="1.0" encoding="utf-8"?>
<root>
<resheader name="resmimetype">
<value>text/microsoft-resx</value>
</resheader>
<resheader name="version">
<value>2.0</value>
</resheader>
<resheader name="reader">
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<resheader name="writer">
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<data name="M0001" xml:space="preserve">
<value>Tool {0} execution started with arguments: {1}
</value>
</data>
<data name="M0002" xml:space="preserve">
<value>Tool {0} execution finished (exit code = {1}).
</value>
</data>
<data name="E0003" xml:space="preserve">
<value>Error executing tool '{0}': {1}
</value>
</data>
<data name="E0004" xml:space="preserve">
<value>Failed to codesign '{0}': {1}
</value>
</data>
<data name="E0005" xml:space="preserve">
<value>Failed to codesign '{0}'
</value>
</data>
<data name="E0006" xml:space="preserve">
<value> '{0}' not found.
</value>
</data>
<data name="E0007" xml:space="preserve">
<value>Error loading '{0}': Unknown image format.
</value>
</data>
<data name="E0008" xml:space="preserve">
<value>Invalid iTunesArtwork dimensions ({0}x{1}) for '{2}'.
</value>
</data>
<data name="E0009" xml:space="preserve">
<value>Multiple iTunesArtwork files with the same dimensions detected ({0}x{1}) for '{2}'.
</value>
</data>
<data name="E0010" xml:space="preserve">
<value>Error loading '{0}': {1}
</value>
</data>
<data name="E0011" xml:space="preserve">
<value>Could not parse MinimumOSVersion value '{0}'
</value>
</data>
<data name="E0012" xml:space="preserve">
<value>Could not parse TargetArchitectures '{0}'
</value>
</data>
<data name="E0013" xml:space="preserve">
<value>The {0} SDK for '{1}' is not installed.
</value>
</data>
<data name="E0014" xml:space="preserve">
<value>The executable (CFBundleExecutable) name ({0}) cannot end with '.app', because iOS may fail to launch the app.
</value>
</data>
<data name="W0016" xml:space="preserve">
<value>Can only fake the watchOS 4.3 SDK when building for watchOS.
</value>
</data>
<data name="M0017" xml:space="preserve">
<value>All http loads are already allowed.
</value>
</data>
<data name="M0018" xml:space="preserve">
<value>Allowed arbitrary HTTP loads to support debugging.
</value>
</data>
<data name="W0019" xml:space="preserve">
<value>Supported iPhone orientations have not been set
</value>
</data>
<data name="W0020" xml:space="preserve">
<value>Supported iPhone orientations are not matched pairs
</value>
<comment>The iPhone orientation settings do not match iPad, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="W0021" xml:space="preserve">
<value>Supported iPad orientations have not been set
</value>
</data>
<data name="W0022" xml:space="preserve">
<value>Supported iPad orientations are not matched pairs
</value>
<comment>The iPad orientation settings do not match iPhone, see: https://xamarin.github.io/bugzilla-archives/85/850/bug.html</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E0023" xml:space="preserve">
<value>Cannot have more than 1 iTunesMetadata.plist.
</value>
</data>
<data name="E0024" xml:space="preserve">
<value>Error loading Settings plist file '{0}/Settings.bundle/Root.plist': {1}.
</value>
</data>
<data name="E0025" xml:space="preserve">
<value>Could not parse the SDK version '{0}'
</value>
</data>
<!-- E0026: not used anymore -->
<!-- E0027: not used anymore -->
<!-- E0028: not used anymore -->
<!-- E0029: not used anymore -->
<!-- E0030: not used anymore -->
<!-- E0031: not used anymore -->
2020-03-14 00:46:28 +03:00
<data name="E0032" xml:space="preserve">
<value>Could not locate SDK bin directory
</value>
</data>
<!-- E0033: not used anymore -->
<!-- E0034: not used anymore -->
<!-- E0035: not used anymore -->
<!-- E0036: not used anymore -->
<!-- E0037: not used anymore -->
<!-- E0038: not used anymore -->
<!-- E0039: not used anymore -->
<!-- E0040: not used anymore -->
<!-- E0041: not used anymore -->
<!-- E0042: not used anymore -->
<!-- E0043: not used anymore -->
2020-03-14 00:46:28 +03:00
<data name="E0044" xml:space="preserve">
<value>Could not find a valid Xcode app bundle at '{0}'. Please update your Apple SDK location in Visual Studio's preferences {1}.
</value>
<comment>The following are literal names and should not be translated: Xcode, Apple SDK, Visual Studio
{0} - The selected Xcode / Apple SDK directory.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E0045" xml:space="preserve">
<value>Could not find valid a usable Xcode developer path
</value>
</data>
<data name="E0046" xml:space="preserve">
<value>Could not find '{0}'
2020-03-14 00:46:28 +03:00
</value>
</data>
<data name="M0047" xml:space="preserve">
<value>Searching for '{0}' in '{1}'
</value>
</data>
<data name="E0048" xml:space="preserve">
<value>Unknown SDK platform: {0}
</value>
</data>
<data name="E0049" xml:space="preserve">
<value>Could not locate the provisioning profile with a Name or UUID of {0}.
</value>
</data>
<data name="E0050" xml:space="preserve">
<value>Unknown search option: {0}
</value>
</data>
<data name="W0051" xml:space="preserve">
<value>Unknown native reference type for '{0}'.
</value>
</data>
<data name="W0052" xml:space="preserve">
<value>Dynamic native references are not supported: '{0}'
</value>
</data>
<data name="E0053" xml:space="preserve">
<value>Target architecture ARMv6 is no longer supported in Xamarin.iOS. Please select a supported architecture.
</value>
</data>
<data name="W0054" xml:space="preserve">
<value>Failed to create response file '{0}': {1}
</value>
</data>
<data name="E0055" xml:space="preserve">
<value>Could not load Info.plist: {0}
</value>
</data>
<data name="E0057" xml:space="preserve">
<value>Invalid architectures: '{0}'.
</value>
</data>
<data name="E0058" xml:space="preserve">
<value>Failed to parse the target device information.
</value>
</data>
<data name="E0059" xml:space="preserve">
<value>No target device found.
</value>
</data>
<data name="E0060" xml:space="preserve">
<value>No device architecture information found.
</value>
</data>
<data name="E0061" xml:space="preserve">
<value>Invalid target architecture: '{0}'
</value>
</data>
<data name="E0062" xml:space="preserve">
<value>No device operating system information found.
</value>
</data>
<data name="E0063" xml:space="preserve">
<value>No device model information found.
</value>
</data>
<data name="E0064" xml:space="preserve">
<value>No iOS version information found.
</value>
</data>
<data name="E0065" xml:space="preserve">
<value>Resources rules file '{0}' not found.
</value>
</data>
<data name="E0066" xml:space="preserve">
<value>Failed to parse SdkVersion '{0}'.
</value>
</data>
<data name="E0067" xml:space="preserve">
<value>Xcode 10 does not support watchOS 1 apps. Either upgrade to watchOS 2 apps, or use an older version of Xcode.</value>
</data>
<data name="E0068" xml:space="preserve">
<value>An installation of Xcode >= 6.2 is required to build WatchKit applications.
</value>
</data>
<data name="E0069" xml:space="preserve">
<value>iOS {0} does not support WatchKit.
</value>
</data>
<data name="E0070" xml:space="preserve">
<value>Failed to locate the WatchKit launcher in the Xcode app bundle.
</value>
</data>
<data name="W0071" xml:space="preserve">
<value>The App Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2})
</value>
</data>
<data name="W0072" xml:space="preserve">
<value>The App Extension '{0}' does not specify a CFBundleVersion
</value>
</data>
<data name="W0073" xml:space="preserve">
<value>The App Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2})
</value>
</data>
<data name="W0074" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The App Extension '{0}' has an unrecognized NSExtensionPointIdentifier value ('{1}').
</value>
</data>
<data name="W0075" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not specify a CFBundleShortVersionString
</value>
</data>
<data name="W0076" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2})
</value>
</data>
<data name="W0077" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not specify a CFBundleVersion
</value>
</data>
<data name="W0078" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2})
</value>
</data>
<data name="W0079" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' does not specify a CFBundleShortVersionString)
</value>
</data>
<data name="W0080" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has a CFBundleShortVersionString ({1}) that does not match the main app bundle's CFBundleShortVersionString ({2})
</value>
</data>
<data name="W0081" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' does not specify a CFBundleVersion
</value>
</data>
<data name="W0082" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has a CFBundleVersion ({1}) that does not match the main app bundle's CFBundleVersion ({2})
</value>
</data>
<!-- E0083: not used anymore -->
<data name="E0084" xml:space="preserve">
<value>Could not locate the {0} '{1}' SDK at path '{}'
2020-03-14 00:46:28 +03:00
</value>
</data>
<data name="E0085" xml:space="preserve">
<value>Could not locate the {0} '{1}' SDK usr path at '{2}'
2020-03-14 00:46:28 +03:00
</value>
<comment>The provided SDK path is missing a 'usr' directory. The following are literal names and should not be translated: SDK, usr
{0} - The platform name, such as 'iOS'.
{1} - The version number of the SDK.
{2} - The file path of the SDK.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E0086" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Could not find a valid Xcode developer path
</value>
</data>
<!-- E0087: not used anymore -->
<!-- E0088: not used anymore -->
<data name="E0089" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Unrecognized platform: {0}
</value>
</data>
<data name="W0090" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Asset not part of an asset catalog: {0}
</value>
</data>
<data name="E0091" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>File not found: {0}
</value>
</data>
<data name="E0092" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Invalid json: {0}
</value>
</data>
<data name="E0093" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Partial Info.plist file was not generated: {0}
</value>
</data>
<data name="E0094" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Failed to load {0} log file `{1}`: {2}
</value>
<comment>A general failure message if a log file wasn't able to be loaded.
{0} - The command-line tool that generated the log.
{1} - The file path to the log.
{2} - Further detail about the failure.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="W0095" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Failed to parse altool output: {0}.
Output: {1}
2020-03-14 00:46:28 +03:00
</value>
</data>
<!-- E0096: not used anymore -->
<data name="E0097" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>No API definition file specified.
</value>
</data>
<data name="E0098" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} failed.
</value>
<comment>A general error message that a command-line tool failed.
{0} - The file path to the command-line tool.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E0099" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value> Bundle Resource '{0}' not found on disk (should be at '{1}')
</value>
</data>
<data name="E0100" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The path '{0}' would result in a file outside of the app bundle and cannot be used.
</value>
</data>
<data name="E0101" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Info.plist files should have a Build Action of 'None'.
</value>
</data>
<data name="E0102" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The name '{0}' is reserved and cannot be used.
</value>
</data>
<data name="W0103" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Found a directory within the Frameworks directory which is not a framework: {0}
</value>
</data>
<data name="W0104" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The framework {0} does not contain a binary named {1}
</value>
</data>
<data name="M0105" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>No Frameworks directory found.
</value>
</data>
<data name="W0106" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Could not determine value for manifest key '{0}'
</value>
</data>
<data name="E0107" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Error loading partial Info.plist template file '{0}': {1}
</value>
</data>
<data name="W0108" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Cannot expand $(TeamIdentifierPrefix) in Entitlements.plist without a provisioning profile.
</value>
</data>
<data name="W0109" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Cannot expand $(AppIdentifierPrefix) in Entitlements.plist without a provisioning profile.
</value>
</data>
<data name="W0110" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>iCloud entitlements such as '{0}' require a Provisioning Profile.
</value>
</data>
<data name="W0111" xml:space="preserve">
<value>The iCloud entitlement '{0}' is not supported by the Provisioning Profile.
2020-03-14 00:46:28 +03:00
</value>
</data>
<data name="E0112" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Entitlements.plist template '{0}' not found.
</value>
</data>
<data name="E0113" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Error loading Entitlements.plist template '{0}': {1}
</value>
</data>
<data name="E0114" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Error writing xcent file '{0}': {1}
</value>
</data>
<data name="E0115" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Error writing archived-expanded-entitlements.xcent file: {0}
</value>
</data>
<data name="M0116" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Tool {0} execution finished.
</value>
</data>
<data name="E0117" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} exited with code {1}
</value>
</data>
<data name="E0118" xml:space="preserve">
<value>{0} exited with code {1}:
{2}</value>
</data>
<data name="M0119" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Skipping `{0}' as the output file, `{1}', is newer.
</value>
<comment>Skipping a build operation, since the destination file is newer than the source file.
{0} - The destination file.
{1} - The source file.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E0120" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Error saving `{0}': {1}
</value>
</data>
<data name="M0121" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Creating binding resource package: {0}
</value>
</data>
<data name="E0122" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Error loading '{0}'
</value>
</data>
<data name="E0123" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Package creation failed. Could not parse extra arguments.
</value>
</data>
<data name="E0124" xml:space="preserve">
<value>The identity '{0}' doesn't match any valid certificate/private key pair in the default keychain.
2020-03-14 00:46:28 +03:00
</value>
<comment>A failure to sign the iOS application, due to a missing certificate/private key. Xcode has an identical error message, see: https://developer.apple.com/library/archive/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933-CH1-TNTAG40-WHAT_DOES__VALID_SIGNING_IDENTITY_NOT_FOUND__MEAN_AND_HOW_DO_I_RESOLVE_IT_
{0} - The name of the identity, such as 'iPhone Developer'.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="M0125" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Detected signing identity:
</value>
</data>
<data name="M0126" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The certificate '{0}' does not match any of the prefixes '{1}'.
</value>
</data>
<data name="M0127" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The certificate '{0}' has expired ({1})
</value>
</data>
<data name="E0128" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>No valid {0} code signing keys found in keychain. You need to request a codesigning certificate from https://developer.apple.com.
</value>
<comment>A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys
{0} - The platform name, such as 'iOS'.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="M0129" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The certificate '{0}' does not match '{1}'.
</value>
</data>
<data name="E0130" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} code signing key '{1}' not found in keychain.
</value>
<comment>A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys
{0} - The platform name, such as 'iOS'.
{1} - The name of the code signing key, such as 'Apple Development'.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E0131" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Could not find any available provisioning profiles for {0} on {1}.
</value>
<comment>A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys
{0} - The app bundle name, such as 'YouriOSApp.app'
{1} - The platform name, such as 'iOS'.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="M0132" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>'{0}' doesn't match '{1}'.
</value>
</data>
<data name="E0133" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>No installed provisioning profiles match the installed {0} {1} signing identities.
</value>
<comment>A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys
{0} - The platform name, such as 'iOS'.
{1} - The app bundle name, such as 'YouriOSApp.app'</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="M0134" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Finding matching provisioning profiles with compatible AppID, keeping only those with the longest matching (wildcard) IDs.
</value>
</data>
<data name="M0135" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>AppID: {0} was ruled out because we found a better match: {1}.
</value>
</data>
<data name="M0136" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>AppID: {0} was ruled out because we already found better matches: {1}.
</value>
</data>
<data name="W0137" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>No installed provisioning profiles match the bundle identifier.
</value>
</data>
<data name="M0138" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Multiple provisioning profiles match the bundle identifier; using the first match.
</value>
</data>
<data name="E0139" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} does not define CFBundleIdentifier
</value>
</data>
<data name="E0140" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The specified {0} provisioning profile '{1}' could not be found
</value>
<comment>A failure to sign the iOS application, due to missing code-signing credentials. See: https://docs.microsoft.com/xamarin/ios/troubleshooting/questions/no-codesigning-keys
{0} - The platform name, such as 'iOS'.
{1} - The provisioning profile ID. A string such as: 'f35b0040-2be5-4b1c-a1d6-59ae85047fad'</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E0141" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Project bundle identifier '{0}' does not match specified provisioning profile '{1}'
</value>
</data>
<data name="M0142" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Multiple signing identities match '{0}'; using the first match.
</value>
</data>
<data name="M0143" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Multiple signing identities found; using the first identity.
</value>
</data>
<data name="E0144" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The specified {0} provisioning profile '{1}' could not be found
</value>
</data>
<data name="E0145" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>No {0} signing identities match the specified provisioning profile '{1}'.
</value>
</data>
<data name="E0146" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'.
</value>
</data>
<data name="E0147" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Bundle identifier '{0}' does not match any installed provisioning profile for selected signing identity '{0}'.
</value>
</data>
<data name="E0148" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Bundle identifier '{0}' does not match any installed provisioning profile.
</value>
</data>
<data name="M0149" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value> {0} found at: {1}
</value>
<comment>A file was found at a location.
{0} - The '%(LogicalName)' of the file, or a relative path.
{1} - The location the file was found.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E0150" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value> AssemblyPath cannot be null or empty
</value>
</data>
<data name="M0151" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Generated bundle name: {0}
</value>
</data>
<data name="E0152" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>No property specified.
</value>
</data>
<data name="E0153" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The dictionary at '{0}' did not contain the key: {1}
</value>
</data>
<data name="E0154" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Could not parse array index: {0}
</value>
</data>
<data name="E0155" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Array index out of range for item '{0}'
</value>
</data>
<data name="E0156" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} values do not support child properties.
</value>
<comment>The type of value in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), such as a number or string cannot contain child values.
{0} - The value type, such as 'NSString'.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E0157" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Getting {0} values is not supported.
</value>
</data>
<data name="E0158" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The file '{0}' does not exist.
</value>
</data>
<data name="E0159" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The file '{0}' conflicts with '{1}'.
</value>
</data>
<data name="E0160" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Watch apps/extensions require Xcode 6.2 or later. The current Xcode version is {0}
</value>
</data>
<data name="E0161" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Items must have logical names computed.
</value>
</data>
<data name="M0162" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Duplicate Entry Was Skipped: {0}
</value>
</data>
<data name="M0163" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>File Doesn't Exist, Will Create: {0}
</value>
</data>
<data name="M0164" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Creating directory '{0}'
</value>
</data>
<data name="M0165" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Copying file from '{0}' to '{1}'
</value>
</data>
<data name="E0166" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>You must specify a DestinationFolder or the DestinationFiles, but not both.
</value>
</data>
<data name="E0167" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The number of DestinationFiles must match the number of SourceFiles.
</value>
</data>
<data name="M0168" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value> Skipping framework assembly: {0}
</value>
</data>
<data name="E0169" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Unknown target framework identifier: {0}.
</value>
</data>
<data name="E0170" xml:space="preserve">
<value>Could not find {0} in {1}.
</value>
</data>
<data name="E0171" xml:space="preserve">
<value>The {0} SDK is not installed.
</value>
</data>
<data name="E0172" xml:space="preserve">
<value>The {0} SDK version '{1}' is not installed, and no newer version was found.
</value>
</data>
<data name="E0173" xml:space="preserve">
<value>The {0} SDK version '{1}' is not installed. Using newer version '{2}' instead'.
</value>
</data>
<data name="E0174" xml:space="preserve">
<value>{0} has an incorrect or unknown format and cannot be processed.
</value>
</data>
<data name="E0175" xml:space="preserve">
<value>No matching framework found inside '{0}'.
</value>
</data>
[msbuild] Fix semi-conflicting options to set codesign timestamp (#10428) TL&DR: This effectively change nothing - but prevents (warn) if both options contradict themselves. Long Story.... So we have two ways to control the codesign's `--timetamp` option but they both ignore each other so we can end up with the option being set more than once at build time. `DisableTimestamp` was the original one. It was meant for iOS (and derivative OS) and disable the option (which requires the network) for simulator or debug builds. IOW we _wanted_ timestamps when doing release builds for devices. ``` DisableTimestamp="$(_CodesignDisableTimestamp)" ``` ``` <_CodesignDisableTimestamp>False</_CodesignDisableTimestamp> <_CodesignDisableTimestamp Condition="'$(_SdkIsSimulator)' == 'true' Or '$(_BundlerDebug)' == 'true'">True</_CodesignDisableTimestamp> ``` Now disabling the timestamp did not mean it was enabled. We did not ask for a timestamp, leaving it to the default which from `man codesign` means: > If this option is not given at all, a system-specific default behavior is invoked. > This may result in some but not all code signatures being timestamped. Then `UseSecureTimestamp` was added for macOS builds. If hardening is enabled then a secure timestamp is required. `msbuild/Xamarin.Mac.Tasks/Xamarin.Mac.Common.targets` `_CodesignAppBundle` ``` UseSecureTimestamp="$(UseHardenedRuntime)" ``` However it's also exposed for iOS (shared target) in `msbuild/Xamarin.Shared/Xamarin.Shared.targets` `__CodesignNativeLibraries` but it would always be `false` in that case. Adding this option means there's now always a `--timestamp` option given, either to enable it (no URL so it means using Apple's server) or to disable it (`=none`) but since it's controlled by `UseHardenedRuntime`, which is macOS only, then iOS device builds are never timestamped. An alternative would be to have `UseSecureTimestamp` as a macOS-only option - but that would change how we currently sign the iOS applications and I'd rather not change things that are known to work.
2021-01-15 18:43:11 +03:00
<data name="W0176" xml:space="preserve">
<value>Conflicting '{0}' and '{1}' options. '{1}' will be ignored.
</value>
</data>
[dotnet] Initial support for .NET6 from Windows (#10590) These changes add support for executing iOS and MacDev tasks remotely (on a Mac) when running a build from Windows, and creates a specific .NET6 pack for Windows that's only included in the MSI. For now this only enables builds for the iOS Simulator, physical devices are not yet supported. - Each task decides if it should run locally or remotely depending on the SessionId property, which will only have a value on Windows. - The XMA Build agent is now part of this repo and will be included in the iOS .NET6 Windows pack. - On this first version we're including some Windows specific tasks and references into the Xamarin.iOS.Tasks project for simplicity, but those will be moved to the Windows specific project. ------------ * [msbuild] Adds support for executing Xamarin.iOS tasks from Windows * [msbuild] Adds support for executing Xamarin.MacDev tasks from Windows * Added XMA Build Agent to Xamarin.MacDev.Tasks.sln * Fixes some MSBuild versioning problems * Makes the XMA Build agent load Xamarin.iOS tasks We need to load a type from the iOS tasks assembly so we can run the tasks requested by MSBuild from Windows. We only need to load Xamarin.iOS.Tasks.dll since MacDev.tasks is already embedded in that one. There's a little trick on the csproj, we can't directly use the Xamarin.iOS.Tasks project ref assemblies because that includes both Xamarin.iOS.Tasks.dll and Xamarin.MacDev.Tasks.dll, so the MacDev tasks will collide. We use the project ref only for build dependency purposes but we add an assembly reference to Xamarin.iOS.Tasks.dll. * Added Xamarin.iOS.Tasks.Windows project * Removed unnecessary references on Xamarin.iOS.Tasks.Windows.csproj * Adds Messaging assemblies when ILRepacking Xamarin Tasks The Xamarin Task assemblies now depend on Messaging, so we need the Messaging assemblies to be packed into Xamarin.Mac.Tasks and Xamarin.iOS.Tasks. Also had to remove the direct Messaging dependencies from the build agent since those are already contained in Xamarin.iOS.Tasks * Adds a reference to Messaging.Core targets to the Agent's project * [msbuild] Adds Xamarin iOS Windows targets * [msbuild] Adds missing dependencies to Xamarin.iOS.Tasks This should fix build errors because of missing dependencies. Had to move System.Net.Mqtt.Server from the Build agent project to the tasks one to avoid conflicts with System.Diagnostics.Tracer. * [dotnet] Creates iOS Windows pack Creates a new pack for Windows specific (targets, build agent, etc.) files that shouldn't be installed on the Mac. We have a separate package for this to avoid increasing the core pack size with things that are not needed when using it from macOS. * Fixes type in dotnet makefile * [dotnet] Fixes the iOS Windows pack generation - The windows pack should not include the Sdk and Targets folders - For now we'll just create an iOS pack - Fixes the path to the files to include on the Windows Sdk pack * Added reference to the Windows iOS SDK from the Xamarin.iOS.Common.targets Added a property to navigate to the Windows iOS SDK folder, based on a naming convention that assumes that both packs will always have the same version * Added reference to the core iOS SDK from the Windows iOS SDK Added a property to navigate to the core iOS SDK folder, based on a naming convention that assumes that both packs will always have the same version * Updated Messaging version * Override MessagingBuildClientAssemblyFile property and correctly imported props from targets * [dotnet] Make Windows pack using target files from the output dir We need to take the target files from the output dir to include targets that are part of nuget packages, otherwise we will only include targets from our source * [dotnet] Adds the Windows Sdk pack to the workload manifest * [msbuild] Fixes the Windows Sdk pack name * [dotnet] Merge Mqtt instead of Mqtt.Server We only need System.Net.Mqtt to be merged into Xamarin.iOS.Tasks * Updated Messaging version * [dotnet] Several fixes for the Windows Sdk - Adds missing task CollectMonotouchReferences - Merges more dependencies into Xamarin.iOS.Tasks.dll needed by XMA - Updates the msbuild/Makefile to include files from both the output dir and the source dir - Overrides the agents directory to look for them on the Windows pack * [dotnet] Fixes the XMA Build agent - The build agent is an app so it cannot target ns2.0 - The MSBuild dependencies should be copied into the agent zip file - Avoids copying all the Xamarin iOS SDK core targets into the build agent, since those are not needed - Ensures the broker zip file is copied into the Xamarin.iOS.Windows.Tasks output dir so its included in the Windows pack * Bumps Xamarin.Messaging to 1.2.102 * Adds net6-win branch to trigger builds * Adds Messaging.Client missing dependency to Xamarin.Mac.Tasks * Added Xamarin.Messaging.Apple.Tasks project and VerifyXcodeVersion Task * Fix unloaded Xamarin.Messaging.Build project * Added Build contracts project and unified Xamarin.Messaigng.Apple.Tasks in Xamarin.iOS.Tasks.Windows Also added missing tasks and changes .After.targets * Updated Xamarin.Messaging version * Build agent - reference MSBuild assemblies from the framework Since the assemblies will be included in the build agent we need those to be the ones that come from the framework to be compatible with macOS * [msbuild] Fixes _UpdateDynamicLibraryId target The tasks con this target need to be executed remotely (when building from Windows). * Updates resources * Bump Xamarin.Messaging Fixes problems when executing Exec task remotely * [dotnet] Overrides Publish targets to execute them remotely from Windows The `_CopyResolvedFilesToPublishPreserveNewest` and `_CopyResolvedFilesToPublishAlways` targets essentially copy files into the app bundle. Since those are part of the .NET SDK we need to override those so we can pass to the Copy task the SessionId parameter and then it will be executed remotely when building from Windows. This is done in a Windows.After.targets file so it won't affect builds on macOS. * Added ILMerge to Xamarin.iOS.Tasks.Windows Also modified ILMerge.targets to not include System assemblies because we don't need them on the Windows package * Bumps Messaging This new version of messaging fixes a problem when copying task inputs from Windows to the Mac * [dotnet] Fixes copying files to the Mac when building from Windows When building from Windows there are .NET SDK targets that copy dynamic libraries from the SDK to the intermediate output directory or other files to the publish directory, since we can't control those we can't run them remotely so we need to copy those files to the Mac to ensure other targets will find those. * [dotnet] Fixes how files are copied to the output dir - Before executing `_CopyResolvedFilesToPublishPreserveNewest` and `_CopyResolvedFilesToPublishAlways` we copy the input files for those targets to the Mac - Then we override the original targets to execute the same copy task as the original ones but on the Mac, so the output files are placed in the right location for the following targets to pick them up. * Fixes typo on Xamarin.iOS.Common.After.targets * Bumps Xamarin.Messaging * [msbuild] Fixes VerifyXcodeVersion and ResolveUTIs tasks Both tasks were not being able to connect to the Mac mostly because of ILRepack, there were kind of 2 versions of Xamarin.Messaging, one merged into Xamarin.iOS.Tasks and another one merged into Xamarin.iOS.Windows.Tasks. Because of this the build connection object registered on the task could not be casted to the build connection type. This essentially moves both tasks into the Xamarin.iOS.Tasks assembly to avoid this issue, and as part of that also includes the Messaging contracts into that same project. * [msbuild] Fixes warnings when building from Windows * [dotnet] Adds missing assemblies to merge into Xamarin.iOS.Tasks Those 2 new assemblies will only be used from Windows and we need their implementation instead of the ref assemblies. In the future we will need to find a way of doing this on the Windows only pack insted of doing it on the core Xamarin.iOS.Tasks assembly. * [dotnet] Compute PublishTrimmed on a target We need to do this so the property is evaluated after VS on Windows connects to the Mac, otherwise by default IsMacEnabled is false from Windows. * Bumps Messaging to 1.2.111 * [dotnet] Execute ILLink remotely when building from Windows - Overrides the ILLink task and _RunILLink target to add the hability to execute it remotely, adding input and output properties so files are copied to the server and output files are created on Windows. - This "custom" ILLink task will only be executed from the Windows targets so when building from a Mac it will execute the core SDK task. * [dotnet] Fixes intput/output files creation for linker tasks - Custom Linker options file should be created on the Mac so we need to execute WriteLinesToFile remotely - All the *.items files from the linker are created on the Mac so we need to execute ReadItemsFromFile remotely - CompileNativeCode: fixes the OutputFile metadata path, otherwise the execution fails; also copies all the files in the declared "IncludeDirectories" to the Mac - Avoids copying input files from Windows to the Mac when running LinkNativeCode since the real input files already exist on the Mac, and Windows contains only empty files just to make MSBuild inputs/outputs check work. If we copy those empty files to the Mac we brake the build. * [msbuild] Minor fixes after merging from main * [dotnet] Adds missing output files to the Xamarin.iOS.Tasks.Windows project The output of this project was missing Messaging build targets and the build agent zip file that are needed to create the dotnet Windows specific pack * [dotnet] Fixes dotnet Windows specific pack generation Ensures the Windows projects are built and the files are copied to the dotnet pack directory before creating the package. It also adds a variable to enable building this pack. * [dotnet] Adds iOS Windows specific pack to iOS only MSI There's only a Windows specific pack for iOS available for now, so we should only add it to the iOS SDK MSI * [dotnet] Create a separate bundle for the iOS Windows MSI We need to do this to avoid including the Windows specific pack in the pkg. Also for now we'll only create an MSI for iOS since it's the only supported platform from Windows. * Fixes spacing issues in Xamarin.iOS.Tasks.csproj * Bumps Touch.Unit back to 05db76 * Fixes formatting problems * [msbuild] Replaces error E0176 by E0186 Because there's a warning W0176 that will overlap with the error * [msbuild] Fixes CompileEntitlements task There were 2 problems: 1- The if statement on the DefaultEntitlementsPath was wrong, because we should return the base value if there's no SessionId (which means the task is running on a Mac) 2- We should copy to the Mac the default entitlements file if no custom file was specified * Several fixes to cleanup the code to support iOS from Windows * Apply suggestions from code review Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com> * Formatting fixes in Xamarin.Messaging.Build * Reverted formatting changes in CompileEntitlements.cs * More formatting fixes * Update msbuild/Messaging/Xamarin.Messaging.Build/Handlers/ExecuteTaskMessageHandler.cs Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com> * Fixes order of MSBuild errors in the resource file * Add newly added localizable strings to canary test of translated strings. * Delete tests that ensure theres code only on the abstract tasks These were needed to ensure all the code was in the base tasks so we could have tasks implementations on Windows to remote those. Now that code is part of this repo (and that is why these tests are failing now) so we do not need them anymore. * [dotnet] Don't build the Windows SDK pack if not configured to do so. Co-authored-by: mag <mauro.agnoletti@gmail.com> Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2021-02-12 09:43:17 +03:00
<data name="E0177" xml:space="preserve">
<value>Can't get an ISshCommands instance. Please check that a valid connection to the Mac is established.</value>
</data>
<data name="E0178" xml:space="preserve">
<value>An error occurred while trying to copy Archive '{0}' to '{1}'. Details: {2}</value>
</data>
<data name="E0179" xml:space="preserve">
<value>There is no available connection to the Mac. Task '{0}' will not be executed</value>
</data>
<data name="E0180" xml:space="preserve">
<value>Could not deserialize DataSet {0}</value>
</data>
<data name="E0181" xml:space="preserve">
<value>The file {0} does not have ImageAsset as build action.</value>
</data>
<data name="E0182" xml:space="preserve">
<value>Could not resolve UTI for {0} in catalog {1}</value>
</data>
<data name="E0183" xml:space="preserve">
<value>An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS</value>
</data>
<data name="E0184" xml:space="preserve">
<value>The project was built with a version of Xcode ({0}) that is not compatible which may result in unexpected warnings or errors. Please install Xcode '{1}' or visit the documentation to learn more.</value>
</data>
<data name="E0185" xml:space="preserve">
<value>An error occurred while trying to verify the compatibility between Xcode and Xamarin.iOS. Details: {0}
</value>
</data>
<data name="E0186" xml:space="preserve">
<value>The provided Archive Path is not from a valid archive file (.xcarchive). Archive Path: '{0}'</value>
</data>
<data name="E0187" xml:space="preserve">
<value>Could not map the macOS version {0} to a corresponding Mac Catalyst version. Valid macOS versions are: {1}</value>
</data>
[dotnet] Initial support for .NET6 from Windows (#10590) These changes add support for executing iOS and MacDev tasks remotely (on a Mac) when running a build from Windows, and creates a specific .NET6 pack for Windows that's only included in the MSI. For now this only enables builds for the iOS Simulator, physical devices are not yet supported. - Each task decides if it should run locally or remotely depending on the SessionId property, which will only have a value on Windows. - The XMA Build agent is now part of this repo and will be included in the iOS .NET6 Windows pack. - On this first version we're including some Windows specific tasks and references into the Xamarin.iOS.Tasks project for simplicity, but those will be moved to the Windows specific project. ------------ * [msbuild] Adds support for executing Xamarin.iOS tasks from Windows * [msbuild] Adds support for executing Xamarin.MacDev tasks from Windows * Added XMA Build Agent to Xamarin.MacDev.Tasks.sln * Fixes some MSBuild versioning problems * Makes the XMA Build agent load Xamarin.iOS tasks We need to load a type from the iOS tasks assembly so we can run the tasks requested by MSBuild from Windows. We only need to load Xamarin.iOS.Tasks.dll since MacDev.tasks is already embedded in that one. There's a little trick on the csproj, we can't directly use the Xamarin.iOS.Tasks project ref assemblies because that includes both Xamarin.iOS.Tasks.dll and Xamarin.MacDev.Tasks.dll, so the MacDev tasks will collide. We use the project ref only for build dependency purposes but we add an assembly reference to Xamarin.iOS.Tasks.dll. * Added Xamarin.iOS.Tasks.Windows project * Removed unnecessary references on Xamarin.iOS.Tasks.Windows.csproj * Adds Messaging assemblies when ILRepacking Xamarin Tasks The Xamarin Task assemblies now depend on Messaging, so we need the Messaging assemblies to be packed into Xamarin.Mac.Tasks and Xamarin.iOS.Tasks. Also had to remove the direct Messaging dependencies from the build agent since those are already contained in Xamarin.iOS.Tasks * Adds a reference to Messaging.Core targets to the Agent's project * [msbuild] Adds Xamarin iOS Windows targets * [msbuild] Adds missing dependencies to Xamarin.iOS.Tasks This should fix build errors because of missing dependencies. Had to move System.Net.Mqtt.Server from the Build agent project to the tasks one to avoid conflicts with System.Diagnostics.Tracer. * [dotnet] Creates iOS Windows pack Creates a new pack for Windows specific (targets, build agent, etc.) files that shouldn't be installed on the Mac. We have a separate package for this to avoid increasing the core pack size with things that are not needed when using it from macOS. * Fixes type in dotnet makefile * [dotnet] Fixes the iOS Windows pack generation - The windows pack should not include the Sdk and Targets folders - For now we'll just create an iOS pack - Fixes the path to the files to include on the Windows Sdk pack * Added reference to the Windows iOS SDK from the Xamarin.iOS.Common.targets Added a property to navigate to the Windows iOS SDK folder, based on a naming convention that assumes that both packs will always have the same version * Added reference to the core iOS SDK from the Windows iOS SDK Added a property to navigate to the core iOS SDK folder, based on a naming convention that assumes that both packs will always have the same version * Updated Messaging version * Override MessagingBuildClientAssemblyFile property and correctly imported props from targets * [dotnet] Make Windows pack using target files from the output dir We need to take the target files from the output dir to include targets that are part of nuget packages, otherwise we will only include targets from our source * [dotnet] Adds the Windows Sdk pack to the workload manifest * [msbuild] Fixes the Windows Sdk pack name * [dotnet] Merge Mqtt instead of Mqtt.Server We only need System.Net.Mqtt to be merged into Xamarin.iOS.Tasks * Updated Messaging version * [dotnet] Several fixes for the Windows Sdk - Adds missing task CollectMonotouchReferences - Merges more dependencies into Xamarin.iOS.Tasks.dll needed by XMA - Updates the msbuild/Makefile to include files from both the output dir and the source dir - Overrides the agents directory to look for them on the Windows pack * [dotnet] Fixes the XMA Build agent - The build agent is an app so it cannot target ns2.0 - The MSBuild dependencies should be copied into the agent zip file - Avoids copying all the Xamarin iOS SDK core targets into the build agent, since those are not needed - Ensures the broker zip file is copied into the Xamarin.iOS.Windows.Tasks output dir so its included in the Windows pack * Bumps Xamarin.Messaging to 1.2.102 * Adds net6-win branch to trigger builds * Adds Messaging.Client missing dependency to Xamarin.Mac.Tasks * Added Xamarin.Messaging.Apple.Tasks project and VerifyXcodeVersion Task * Fix unloaded Xamarin.Messaging.Build project * Added Build contracts project and unified Xamarin.Messaigng.Apple.Tasks in Xamarin.iOS.Tasks.Windows Also added missing tasks and changes .After.targets * Updated Xamarin.Messaging version * Build agent - reference MSBuild assemblies from the framework Since the assemblies will be included in the build agent we need those to be the ones that come from the framework to be compatible with macOS * [msbuild] Fixes _UpdateDynamicLibraryId target The tasks con this target need to be executed remotely (when building from Windows). * Updates resources * Bump Xamarin.Messaging Fixes problems when executing Exec task remotely * [dotnet] Overrides Publish targets to execute them remotely from Windows The `_CopyResolvedFilesToPublishPreserveNewest` and `_CopyResolvedFilesToPublishAlways` targets essentially copy files into the app bundle. Since those are part of the .NET SDK we need to override those so we can pass to the Copy task the SessionId parameter and then it will be executed remotely when building from Windows. This is done in a Windows.After.targets file so it won't affect builds on macOS. * Added ILMerge to Xamarin.iOS.Tasks.Windows Also modified ILMerge.targets to not include System assemblies because we don't need them on the Windows package * Bumps Messaging This new version of messaging fixes a problem when copying task inputs from Windows to the Mac * [dotnet] Fixes copying files to the Mac when building from Windows When building from Windows there are .NET SDK targets that copy dynamic libraries from the SDK to the intermediate output directory or other files to the publish directory, since we can't control those we can't run them remotely so we need to copy those files to the Mac to ensure other targets will find those. * [dotnet] Fixes how files are copied to the output dir - Before executing `_CopyResolvedFilesToPublishPreserveNewest` and `_CopyResolvedFilesToPublishAlways` we copy the input files for those targets to the Mac - Then we override the original targets to execute the same copy task as the original ones but on the Mac, so the output files are placed in the right location for the following targets to pick them up. * Fixes typo on Xamarin.iOS.Common.After.targets * Bumps Xamarin.Messaging * [msbuild] Fixes VerifyXcodeVersion and ResolveUTIs tasks Both tasks were not being able to connect to the Mac mostly because of ILRepack, there were kind of 2 versions of Xamarin.Messaging, one merged into Xamarin.iOS.Tasks and another one merged into Xamarin.iOS.Windows.Tasks. Because of this the build connection object registered on the task could not be casted to the build connection type. This essentially moves both tasks into the Xamarin.iOS.Tasks assembly to avoid this issue, and as part of that also includes the Messaging contracts into that same project. * [msbuild] Fixes warnings when building from Windows * [dotnet] Adds missing assemblies to merge into Xamarin.iOS.Tasks Those 2 new assemblies will only be used from Windows and we need their implementation instead of the ref assemblies. In the future we will need to find a way of doing this on the Windows only pack insted of doing it on the core Xamarin.iOS.Tasks assembly. * [dotnet] Compute PublishTrimmed on a target We need to do this so the property is evaluated after VS on Windows connects to the Mac, otherwise by default IsMacEnabled is false from Windows. * Bumps Messaging to 1.2.111 * [dotnet] Execute ILLink remotely when building from Windows - Overrides the ILLink task and _RunILLink target to add the hability to execute it remotely, adding input and output properties so files are copied to the server and output files are created on Windows. - This "custom" ILLink task will only be executed from the Windows targets so when building from a Mac it will execute the core SDK task. * [dotnet] Fixes intput/output files creation for linker tasks - Custom Linker options file should be created on the Mac so we need to execute WriteLinesToFile remotely - All the *.items files from the linker are created on the Mac so we need to execute ReadItemsFromFile remotely - CompileNativeCode: fixes the OutputFile metadata path, otherwise the execution fails; also copies all the files in the declared "IncludeDirectories" to the Mac - Avoids copying input files from Windows to the Mac when running LinkNativeCode since the real input files already exist on the Mac, and Windows contains only empty files just to make MSBuild inputs/outputs check work. If we copy those empty files to the Mac we brake the build. * [msbuild] Minor fixes after merging from main * [dotnet] Adds missing output files to the Xamarin.iOS.Tasks.Windows project The output of this project was missing Messaging build targets and the build agent zip file that are needed to create the dotnet Windows specific pack * [dotnet] Fixes dotnet Windows specific pack generation Ensures the Windows projects are built and the files are copied to the dotnet pack directory before creating the package. It also adds a variable to enable building this pack. * [dotnet] Adds iOS Windows specific pack to iOS only MSI There's only a Windows specific pack for iOS available for now, so we should only add it to the iOS SDK MSI * [dotnet] Create a separate bundle for the iOS Windows MSI We need to do this to avoid including the Windows specific pack in the pkg. Also for now we'll only create an MSI for iOS since it's the only supported platform from Windows. * Fixes spacing issues in Xamarin.iOS.Tasks.csproj * Bumps Touch.Unit back to 05db76 * Fixes formatting problems * [msbuild] Replaces error E0176 by E0186 Because there's a warning W0176 that will overlap with the error * [msbuild] Fixes CompileEntitlements task There were 2 problems: 1- The if statement on the DefaultEntitlementsPath was wrong, because we should return the base value if there's no SessionId (which means the task is running on a Mac) 2- We should copy to the Mac the default entitlements file if no custom file was specified * Several fixes to cleanup the code to support iOS from Windows * Apply suggestions from code review Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com> * Formatting fixes in Xamarin.Messaging.Build * Reverted formatting changes in CompileEntitlements.cs * More formatting fixes * Update msbuild/Messaging/Xamarin.Messaging.Build/Handlers/ExecuteTaskMessageHandler.cs Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com> * Fixes order of MSBuild errors in the resource file * Add newly added localizable strings to canary test of translated strings. * Delete tests that ensure theres code only on the abstract tasks These were needed to ensure all the code was in the base tasks so we could have tasks implementations on Windows to remote those. Now that code is part of this repo (and that is why these tests are failing now) so we do not need them anymore. * [dotnet] Don't build the Windows SDK pack if not configured to do so. Co-authored-by: mag <mauro.agnoletti@gmail.com> Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2021-02-12 09:43:17 +03:00
<data name="E0188" xml:space="preserve">
<value>Could not map the Mac Catalyst version {0} to a corresponding macOS version. Valid Mac Catalyst versions are: {1}</value>
</data>
<data name="E0189" xml:space="preserve">
<value>Could not parse the custom linker argument(s) '-{0}': {1}</value>
</data>
2020-03-14 00:46:28 +03:00
<data name="E7001" xml:space="preserve">
<value>Could not resolve host IPs for WiFi debugger settings.
</value>
</data>
<data name="E7002" xml:space="preserve">
<value>This machine does not have any network adapters. This is required when debugging or profiling on device over WiFi.
</value>
</data>
<data name="E7003" xml:space="preserve">
<value>The App Extension '{0}' does not contain an Info.plist.
</value>
</data>
<data name="E7004" xml:space="preserve">
<value>The App Extension '{0}' does not specify a CFBundleIdentifier.
</value>
</data>
<data name="E7005" xml:space="preserve">
<value>The App Extension '{0}' does not specify a CFBundleExecutable.
</value>
</data>
<data name="E7006" xml:space="preserve">
<value>The App Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}).
</value>
</data>
<data name="E7007" xml:space="preserve">
<value>The App Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key".
</value>
</data>
<data name="E7008" xml:space="preserve">
<value>The App Extension '{0}' does not specify a CFBundleShortVersionString.
</value>
</data>
<data name="E7009" xml:space="preserve">
<value>The App Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary.
</value>
</data>
<data name="E7010" xml:space="preserve">
<value>The App Extension '{0}' has an invalid Info.plist: the NSExtension dictionary does not contain an NSExtensionPointIdentifier value.
</value>
</data>
<!-- E7011: not used anymore -->
<!-- E7012: not used anymore -->
<!-- E7013: not used anymore -->
<data name="E7014" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not contain an Info.plist.
</value>
</data>
<data name="E7015" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not specify a CFBundleIdentifier.
</value>
</data>
<data name="E7016" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}).
</value>
</data>
<data name="E7017" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected 'Watch (4)' but found '{1} ({2})'.
</value>
</data>
<data name="E7018" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{name}' does not specify a CFBundleExecutable
</value>
</data>
<data name="E7019" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}').
</value>
</data>
<data name="E7020" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' has an invalid Info.plist: the WKWatchKitApp key must be present and have a value of 'true'.
</value>
</data>
<data name="E7021" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present.
</value>
</data>
<data name="E7022" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not contain any Watch Extensions.
</value>
</data>
<data name="E7022_A" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not contain a Watch Extension.
</value>
<comment>The watchOS Application does not contain a watchOS extension, see: https://developer.apple.com/documentation/watchkit
{0} - The app bundle name, such as 'YourWatchOSApp.app'</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E7023" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' does not contain an Info.plist.
</value>
</data>
<data name="E7024" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' does not specify a CFBundleIdentifier.
</value>
</data>
<data name="E7025" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' does not specify a CFBundleExecutable.
</value>
</data>
<data name="E7026" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has an invalid CFBundleIdentifier ({1}), it does not begin with the main app bundle's CFBundleIdentifier ({2}).
</value>
</data>
<data name="E7027" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has a CFBundleIdentifier ({1}) that ends with the illegal suffix ".key".
</value>
</data>
<data name="E7028" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has an invalid Info.plist: it does not contain an NSExtension dictionary.
</value>
</data>
<data name="E7029" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionPointIdentifier must be "com.apple.watchkit".
</value>
</data>
<data name="E7029_A" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain an NSExtensionPointIdentifier.
</value>
</data>
<data name="E7030" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has an invalid Info.plist: the NSExtension dictionary must contain NSExtensionAttributes.
</value>
</data>
<data name="E7031" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the parent Watch App bundle's CFBundleIdentifier ('{2}').
</value>
</data>
<data name="E7031_A" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch Extension '{0}' has an invalid Info.plist: the NSExtensionAttributes dictionary must contain a WKAppBundleIdentifier.
</value>
</data>
<data name="E7032" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities dictionary should not contain the 'watch-companion' capability.
</value>
</data>
<data name="E7032_A" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The WatchKit Extension '{0}' has an invalid Info.plist: the UIRequiredDeviceCapabilities array should not contain the 'watch-companion' capability.
</value>
</data>
<data name="E7033" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not contain an Info.plist.
</value>
</data>
<data name="E7034" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not specify a CFBundleIdentifier.
</value>
</data>
<data name="E7035" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not have a valid UIDeviceFamily value. Expected '{1}' but found '{2} ({3})'.
</value>
</data>
<data name="E7036" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' does not specify a CFBundleExecutable.
</value>
</data>
<data name="E7037" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The WatchKit Extension '{0}' has an invalid WKAppBundleIdentifier value ('{1}'), it does not match the Watch App's CFBundleIdentifier ('{2}').
</value>
</data>
<data name="E7038" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' has an invalid WKCompanionAppBundleIdentifier value ('{1}'), it does not match the main app bundle's CFBundleIdentifier ('{2}').
</value>
</data>
<data name="E7038_A" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' has an invalid Info.plist: the WKCompanionAppBundleIdentifier must exist and must match the main app bundle's CFBundleIdentifier.
</value>
</data>
<data name="E7039" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The Watch App '{0}' has an invalid Info.plist: the LSRequiresIPhoneOS key must not be present.
</value>
</data>
<data name="E7040" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>The app bundle {0} does not contain an Info.plist.
</value>
</data>
<data name="E7041" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} does not specify a CFBundleIdentifier.
</value>
</data>
<data name="E7042" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} does not specify a CFBundleExecutable.
</value>
</data>
<data name="E7043" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} does not specify a CFBundleSupportedPlatforms.
</value>
</data>
<data name="E7044" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} does not specify a UIDeviceFamily.
</value>
</data>
<data name="E7044_A" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>{0} is invalid: the UIDeviceFamily key must contain a value for '{1}'.
</value>
</data>
<data name="E7045" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Unrecognized Type: {Type}
</value>
</data>
<data name="E7046" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Add: Entry, "{0}", Incorrectly Specified
</value>
</data>
<data name="E7047" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Add: Entry, "{0}", Contains Invalid Array Index
</value>
</data>
<data name="E7048" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Add: "{0}" Entry Already Exists
</value>
</data>
<data name="E7049" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Add: Can't Add Entry, "{0}", to Parent
</value>
</data>
<data name="E7050" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Delete: Can't Delete Entry, "{0}", from Parent
</value>
</data>
<data name="E7051" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Delete: Entry, "{0}", Contains Invalid Array Index
</value>
</data>
<data name="E7052" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Delete: Entry, "{0}", Does Not Exist
</value>
</data>
<data name="E7053" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Import: Entry, "{0}", Incorrectly Specified
</value>
</data>
<data name="E7054" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Import: Entry, "{0}", Contains Invalid Array Index
</value>
</data>
<data name="E7055" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Import: Error Reading File: {0}
</value>
</data>
<data name="E7056" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Import: Can't Add Entry, "{0}", to Parent
</value>
</data>
<data name="E7057" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Merge: Can't Add array Entries to dict
</value>
<comment>Array entries in a '.plist' file (see: https://en.wikipedia.org/wiki/Property_list), cannot be added to a dictionary.</comment>
2020-03-14 00:46:28 +03:00
</data>
<data name="E7058" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Merge: Specified Entry Must Be a Container
</value>
</data>
<data name="E7059" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Merge: Entry, "{0}", Contains Invalid Array Index
</value>
</data>
<data name="E7060" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Merge: Entry, "{0}", Does Not Exist
</value>
</data>
<data name="E7061" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Merge: Error Reading File: {0}
</value>
</data>
<data name="E7062" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Set: Entry, "{0}", Incorrectly Specified
</value>
</data>
<data name="E7063" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Set: Entry, "{0}", Contains Invalid Array Index
</value>
</data>
<data name="E7064" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Set: Entry, "{0}", Does Not Exist
</value>
</data>
<data name="E7068" xml:space="preserve">
2020-03-14 00:46:28 +03:00
<value>Can't create a binding resource package unless there are native references in the binding project.
</value>
</data>
<data name="E7069" xml:space="preserve">
<value>Xamarin.iOS 14+ does not support watchOS 1 apps. Please migrate your project to watchOS 2+.</value>
</data>
<data name="E7070" xml:space="preserve">
<value>Invalid architecture ({0}): can't link more than one architecture at a time.</value>
</data>
2021-01-25 17:38:17 +03:00
<data name="E7071" xml:space="preserve">
<value>Unable to parse the AOT compiler arguments: {0} ({1})</value>
<comment>
AOT: Ahead-of-Time
{0}: The arguments that failed to parse
{1}: A more detailed description about the failure
</comment>
</data>
<data name="InvalidFramework" xml:space="preserve">
<value>Invalid framework: {0}</value>
</data>
<data name="InvalidPlatform" xml:space="preserve">
<value>Invalid platform: {0}</value>
</data>
Xamarin.Mac native Apple Silicon targetting support (#10115) * Add support for Xamarin.Mac arm64 * Add compile product definition task Xamarin.Mac can be provided with a ProductDefinition file for the generated pkg. Normally, providing a product definition was optional. However, with Apple Silicon, we have an extra issue : `productbuild` needs to know what architectures your package target. If not provided with them, it will guess to the best of its abilities. However, on Catalina and lower, the guess is x86_64, even if you have an arm64 slice. To fix this, we add a new task to compile the product definition and use this file to create the pkg. If you provide your own Product Definition, we can check and warn if the architectures don't match what we expect. If the file doesn't exist or there is no architecture, we set it ourselves based on our target architectures. * Don't reference dynamic objC_send on arm64 When building in debug, we currently try to link dynamic objC_send symbols when targeting a 64-bit architecture. However, this is actually only defined on Intel architectures, not on arm64, so we end up failing because we're referring symbols that don't exist. Rework the `GetRequiredSymbols` to take an abi, and tag those symbols to only be valid on i386/x86_64, so they don't get referred at all when building on arm64, but still get referred in x86_64. * Fix improper delete/move with already existing directories * Fix stret requirement for Xamarin.Mac in arm64. The generator supposes that we're running in x64 mode, refactor to take into account the possibility of running in arm64. * Implement OS version generation in Product.plist, based on MinimumSystemVersion of the app * Re-generalize some mmp registrar rules `Microsoft.macOS.registrar` was missed by the current rule set * Fix mmp tests * Set E7072 as not translated Tests were failing otherwise * Rename Xamarin.Mac lib/x86_64 folder to 64bits (currently all targeted archs are the same) * Fix style issues * Fix `ToLower` usage for invariant usage * Fix xtro-sharpie test
2021-03-18 04:48:02 +03:00
<data name="E7072" xml:space="preserve">
<value>Package product requirement file contains architectures ({0}) which mismatches with target architectures ({1})</value>
</data>
<data name="E7073" xml:space="preserve">
<value>At least one app bundle must be specified.</value>
</data>
<data name="E7074" xml:space="preserve">
<value>The app bundle {0} does not exist.</value>
</data>
<data name="E7075" xml:space="preserve">
<value>No 'SpecificSubDirectory' metadata was provided for the app bundle {0}.</value>
</data>
<data name="E7076" xml:space="preserve">
<value>Can't merge the symlink '{0}', it has different targets.</value>
</data>
<data name="E7077" xml:space="preserve">
<value>Unable to merge the file '{0}', it's different between the input app bundles.</value>
</data>
<data name="E7078" xml:space="preserve">
<value>Invalid app bundle: the Mach-O file {0} has dependent files.</value>
</data>
<data name="E7079" xml:space="preserve">
<value>Invalid app bundle: the file {0} has different types between the input app bundles.</value>
</data>
<data name="E7080" xml:space="preserve">
<value>App bundle file #{0}: {1}</value>
<comment>
This error will be shown multiple times, listing the full path to the files causing E7076, E7077 and E7079.
{0}: a number indicating which input app bundle the file is from
{1}: the full path to the file in question
</comment>
</data>
<data name="E7081" xml:space="preserve">
<value>The AOT compiler '{0}' does not exist.</value>
<comment>
AOT: Ahead-Of-Time
{0}: the path to the compiler
</comment>
</data>
<data name="E7082" xml:space="preserve">
<value>The {0} value in the Info.plist ({1}) does not match the SupportedOSPlatformVersion value ({2}) in the project file (if there is no SupportedOSPlatformVersion value in the project file, then a default value has been assumed). Either change the value in the Info.plist to match the SupportedOSPlatformVersion value, or remove the value in the Info.plist (and add a SupportedOSPlatformVersion value to the project file if it doesn't already exist).</value>
<comment>
{0}: the name of a value from the Info.plist file the message talks about (either 'MinimumOSVersion' or 'LSMinimumSystemVersion').
{1}: the value from the Info.plist.
{2}: the value from the project file.
</comment>
</data>
<data name="E7083" xml:space="preserve">
<value>All font files must be located in the same directory in the app bundle. The following font files have different target directories in the app bundle:</value>
<comment>This error message will be followed by E7084 error messages listing the target directory for each font file</comment>
</data>
<data name="E7084" xml:space="preserve">
<value>The target directory is {0}</value>
<comment>See E7082 as well.
{0}: the target directory (in the app bundle) for the font file
</comment>
</data>
[msbuild] Rework code signing to sign everything at the end of the build. (#13956) * Add support for specifying metadata on items that are to be codesigned to override any general codesign setting. * Make the Codesign task able to sign files and directories that may depend on eachother. Implement support for ordering signing so that directories containing files that also must be signed are signed after those files. This is implemented by: 1. Normalize all input (resolve symlinks, create full path, etc.) 2. Sort by path length (longest to shortest paths). This way we're certain that if we find a directory, we'll know that we won't find any files later in the list from inside that directory. 3. Group into an ordered list of buckets, where each bucket contains files and directories that don't depend on eachother (i.e. they can all be signed in parallel). This makes it possible to call Codesign once, listing both the app bundle itself, and all the individual files or directories inside that need signing, and the Codesign task will sign the items in an order that ensures parent directories are always signed after any files or directories inside. * Finally rework code signing to sign everything with a single call to the Codesign task in the _CodesignAppBundle target for the executable project, instead of having multiple calls to the Codesign task from multiple targets (and projects). This makes it easier to reason about what's being signed, and it also makes it easier to add files to the signing process. * Also make the Codesign task able to figure out if something needs to be signed, and change the _CodesignAppBundle target to not keep track of inputs/outputs, because it becomes quite complex (for directories, it needs to keep track of all the files inside that directory, and also if there's anything in the directory that's also being signed).
2022-02-08 12:41:51 +03:00
<data name="E7085" xml:space="preserve">
<value>The "{0}" task was not given a value for the required parameter "{1}", nor was there a "{2}" metadata on the resource {3}.</value>
</data>
<data name="W7085" xml:space="preserve">
<value>Creating a compressed binding resource package because there are symlinks in the input.</value>
</data>
<data name="E7086" xml:space="preserve">
<value>The value '{0}' is invalid for the Compress property. Valid values: 'true', 'false' or 'auto'.</value>
<comment>The following are literal names and should not be translated: Compress, true, false, auto.</comment>
</data>
<data name="W7087" xml:space="preserve">
<value>Expected a 'manifest' file in the directory {0}.</value>
<comment>The following are literal names and should not be translated: manifest</comment>
</data>
<data name="E7088" xml:space="preserve">
<value>The 'PublishFolderType' metadata value '{0}' on the item '{1}' is not recognized. The file will not be copied to the app bundle.</value>
<comment>
PublishFolderType: do not translate (name of metadata)
{0}: metadata value (read from a user file)
{1}: path to a file
</comment>
</data>
<data name="E7089" xml:space="preserve">
<value>The file '{0}' does not specify a 'PublishFolderType' metadata, and a default value could not be calculated. The file will not be copied to the app bundle.</value>
<comment>
PublishFolderType: do not translate (name of metadata)
{0}: path to a file
</comment>
</data>
<data name="E7090" xml:space="preserve">
<value>The 'PublishFolderType' metadata value '{0}' on the item '{1}' is not recognized. The file will not be copied to the app bundle. If the file is not supposed to be copied to the app bundle, remove the '{2}' metadata on the item.</value>
<comment>
PublishFolderType: do not translate (name of metadata)
{0}: metadata value (read from a user file)
{1}: path to a file
{2}: name of metadata (either 'CopyToOutputDirectory' or 'CopyToPublishDirectory')
</comment>
</data>
<data name="W7091" xml:space="preserve">
<value>The framework {0} is a framework of static libraries, and will not be copied to the app.</value>
</data>
<!-- This is the same as MT0140 -->
<data name="E7092" xml:space="preserve">
<value>File '{0}' is not a valid framework: {1}</value>
</data>
<data name="W7093" xml:space="preserve">
<value>The binding resource package {0} does not exist.</value>
</data>
<data name="E7094" xml:space="preserve">
<value>The file or directory '{0}' is not a framework nor a file within a framework.</value>
</data>
<data name="W7095" xml:space="preserve">
<value>Code signing has been requested multiple times for '{0}', with different metadata. The metadata for one are: '{1}', while the metadata for the other are: '{2}'</value>
</data>
<data name="W7096" xml:space="preserve">
<value>Code signing has been requested multiple times for '{0}', with different metadata. The metadata '{1}={2}' has been set for one item, but not the other.</value>
</data>
<data name="W7097" xml:space="preserve">
<value>Code signing has been requested multiple times for '{0}', with different metadata. The metadata '{1}' has different values for each item (once it's '{2}', another time it's '{3}').</value>
</data>
<data name="E7098" xml:space="preserve">
<value>The UIDeviceFamily value '6' is not valid for this platform. It's only valid for Mac Catalyst.</value>
</data>
<data name="E7099" xml:space="preserve">
<value>The UIDeviceFamily value '6' requires macOS 11.0. Please set the 'SupportedOSPlatformVersion' in the project file to at least 14.0 (the Mac Catalyst version equivalent of macOS 11.0). The current value is {0} (equivalent to macOS {1}).</value>
</data>
[msbuild/dotnet] Fix building binding projects on Windows in .NET (#14704) When building a binding project, we need to execute bgen (and csc) on the mac. Figuring out where these files are on the Mac is rather complicated from a remotely executed task, so instead we execute a sub-build that computes these properties. In legacy Xamarin this was accomplished by building the 'Xamarin.iOS.ObjCBinding.Common.props' file using msbuild, and invoking a custom target that prints the property we're looking for (the 'targetGetPropertyValue_*' targets). For multiple reasons this approach doesn't work in .NET anymore (in particular it seems that the 'Xamarin.iOS.ObjCBinding.Common.After.targets' file with the custom 'targetGetPropertyValue_*' targets is nowhere to be found, but logic has also moved around in the .targets/.props files which makes just building the 'Xamarin.iOS.ObjCBinding.Common.props' not work correctly since the properties we need wouldn't be set). So I'm adding a new task that does a sub-build, using either msbuild or dotnet as appropriate, to compute the properties we need. Instead of building the 'Xamarin.iOS.ObjCBinding.Common.props' file, the task creates an actual binding project (an empty one), and executes the new '_WriteRemoteGeneratorProperties' target in this binding project. An additional advantage in this new task is that it will only execute one sub-build where all the properties are computed (the previous approach executed one sub-msbuild per property). In order to keep code as similar as possible between legacy Xamarin and .NET, the new task is being used for legacy Xamarin as well (and the old approach deleted). This fixes building binding projects on Windows in .NET.
2022-04-22 17:17:03 +03:00
<data name="W7100" xml:space="preserve">
<value>Could not find the binding resource package: {0}</value>
</data>
[msbuild/dotnet] Fix building binding projects on Windows in .NET (#14704) When building a binding project, we need to execute bgen (and csc) on the mac. Figuring out where these files are on the Mac is rather complicated from a remotely executed task, so instead we execute a sub-build that computes these properties. In legacy Xamarin this was accomplished by building the 'Xamarin.iOS.ObjCBinding.Common.props' file using msbuild, and invoking a custom target that prints the property we're looking for (the 'targetGetPropertyValue_*' targets). For multiple reasons this approach doesn't work in .NET anymore (in particular it seems that the 'Xamarin.iOS.ObjCBinding.Common.After.targets' file with the custom 'targetGetPropertyValue_*' targets is nowhere to be found, but logic has also moved around in the .targets/.props files which makes just building the 'Xamarin.iOS.ObjCBinding.Common.props' not work correctly since the properties we need wouldn't be set). So I'm adding a new task that does a sub-build, using either msbuild or dotnet as appropriate, to compute the properties we need. Instead of building the 'Xamarin.iOS.ObjCBinding.Common.props' file, the task creates an actual binding project (an empty one), and executes the new '_WriteRemoteGeneratorProperties' target in this binding project. An additional advantage in this new task is that it will only execute one sub-build where all the properties are computed (the previous approach executed one sub-msbuild per property). In order to keep code as similar as possible between legacy Xamarin and .NET, the new task is being used for legacy Xamarin as well (and the old approach deleted). This fixes building binding projects on Windows in .NET.
2022-04-22 17:17:03 +03:00
<data name="E7101" xml:space="preserve">
<value>Unknown property '{0}' with value '{1}'.</value>
</data>
2020-03-14 00:46:28 +03:00
</root>