diff --git a/src/Shared/Resources/xlf/Strings.shared.ru.xlf b/src/Shared/Resources/xlf/Strings.shared.ru.xlf index fb8b260fb3b..bbc061ddd6c 100644 --- a/src/Shared/Resources/xlf/Strings.shared.ru.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.ru.xlf @@ -4,90 +4,47 @@ MSB4188: Build was canceled. - MSB4188: Build was canceled. + MSB4188: сборка отменена. {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. + MSB5022: узел сборки MSBuild не поддерживает задачи, которые выполняют обратные вызовы IBuildEngine. Если необходимо выполнить эти операции, запустите задачу в основном процессе MSBuild. Задача будет автоматически выполнена в узле задач, если для UsingTask был указан атрибут со значением "Runtime" или "Architecture" или для вызова задачи был указан атрибут со значением "MSBuildRuntime" или "MSBuildArchitecture", которые не соответствуют текущей среде выполнения или архитектуре MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. Build started. - Build started. + Сборка начата. The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). - The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + Количество элементов в коллекции превышает доступное пространство в целевом массиве (при запуске с указанного индекса). MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". + MSB4008: в "{1}" обнаружена сборка, конфликтующая со сборкой задачи "{0}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs + Настраиваемый тип '{0}' не поддерживается, так как все пользовательские типы событий устарели. Используйте extended*EventArgs. Дополнительные сведения: https://aka.ms/msbuild/eventargs - - Could not find directory path: {0} - Could not find directory path: {0} - Directory must exist - Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + Необходимо, чтобы тип события "{0}" был сериализуемым с помощью сериализатора .NET. Событие не было сериализуемым и было пропущено. {0} ({1},{2}) - {0} ({1},{2}) + {0} ({1},{2}) A file location to be embedded in a string. - - When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - No Error code because this resource will be used in an exception. The error code is discarded if it is included - - - .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - - - - .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - - - - Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - - - - MSB4233: There was an exception while reading the log file: {0} - MSB4233: There was an exception while reading the log file: {0} - {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. - - - MSB4025: The project file could not be loaded. {0} - MSB4025: The project file could not be loaded. {0} - {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is - invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is - provided separately to loggers. - LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. - - - MSB4103: "{0}" is not a valid logger verbosity level. - MSB4103: "{0}" is not a valid logger verbosity level. - {StrBegin="MSB4103: "} - MSB6005: Task attempted to log before it was initialized. Message was: {0} - MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: задачей предпринята попытка вести журнал до своей инициализации. Сообщение: {0} {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. @@ -100,247 +57,290 @@ Normal should not be localized. Low should not be localized. - - MSBuild is expecting a valid "{0}" object. - MSBuild is expecting a valid "{0}" object. - - Making the following modifications to the environment received from the parent node before applying it to the task host: - Making the following modifications to the environment received from the parent node before applying it to the task host: + Перед применением окружения, полученного от родительского узла, к серверу задач в нем выполняются следующие изменения: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. + Задание для "{0}" значения "{1}", а не значения родительского окружения "{2}". Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 - - MSB5016: The name "{0}" contains an invalid character "{1}". - MSB5016: The name "{0}" contains an invalid character "{1}". - {StrBegin="MSB5016: "} + + MSB4025: The project file could not be loaded. {0} + MSB4025: не удалось загрузить файл проекта. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. - - This collection is read-only. - This collection is read-only. + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" не является допустимым уровнем детализации средства ведения журнала. + {StrBegin="MSB4103: "} + + + MSBuild is expecting a valid "{0}" object. + Для MSBuild требуется допустимый объект "{0}". - - MSB5024: Could not determine a valid location to MSBuild. Try running this process from the Developer Command Prompt for Visual Studio. - MSB5024: Could not determine a valid location to MSBuild. Try running this process from the Developer Command Prompt for Visual Studio. - {StrBegin="MSB5024: "} + + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. + Длина пути {0} превышает максимально допустимую в ОС. Символов в полном имени файла должно быть не больше {1}. + + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: файл фильтра решения в "{0}" включает проект "{1}", который отсутствует в файле решения в "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: код JSON в файле фильтра решения "{0}" имеет неправильный формат. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: файл фильтра решения в "{0}" указывает на то, что в "{1}" будет находиться файл решения, однако этот файл отсутствует. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: ошибка при синтаксическом анализе раздела проекта "{0}" с GUID: "{1}". Он вложен в "{2}", но этот проект не найден в решении. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: версия инструментов "{0}" не распознана. Доступные версии инструментов: {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: имя "{0}" содержит недопустимый знак "{1}". + {StrBegin="MSB5016: "} "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{0}" - зарезервированные метаданные элемента; их изменение или удаление невозможно. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The string "{0}" cannot be converted to a boolean (true/false) value. - The string "{0}" cannot be converted to a boolean (true/false) value. + Строка "{0}" не может быть преобразована в логическое значение (истина/ложь). MSB5003: Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - MSB5003: Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} + MSB5003: не удалось создать временный файл. Папка временных файлов переполнена, или указан неверный путь. {0} {StrBegin="MSB5003: "} MSB5018: Failed to delete the temporary file "{0}". {1} {2} - MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: не удалось удалить временный файл "{0}". {1} {2} {StrBegin="MSB5018: "} - - An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - - The item metadata "%({0})" cannot be applied to the path "{1}". {2} - The item metadata "%({0})" cannot be applied to the path "{1}". {2} + Не удается применить метаданные элемента "%({0})" к пути "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. - - MSB5019: The project file is malformed: "{0}". {1} - MSB5019: The project file is malformed: "{0}". {1} - {StrBegin="MSB5019: "} + + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. + MSB4077: задача "{0}" помечена атрибутом LoadInSeparateAppDomain, но не является производной от MarshalByRefObject. Задача должна быть производной от MarshalByRefObject или AppDomainIsolatedTask. + {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. + + + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework версии "{0}" не поддерживается. Укажите значение из перечисления Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + + + + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. + При явном использовании пакета Windows SDK платформа .NET Framework версии "{0}" не поддерживается; она поддерживается только платформой .NET 4.5 и более поздними версиями. Укажите значение из перечисления Microsoft.Build.Utilities.TargetDotNetFrameworkVersion версии Version45 или более поздней. + + + + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. + Visual Studio версии "{0}" не поддерживается. Укажите значение из перечисления Microsoft.Build.Utilities.VisualStudioVersion. + + + + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} + Ошибка при попытке создать ссылочный путь к сборке из пути "{0}" и моникер инфраструктуры "{1}". {2} + No Error code because this resource will be used in an exception. The error code is discarded if it is included + + + Could not find directory path: {0} + Не удалось найти путь к каталогу: {0} + Directory must exist + + + You do not have access to: {0} + Отсутствуют права доступа к: {0} + Directory must have access + + + Schema validation + Проверка схемы + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. - MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: завершается исполняемый файл задачи "{0}", так как он не закончил работу в указанный период {1} мс. {StrBegin="MSB5002: "} - - MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. - MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. - {StrBegin="MSB5021: "} - Parameter "{0}" cannot be null. - Parameter "{0}" cannot be null. - - - - Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. - Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Параметр "{0}" не может иметь неопределенное (null) значение. Parameter "{0}" cannot have zero length. - Parameter "{0}" cannot have zero length. + Длина параметра "{0}" не может быть равна нулю. Parameters "{0}" and "{1}" must have the same number of elements. - Parameters "{0}" and "{1}" must have the same number of elements. + Параметры "{0}" и "{1}" должны содержать одинаковое количество элементов. - - Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - - - - MSB5020: Could not load the project file: "{0}". {1} - MSB5020: Could not load the project file: "{0}". {1} - {StrBegin="MSB5020: "} - The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. - The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + Не удалось найти строку ресурса "{0}" для задачи "{1}". Убедитесь, что имя ресурса "{0}" написано правильно и ресурс существует в сборке задачи. The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. - The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + Задача "{0}" не зарегистрировала свои ресурсы. Чтобы использовать метод "TaskLoggingHelper.FormatResourceString()", эта задача должна зарегистрировать свои ресурсы во время построения или через свойство "TaskResources". LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. - - MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". - MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". - {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. - - - MSB5025: Json in solution filter file "{0}" is incorrectly formatted. - MSB5025: Json in solution filter file "{0}" is incorrectly formatted. - {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. - - - MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. - MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. - {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. - MSB5004: The solution file has two projects named "{0}". - MSB5004: The solution file has two projects named "{0}". + MSB5004: файл решения содержит два проекта с именем "{0}". {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. - MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: ошибка синтаксического анализа раздела проекта "{0}". Имя файла проекта "{1}" содержит недопустимые символы. {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. MSB5006: Error parsing project section for project "{0}". The project file name is empty. - MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: ошибка синтаксического анализа раздела проекта "{0}". Имя файла проекта пусто. {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. - MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: ошибка синтаксического анализа раздела конфигурации проекта в файле решения. Недопустимая запись "{0}". {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. - MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: ошибка синтаксического анализа раздела конфигурации проекта в файле решения. Недопустимая запись "{0}". {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. MSB5009: Error parsing the nested project section in solution file. - MSB5009: Error parsing the nested project section in solution file. - {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. - - - MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. - MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: ошибка синтаксического анализа вложенного раздела проекта в файле решения. {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. - MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: ошибка синтаксического анализа вложенного раздела проекта в файле решения. Указано, что проект с GUID "{0}" вложен в проект "{1}", но сам проект отсутствует в решении. {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. MSB5010: No file format header found. - MSB5010: No file format header found. + MSB5010: заголовок формата файла не найден. {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. MSB5011: Parent project GUID not found in "{0}" project dependency section. - MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: родительский проект GUID не найден в разделе зависимости проекта "{0}". {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. MSB5012: Unexpected end-of-file reached inside "{0}" project section. - MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: достигнуто непредвиденное окончание файла в разделе проекта "{0}". {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. MSB5013: Error parsing a project section. - MSB5013: Error parsing a project section. + MSB5013: ошибка при синтаксическом анализе раздела проекта. {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. - MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: не распознана версия формата файла. MSBuild может считывать файлы решения только версий с {0}.0 по {1}.0 включительно. {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. - MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: не удалось прочитать свойства из раздела WebsiteProperties проекта "{0}". {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. - - Schema validation - Schema validation - - UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is - displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: - "MSBUILD : Schema validation error MSB0000: This is an error." - LOCALIZATION: This fragment needs to be localized. - + + Unrecognized solution version "{0}", attempting to continue. + Нераспознанная версия решения "{0}"; попытка продолжить. + Solution file - Solution file + Файл решения UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: "MSBUILD : Solution file error MSB0000: This is an error." LOCALIZATION: This fragment needs to be localized. - - MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: файл проекта имеет неправильный формат: "{0}". {1} + {StrBegin="MSB5019: "} - - You do not have access to: {0} - You do not have access to: {0} - Directory must have access + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: не удалось загрузить файл проекта: "{0}". {1} + {StrBegin="MSB5020: "} - - Unrecognized solution version "{0}", attempting to continue. - Unrecognized solution version "{0}", attempting to continue. + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: завершается исполняемый файл задачи "{0}" и его дочерние процессы, так как сборка отменена. + {StrBegin="MSB5021: "} + + + This collection is read-only. + Эта коллекция доступна только для чтения. - - MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. - MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. - {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + MSB5024: Could not determine a valid location to MSBuild. Try running this process from the Developer Command Prompt for Visual Studio. + MSB5024: Не удалось определить допустимое расположение для MSBuild. Попробуйте запустить этот процесс из командной строки разработчика для Visual Studio. + {StrBegin="MSB5024: "} + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: возникло исключение при чтении файла журнала: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Параметр "{0}" с назначенным значением "{1}" не может иметь недопустимый путь или недопустимые символы файлов. + + + + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} + Возникло исключение при расширении fileSpec со стандартными масками: fileSpec: "{0}", предполагая, что это имя файла. Исключение: {1} + MSB5029: The value "{0}" of the "{1}" attribute in element <{2}> in file "{3}" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always defined and that the project and current working directory are not at the drive root. - MSB5029: The value "{0}" of the "{1}" attribute in element <{2}> in file "{3}" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always defined and that the project and current working directory are not at the drive root. + MSB5029: значение "{0}" атрибута "{1}" в элементе <{2}> в файле "{3}" является подстановочным знаком, который приводит к перечислению всех файлов на диске, что, вероятно, не предполагалось. Убедитесь, что указанные свойства всегда определены и что проект и текущий рабочий каталог не находятся в корне диска. {StrBegin="MSB5029: "}UE: This is a generic message that is displayed when we find a project element that has a drive enumerating wildcard value for one of its attributes e.g. <Compile Include="$(NotAlwaysDefined)\**\*.cs"> -- if the property is undefined, the value of Include should not result in enumerating all files on drive. diff --git a/src/Shared/Resources/xlf/Strings.shared.tr.xlf b/src/Shared/Resources/xlf/Strings.shared.tr.xlf index 9dd6f4467b7..2d299362405 100644 --- a/src/Shared/Resources/xlf/Strings.shared.tr.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.tr.xlf @@ -4,90 +4,47 @@ MSB4188: Build was canceled. - MSB4188: Build was canceled. + MSB4188: Derleme iptal edildi. {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. + MSB5022: MSBuild görev konağı IBuildEngine geri çağırmaları gerçekleştiren görevleri çalıştırmayı desteklemez. Bu işlemleri gerçekleştirmek istiyorsanız lütfen bunun yerine görevinizi çekirdek MSBuild işleminde gerçekleştirin. UsingTask öğesine bir "Runtime" veya "Architecture" değeri atfedilmişse veya görev çağrısına MSBuild’in geçerli çalışma zamanı ya da mimarisi ile eşleşmeyen bir "MSBuildRuntime" veya "MSBuildArchitecture" değeri atfedilmişse görev konağında bir görev otomatik olarak yürütülür. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. Build started. - Build started. + Oluşturma başlatıldı. The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). - The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + Koleksiyondaki öğe sayısı hedef dizideki kullanılabilir boşluğun boyutundan (belirtilen dizinden başlayarak) daha büyük. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". + MSB4008: "{0}" görev derlemesi için "{1}" konumunda çakışan derleme bulundu. {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs + Tüm özel '{0}' türleri kullanım dışı bırakıldığinden özel olay türü türü desteklenmiyor. Lütfen bunun yerine Extended*EventArgs kullanın. Daha fazla bilgi: https://aka.ms/msbuild/eventargs - - Could not find directory path: {0} - Could not find directory path: {0} - Directory must exist - Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + "{0}" olay türünün .NET serileştiricisi kullanılarak serileştirilebilir olması bekleniyordu. Olay serileştirilebilir değildi ve yoksayıldı. {0} ({1},{2}) - {0} ({1},{2}) + {0} ({1},{2}) A file location to be embedded in a string. - - When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - No Error code because this resource will be used in an exception. The error code is discarded if it is included - - - .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - - - - .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - - - - Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - - - - MSB4233: There was an exception while reading the log file: {0} - MSB4233: There was an exception while reading the log file: {0} - {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. - - - MSB4025: The project file could not be loaded. {0} - MSB4025: The project file could not be loaded. {0} - {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is - invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is - provided separately to loggers. - LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. - - - MSB4103: "{0}" is not a valid logger verbosity level. - MSB4103: "{0}" is not a valid logger verbosity level. - {StrBegin="MSB4103: "} - MSB6005: Task attempted to log before it was initialized. Message was: {0} - MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Görev başlatılmadan önce günlüğe yazmaya çalıştı. İleti: {0} {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. @@ -100,247 +57,290 @@ Normal should not be localized. Low should not be localized. - - MSBuild is expecting a valid "{0}" object. - MSBuild is expecting a valid "{0}" object. - - Making the following modifications to the environment received from the parent node before applying it to the task host: - Making the following modifications to the environment received from the parent node before applying it to the task host: + Üst düğümden alınan ortam görev ana bilgisayarına uygulanmadan önce ortamda aşağıdaki değişiklikler yapılıyor: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. + '{0}', üst ortamında değeri olan '{2}' yerine '{1}' değerine ayarlanıyor. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 - - MSB5016: The name "{0}" contains an invalid character "{1}". - MSB5016: The name "{0}" contains an invalid character "{1}". - {StrBegin="MSB5016: "} + + MSB4025: The project file could not be loaded. {0} + MSB4025: Proje dosyası yüklenemedi. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. - - This collection is read-only. - This collection is read-only. + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}", geçerli bir günlükçü ayrıntı düzeyi değil. + {StrBegin="MSB4103: "} + + + MSBuild is expecting a valid "{0}" object. + MSBuild, geçerli bir "{0}" nesnesi bekliyor. - - MSB5024: Could not determine a valid location to MSBuild. Try running this process from the Developer Command Prompt for Visual Studio. - MSB5024: Could not determine a valid location to MSBuild. Try running this process from the Developer Command Prompt for Visual Studio. - {StrBegin="MSB5024: "} + + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. + Yol: {0}, işletim sisteminin en yüksek yol sınırını aşıyor. Tam dosya adı en fazla {1} karakter olmalıdır. + + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: "{0}" konumundaki çözüm filtresi dosyası, "{2}" konumundaki çözüm dosyasında bulunmayan "{1}" projesini içeriyor. + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: "{0}" çözüm filtresi dosyasındaki JSON hatalı biçimlendirilmiş. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: "{0}" konumundaki çözüm filtresi dosyası, "{1}" konumunda bir çözüm dosyası olacağını belirtiyor, ancak bu dosya mevcut değil. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: "{1}" GUID'si ile "{0}" proje bölümü ayrıştırılırken hata oluştu. Proje "{2}" altında iç içe yerleştirilmiş ancak bu proje çözümde bulunamadı. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: Araçlar sürümü "{0}" tanınmıyor. Kullanılabilir araç sürümleri şunlardır: {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: "{0}" adı geçersiz "{1}" karakterini içeriyor. + {StrBegin="MSB5016: "} "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{0}" ayrılmış bir öğe meta verisi olduğu için değiştirilemez veya silinemez. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The string "{0}" cannot be converted to a boolean (true/false) value. - The string "{0}" cannot be converted to a boolean (true/false) value. + "{0}" dizesi bir boole (doğru/yanlış) değerine dönüştürülemiyor. MSB5003: Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - MSB5003: Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} + MSB5003: Geçici bir dosya oluşturulamadı. Geçici dosyalar klasörü dolu veya yolu hatalı. {0} {StrBegin="MSB5003: "} MSB5018: Failed to delete the temporary file "{0}". {1} {2} - MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: "{0}" geçici dosyası silinemedi. {1} {2} {StrBegin="MSB5018: "} - - An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - - The item metadata "%({0})" cannot be applied to the path "{1}". {2} - The item metadata "%({0})" cannot be applied to the path "{1}". {2} + "%({0})" öğe meta verisi "{1}" yoluna uygulanamıyor. {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. - - MSB5019: The project file is malformed: "{0}". {1} - MSB5019: The project file is malformed: "{0}". {1} - {StrBegin="MSB5019: "} + + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. + MSB4077: "{0}" görevi LoadInSeparateAppDomain özniteliğiyle işaretlenmiş, ancak MarshalByRefObject öğesinden türetilmiyor. Görevin MarshalByRefObject veya AppDomainIsolatedTask öğesinden türetildiğini denetleyin. + {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. + + + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework "{0}" sürümü desteklenmiyor. Lütfen Microsoft.Build.Utilities.TargetDotNetFrameworkVersion sabit listesinden bir değer belirtin. + + + + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. + Yalnızca .NET 4.5 ve sonraki sürümlerde desteklenen Windows SDK açıkça hedeflenirken .NET Framework "{0}" sürümü desteklenmez. Lütfen Microsoft.Build.Utilities.TargetDotNetFrameworkVersion sabit listesinden Sürüm 45 veya üzerinde bir değer belirtin. + + + + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. + Visual Studio "{0}" sürümü desteklenmiyor. Lütfen Microsoft.Build.Utilities.VisualStudioVersion sabit listesinden bir değer belirtin. + + + + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} + "{0}" yolundan ve "{1}" framework adından bir başvuru bütünleştirilmiş kod yolu oluşturmaya çalışılırken bir hata oluştu. {2} + No Error code because this resource will be used in an exception. The error code is discarded if it is included + + + Could not find directory path: {0} + Dizin yolu bulunamadı: {0} + Directory must exist + + + You do not have access to: {0} + Şu öğeye erişiminiz yok: {0} + Directory must have access + + + Schema validation + Şema doğrulama + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. - MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: "{0}" görev yürütülebilir dosyası belirtilen {1} milisaniye sınırı içinde tamamlanmadığından sonlandırılıyor. {StrBegin="MSB5002: "} - - MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. - MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. - {StrBegin="MSB5021: "} - Parameter "{0}" cannot be null. - Parameter "{0}" cannot be null. - - - - Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. - Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + "{0}" parametresi null olamaz. Parameter "{0}" cannot have zero length. - Parameter "{0}" cannot have zero length. + "{0}" parametresinin uzunluğu sıfır olamaz. Parameters "{0}" and "{1}" must have the same number of elements. - Parameters "{0}" and "{1}" must have the same number of elements. + "{0}" ve "{1}" parametrelerinin öğe sayıları aynı olmalıdır. - - Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - - - - MSB5020: Could not load the project file: "{0}". {1} - MSB5020: Could not load the project file: "{0}". {1} - {StrBegin="MSB5020: "} - The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. - The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + "{1}" görevi için "{0}" kaynak dizesi bulunamıyor. "{0}" kaynak adının doğru yazıldığını ve kaynağın görevin bütünleştirilmiş kodunda bulunduğunu doğrulayın. The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. - The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + "{0}" görevi, kaynaklarını kaydetmedi. "TaskLoggingHelper.FormatResourceString()" metodunu kullanmak için, bu görevin oluşturma sırasında veya "TaskResources" özelliği aracılığıyla kaynaklarını kaydetmesi gerekir. LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. - - MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". - MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". - {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. - - - MSB5025: Json in solution filter file "{0}" is incorrectly formatted. - MSB5025: Json in solution filter file "{0}" is incorrectly formatted. - {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. - - - MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. - MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. - {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. - MSB5004: The solution file has two projects named "{0}". - MSB5004: The solution file has two projects named "{0}". + MSB5004: Çözüm dosyasında "{0}" adlı iki proje var. {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. - MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: "{0}" projesi için proje bölümü ayrıştırma hatası. "{1}" proje dosyası adı geçersiz karakterler içeriyor. {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. MSB5006: Error parsing project section for project "{0}". The project file name is empty. - MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: "{0}" projesi için proje bölümü ayrıştırma hatası. Proje dosyası adı boş. {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. - MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Çözüm dosyasında proje yapılandırma bölümünü ayrıştırma hatası. "{0}" girdisi geçersiz. {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. - MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Çözüm dosyasında çözüm yapılandırma bölümünü ayrıştırma hatası. "{0}" girdisi geçersiz. {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. MSB5009: Error parsing the nested project section in solution file. - MSB5009: Error parsing the nested project section in solution file. - {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. - - - MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. - MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Çözüm dosyasındaki iç içe proje bölümünü ayrıştırma hatası oluştu. {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. - MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Çözüm dosyasındaki iç içe proje bölümünü ayrıştırma hatası. GUID’si "{0}" olan bir proje, "{1}" projesi altında iç içe olarak listelendi, ancak çözümde yok. {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. MSB5010: No file format header found. - MSB5010: No file format header found. + MSB5010: Dosya biçimi üstbilgisi bulunamadı. {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. MSB5011: Parent project GUID not found in "{0}" project dependency section. - MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Üst proje GUID'i, "{0}" proje bağımlılığı bölümünde bulunamadı. {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. MSB5012: Unexpected end-of-file reached inside "{0}" project section. - MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: "{0}" proje bölümünde beklenmeyen şekilde dosya sonuna ulaşıldı. {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. MSB5013: Error parsing a project section. - MSB5013: Error parsing a project section. + MSB5013: Proje bölümünü ayrıştırma hatası oluştu. {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. - MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: Dosya biçimi sürümü tanınmıyor. MSBuild yalnızca {0}.0 ile {1}.0 (dahil) sürümleri arasındaki çözüm dosyalarını okuyabilir. {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. - MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: Özellikler, "{0}" projesinin WebsiteProperties bölümünden okunamadı. {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. - - Schema validation - Schema validation - - UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is - displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: - "MSBUILD : Schema validation error MSB0000: This is an error." - LOCALIZATION: This fragment needs to be localized. - + + Unrecognized solution version "{0}", attempting to continue. + Tanınmayan çözüm sürümü "{0}"; devam edilmeye çalışılıyor. + Solution file - Solution file + Çözüm dosyası UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: "MSBUILD : Solution file error MSB0000: This is an error." LOCALIZATION: This fragment needs to be localized. - - MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: Proje dosyası yanlış biçimlendirilmiş: "{0}". {1} + {StrBegin="MSB5019: "} - - You do not have access to: {0} - You do not have access to: {0} - Directory must have access + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Proje dosyası yüklenemedi: "{0}". {1} + {StrBegin="MSB5020: "} - - Unrecognized solution version "{0}", attempting to continue. - Unrecognized solution version "{0}", attempting to continue. + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Derleme iptal edildiğinden "{0}" görev yürütülebilir dosyası ve bunun alt öğeleri sonlandırılıyor. + {StrBegin="MSB5021: "} + + + This collection is read-only. + Bu koleksiyon salt okunur. - - MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. - MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. - {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + MSB5024: Could not determine a valid location to MSBuild. Try running this process from the Developer Command Prompt for Visual Studio. + MSB5024: MSBuild için geçerli bir konum belirlenemedi. Bu işlemi Visual Studio için Geliştirici Komut İstemi’nde çalıştırmayı deneyin. + {StrBegin="MSB5024: "} + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: Günlük dosyası okunurken bir özel durum oluştu: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + "{1}" değeri atanan "{0}" parametresinde geçersiz yol veya geçersiz dosya karakterleri bulunamaz. + + + + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} + globs: fileSpec: "{0}" ile bir fileSpec genişletilirken özel bir durum oluştu, bunun bir dosya adı olduğu varsayıldı. Özel Durum: {1} + MSB5029: The value "{0}" of the "{1}" attribute in element <{2}> in file "{3}" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always defined and that the project and current working directory are not at the drive root. - MSB5029: The value "{0}" of the "{1}" attribute in element <{2}> in file "{3}" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always defined and that the project and current working directory are not at the drive root. + MSB5029: "{0}" dosyasındaki <{1}> öğesinde "{2}" özniteliğinin "{3}" değeri, sürücüdeki tüm dosyaların numaralandırılmasıyla sonuçlanan (büyük olasılıkla bunun olması amaçlanmıyordu) bir joker karakterdir. Başvurulan özelliklerin her zaman tanımlandığını ve projenin ve geçerli çalışma dizininin sürücü kökünde bulunmadığını kontrol edin. {StrBegin="MSB5029: "}UE: This is a generic message that is displayed when we find a project element that has a drive enumerating wildcard value for one of its attributes e.g. <Compile Include="$(NotAlwaysDefined)\**\*.cs"> -- if the property is undefined, the value of Include should not result in enumerating all files on drive.