From b1452c8fcab789dd9f2921c1479425b291111c5d Mon Sep 17 00:00:00 2001
From: dotnet bot
Date: Thu, 15 Jul 2021 13:07:34 -0700
Subject: [PATCH] Localized file check-in by OneLocBuild Task: Build definition
ID 679: Build ID 1240010 (#55743)
* Localized file check-in by OneLocBuild Task
* Remove asserts against localized text from Logging generator tests
Co-authored-by: Eric StJohn
---
.../Microsoft.CSharp.cs.xlf | 360 ++++++++++++++++++
.../Microsoft.CSharp.de.xlf | 179 ++++-----
.../Microsoft.CSharp.es.xlf | 179 ++++-----
.../Microsoft.CSharp.fr.xlf | 179 ++++-----
.../Microsoft.CSharp.it.xlf | 179 ++++-----
.../Microsoft.CSharp.ja.xlf | 179 ++++-----
.../Microsoft.CSharp.ko.xlf | 179 ++++-----
.../Microsoft.CSharp.pl.xlf | 360 ++++++++++++++++++
.../Microsoft.CSharp.pt-BR.xlf | 360 ++++++++++++++++++
.../Microsoft.CSharp.ru.xlf | 179 ++++-----
.../Microsoft.CSharp.tr.xlf | 360 ++++++++++++++++++
.../Microsoft.CSharp.zh-Hans.xlf | 183 +++++----
.../Microsoft.CSharp.zh-Hant.xlf | 185 ++++-----
.../gen/Resources/xlf/Strings.cs.xlf | 62 +--
.../gen/Resources/xlf/Strings.de.xlf | 62 +--
.../gen/Resources/xlf/Strings.es.xlf | 62 +--
.../gen/Resources/xlf/Strings.fr.xlf | 62 +--
.../gen/Resources/xlf/Strings.it.xlf | 62 +--
.../gen/Resources/xlf/Strings.ja.xlf | 62 +--
.../gen/Resources/xlf/Strings.ko.xlf | 62 +--
.../gen/Resources/xlf/Strings.pl.xlf | 62 +--
.../gen/Resources/xlf/Strings.pt-BR.xlf | 62 +--
.../gen/Resources/xlf/Strings.ru.xlf | 62 +--
.../gen/Resources/xlf/Strings.tr.xlf | 62 +--
.../gen/Resources/xlf/Strings.zh-Hans.xlf | 62 +--
.../gen/Resources/xlf/Strings.zh-Hant.xlf | 62 +--
.../LoggerMessageGeneratorParserTests.cs | 12 +-
.../gen/Resources/xlf/Strings.cs.xlf | 12 +-
.../gen/Resources/xlf/Strings.de.xlf | 12 +-
.../gen/Resources/xlf/Strings.es.xlf | 12 +-
.../gen/Resources/xlf/Strings.fr.xlf | 12 +-
.../gen/Resources/xlf/Strings.it.xlf | 12 +-
.../gen/Resources/xlf/Strings.ja.xlf | 12 +-
.../gen/Resources/xlf/Strings.ko.xlf | 12 +-
.../gen/Resources/xlf/Strings.pl.xlf | 12 +-
.../gen/Resources/xlf/Strings.pt-BR.xlf | 12 +-
.../gen/Resources/xlf/Strings.ru.xlf | 12 +-
.../gen/Resources/xlf/Strings.tr.xlf | 12 +-
.../gen/Resources/xlf/Strings.zh-Hans.xlf | 12 +-
.../gen/Resources/xlf/Strings.zh-Hant.xlf | 12 +-
40 files changed, 2741 insertions(+), 1294 deletions(-)
create mode 100644 src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.cs.xlf
create mode 100644 src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.pl.xlf
create mode 100644 src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.pt-BR.xlf
create mode 100644 src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.tr.xlf
diff --git a/src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.cs.xlf b/src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.cs.xlf
new file mode 100644
index 0000000000000..ae56c2a140d55
--- /dev/null
+++ b/src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.cs.xlf
@@ -0,0 +1,360 @@
+
+
+
+
+
+
+
+
+
+ An unexpected exception occurred while binding a dynamic operation
+ Při vytváření vazby dynamické operace došlo k neočekávané výjimce.
+
+
+ Cannot bind call with no calling object
+ Nelze vytvořit volání vazby s objektem neúčastnícím se volání.
+
+
+ Overload resolution failed
+ Rozlišení přetěžování neproběhlo úspěšně.
+
+
+ Binary operators must be invoked with two arguments
+ Binární operátory je nutné volat se dvěma argumenty.
+
+
+ Unary operators must be invoked with one argument
+ Unární operátory je nutné volat s jedním argumentem.
+
+
+ The name '{0}' is bound to a method and cannot be used like a property
+ Název {0} je vázán na metodu a nemůže být použit jako vlastnost.
+
+
+ The event '{0}' can only appear on the left hand side of +
+ Událost {0} se může vyskytnout pouze na levé straně výrazu +.
+
+
+ Cannot invoke a non-delegate type
+ Nelze volat nedelegující typ.
+
+
+ Binary operators cannot be invoked with one argument
+ Binární operátory nelze volat s jedním argumentem.
+
+
+ Cannot perform member assignment on a null reference
+ U nulového odkazu nelze provést přiřazení členů.
+
+
+ Cannot perform runtime binding on a null reference
+ U nulového odkazu nelze provést vazbu za běhu.
+
+
+ Cannot dynamically invoke method '{0}' because it has a Conditional attribute
+ Nelze dynamicky volat metodu {0}, protože má atribut Conditional.
+
+
+ Cannot implicitly convert type 'void' to 'object'
+ Nelze implicitně převést typ void na object.
+
+
+ Operator '{0}' cannot be applied to operands of type '{1}' and '{2}'
+ Operátor {0} nelze použít na operandy typu {1} a {2}.
+
+
+ Cannot apply indexing with [] to an expression of type '{0}'
+ Ve výrazu typu {0} nelze použít indexování pomocí hranatých závorek ([]).
+
+
+ Wrong number of indices inside []; expected '{0}'
+ Uvnitř hranatých závorek ([]) byl nalezen nesprávný počet indexů. Očekávaný počet indexů: {0}
+
+
+ Operator '{0}' cannot be applied to operand of type '{1}'
+ Operátor {0} nelze použít na operand typu {1}.
+
+
+ Cannot implicitly convert type '{0}' to '{1}'
+ Typ {0} nelze implicitně převést na typ {1}.
+
+
+ Cannot convert type '{0}' to '{1}'
+ Typ {0} nelze převést na typ {1}.
+
+
+ Constant value '{0}' cannot be converted to a '{1}'
+ Konstantní hodnotu {0} nelze převést na typ {1}.
+
+
+ Operator '{0}' is ambiguous on operands of type '{1}' and '{2}'
+ Operátor {0} je nejednoznačný na operandech typu {1} a {2}.
+
+
+ Operator '{0}' is ambiguous on an operand of type '{1}'
+ Operátor {0} je nejednoznačný na operandu typu {1}.
+
+
+ Cannot convert null to '{0}' because it is a non-nullable value type
+ Hodnotu null nelze převést na typ {0}, protože se jedná o typ, který nepovoluje hodnotu null.
+
+
+ Cannot access a non-static member of outer type '{0}' via nested type '{1}'
+ Pomocí vnořeného typu {1} nelze přistupovat k nestatickému členu vnějšího typu {0}.
+
+
+ '{0}' does not contain a definition for '{1}'
+ {0} neobsahuje definici pro {1}.
+
+
+ An object reference is required for the non-static field, method, or property '{0}'
+ Pro nestatické pole, metodu nebo vlastnost {0} je vyžadován odkaz na objekt.
+
+
+ The call is ambiguous between the following methods or properties: '{0}' and '{1}'
+ Volání je nejednoznačné mezi následujícími metodami nebo vlastnostmi: {0} a {1}
+
+
+ '{0}' is inaccessible due to its protection level
+ Typ {0} je vzhledem k úrovni ochrany nepřístupný.
+
+
+ No overload for '{0}' matches delegate '{1}'
+ Žádná přetížená metoda {0} neodpovídá delegátovi {1}.
+
+
+ The left-hand side of an assignment must be a variable, property or indexer
+ Levou stranou přiřazení musí být proměnná, vlastnost nebo indexer.
+
+
+ The type '{0}' has no constructors defined
+ Pro typ {0} nebyly definovány žádné konstruktory.
+
+
+ The property or indexer '{0}' cannot be used in this context because it lacks the get accessor
+ Vlastnost nebo indexer {0} nelze v tomto kontextu použít, protože neobsahuje přistupující objekt get.
+
+
+ Member '{0}' cannot be accessed with an instance reference; qualify it with a type name instead
+ K členovi {0} nelze přistupovat pomocí odkazu na instanci. Namísto toho použijte kvalifikaci pomocí názvu typu.
+
+
+ A readonly field cannot be assigned to (except in a constructor or a variable initializer)
+ Do pole readonly nejde přiřazovat (kromě případu, kdy se nachází uvnitř konstruktoru nebo inicializátoru proměnné).
+
+
+ A readonly field cannot be passed ref or out (except in a constructor)
+ Pole určené jen pro čtení nejde předat jako parametr Ref nebo Out (kromě případu, kdy se nachází uvnitř konstruktoru).
+
+
+ A static readonly field cannot be assigned to (except in a static constructor or a variable initializer)
+ Do statického pole určeného jen pro čtení nejde přiřazovat (kromě případu, kdy se nachází uvnitř statického konstruktoru nebo inicializátoru proměnné).
+
+
+ A static readonly field cannot be passed ref or out (except in a static constructor)
+ Statické pole určené jen pro čtení nejde předat jako parametr Ref nebo Out (kromě případu, kdy se nachází uvnitř statického konstruktoru).
+
+
+ Property or indexer '{0}' cannot be assigned to -- it is read only
+ Vlastnost nebo indexer {0} nelze přiřadit – je jen pro čtení.
+
+
+ A property or indexer may not be passed as an out or ref parameter
+ Vlastnost nebo indexer nelze předat jako parametr ref nebo out.
+
+
+ Dynamic calls cannot be used in conjunction with pointers
+ Dynamická volání nelze použít v kombinaci s ukazateli.
+
+
+ In order to be applicable as a short circuit operator a user-defined logical operator ('{0}') must have the same return type as the type of its 2 parameters
+ Má-li být uživatelem definovaný logický operátor ({0}) použitelný jako operátor zkráceného vyhodnocení, musí vracet hodnotu stejného typu jako jeho dva parametry.
+
+
+ The type ('{0}') must contain declarations of operator true and operator false
+ Typ ({0}) musí obsahovat deklarace operátorů true a false.
+
+
+ Constant value '{0}' cannot be converted to a '{1}' (use 'unchecked' syntax to override)
+ Konstantní hodnotu {0} nelze převést na typ {1} (k přepsání lze použít syntaxi unchecked).
+
+
+ Ambiguity between '{0}' and '{1}'
+ Došlo k nejednoznačnosti mezi metodami nebo vlastnostmi {0} a {1}.
+
+
+ Cannot implicitly convert type '{0}' to '{1}'. An explicit conversion exists (are you missing a cast?)
+ Typ {0} nelze implicitně převést na typ {1}. Existuje explicitní převod. (Nechybí výraz přetypování?)
+
+
+ The property or indexer '{0}' cannot be used in this context because the get accessor is inaccessible
+ Vlastnost nebo indexer {0} nelze v tomto kontextu použít, protože přistupující objekt get není dostupný.
+
+
+ The property or indexer '{0}' cannot be used in this context because the set accessor is inaccessible
+ Vlastnost nebo indexer {0} nelze v tomto kontextu použít, protože přistupující objekt jet není dostupný.
+
+
+ Using the generic {1} '{0}' requires '{2}' type arguments
+ Použití obecné možnosti {1} {0} vyžaduje argumenty typu {2}.
+
+
+ The {1} '{0}' cannot be used with type arguments
+ {1} {0} nelze použít s argumenty typů.
+
+
+ The non-generic {1} '{0}' cannot be used with type arguments
+ Neobecnou možnost {1} {0} nelze použít s argumenty typů.
+
+
+ '{2}' must be a non-abstract type with a public parameterless constructor in order to use it as parameter '{1}' in the generic type or method '{0}'
+ Objekt {2} musí být neabstraktního typu s veřejným konstruktorem bez parametrů, jinak jej nelze použít jako parametr {1} v obecném typu nebo metodě {0}.
+
+
+ The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no implicit reference conversion from '{3}' to '{1}'.
+ Typ {3} nelze použít jako parametr typu {2} v obecném typu nebo metodě {0}. Neexistuje žádný implicitní převod odkazu z {3} na {1}.
+
+
+ The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not satisfy the constraint of '{1}'.
+ Typ {3} nelze použít jako parametr typu {2} v obecném typu nebo metodě {0}. Typ {3} s možnou hodnotou null nevyhovuje omezení {1}.
+
+
+ The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not satisfy the constraint of '{1}'. Nullable types can not satisfy any interface constraints.
+ Typ {3} nelze použít jako parametr typu {2} v obecném typu nebo metodě {0}. Typ {3} s možnou hodnotou null nevyhovuje omezení {1}. Typy s možnou hodnotou null nemohou vyhovět žádným omezením rozhraní.
+
+
+ The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no boxing conversion from '{3}' to '{1}'.
+ Typ {3} nelze použít jako parametr typu {2} v obecném typu nebo metodě {0}. Neexistuje žádný převod na uzavřené určení z {3} na {1}.
+
+
+ The type arguments for method '{0}' cannot be inferred from the usage. Try specifying the type arguments explicitly.
+ Argumenty typu pro metodu {0} nelze stanovit z použití. Zadejte argumenty typu explicitně.
+
+
+ The type '{2}' must be a reference type in order to use it as parameter '{1}' in the generic type or method '{0}'
+ Typ {2} musí být typ odkazu, aby ho bylo možné používat jako parametr {1} v obecném typu nebo metodě {0}.
+
+
+ The type '{2}' must be a non-nullable value type in order to use it as parameter '{1}' in the generic type or method '{0}'
+ Typ {2} musí být typ, který nepovoluje hodnotu null, aby ho bylo možné používat jako parametr {1} v obecném typu nebo metodě {0}.
+
+
+ Ambiguous user defined conversions '{0}' and '{1}' when converting from '{2}' to '{3}'
+ Při převodu typu {2} na typ {3} došlo k uživatelem definovaným nejednoznačným převodům typu {0} na typ {1}.
+
+
+ '{0}' is not supported by the language
+ {0} není tímto jazykem podporovaný.
+
+
+ '{0}': cannot explicitly call operator or accessor
+ {0}: Nejde explicitně volat operátor nebo přistupující objekt.
+
+
+ Cannot convert to static type '{0}'
+ Nelze převést na statický typ {0}.
+
+
+ The operand of an increment or decrement operator must be a variable, property or indexer
+ Operandem operátoru přičtení nebo odečtení musí být proměnná, vlastnost nebo indexer.
+
+
+ No overload for method '{0}' takes '{1}' arguments
+ Žádná přetížená metoda {0} nepoužívá tento počet argumentů ({1}).
+
+
+ The best overloaded method match for '{0}' has some invalid arguments
+ Některé argumenty přetěžované metody, která je nejlepší shodou pro deklaraci {0}, jsou neplatné.
+
+
+ A ref or out argument must be an assignable variable
+ Argumentem ref nebo out musí být proměnná s možností přiřazení hodnoty
+
+
+ Cannot access protected member '{0}' via a qualifier of type '{1}'; the qualifier must be of type '{2}' (or derived from it)
+ K chráněnému členu {0} nelze přistupovat prostřednictvím kvalifikátoru typu {1}. Kvalifikátor musí být typu {2} (nebo musí být od tohoto typu odvozen).
+
+
+ Property, indexer, or event '{0}' is not supported by the language; try directly calling accessor methods '{1}' or '{2}'
+ Vlastnost, indexer nebo událost {0} nejsou tímto jazykem podporovány. Zkuste přímo volat metody přistupujícího objektu {1} nebo {2}.
+
+
+ Property, indexer, or event '{0}' is not supported by the language; try directly calling accessor method '{1}'
+ Vlastnost, indexer nebo událost {0} nejsou tímto jazykem podporovány. Zkuste přímo volat metodu přistupujícího objektu {1}.
+
+
+ Delegate '{0}' does not take '{1}' arguments
+ Počet argumentů delegáta {0} neodpovídá (počet: {1}).
+
+
+ Delegate '{0}' has some invalid arguments
+ Některé argumenty delegáta {0} jsou neplatné.
+
+
+ Cannot assign to '{0}' because it is read-only
+ K položce nelze přiřadit {0} protože je jen pro čtení.
+
+
+ Cannot pass '{0}' as a ref or out argument because it is read-only
+ Element {0} nelze předat jako argument Ref nebo Out, protože je jen pro čtení.
+
+
+ Cannot modify the return value of '{0}' because it is not a variable
+ Vrácenou hodnotu {0} nelze změnit, protože se nejedná o proměnnou.
+
+
+ Members of readonly field '{0}' cannot be modified (except in a constructor or a variable initializer)
+ Členy pole jen pro čtení {0} nelze měnit (kromě případu, kdy se nacházejí uvnitř konstruktoru nebo inicializátoru proměnné).
+
+
+ Members of readonly field '{0}' cannot be passed ref or out (except in a constructor)
+ Členy pole jen pro čtení {0} nelze předat jako parametr Ref nebo Out (kromě případu, kdy se nacházejí uvnitř konstruktoru).
+
+
+ Fields of static readonly field '{0}' cannot be assigned to (except in a static constructor or a variable initializer)
+ Pole statických polí jen pro čtení {0} nelze přiřadit (kromě případu, kdy se nacházejí uvnitř statického konstruktoru nebo inicializátoru proměnné).
+
+
+ Fields of static readonly field '{0}' cannot be passed ref or out (except in a static constructor)
+ Pole statického pole jen pro čtení {0} nelze předat jako parametr Ref nebo Out (kromě případu, kdy se nacházejí uvnitř statického konstruktoru).
+
+
+ Cannot assign to '{0}' because it is a '{1}'
+ K položce nelze přiřadit {0} protože je typu {1}.
+
+
+ Cannot pass '{0}' as a ref or out argument because it is a '{1}'
+ Element {0} nelze předat jako argument Ref nebo Out, protože je {1}.
+
+
+ '{0}' does not contain a constructor that takes '{1}' arguments
+ {0} neobsahuje konstruktor daným počtem vstupních argumentů ({1}).
+
+
+ Non-invocable member '{0}' cannot be used like a method.
+ Nevyvolatelného člena {0} nelze použít jako metodu.
+
+
+ Named argument specifications must appear after all fixed arguments have been specified
+ Specifikace pojmenovaných argumentů musí následovat po specifikaci všech pevných argumentů
+
+
+ The best overload for '{0}' does not have a parameter named '{1}'
+ Nejlepší přetížení pro {0} neobsahuje parametr s názvem {1}.
+
+
+ The delegate '{0}' does not have a parameter named '{1}'
+ Delegát {0} neobsahuje parametr s názvem {1}.
+
+
+ Named argument '{0}' cannot be specified multiple times
+ Pojmenovaný argument {0} nelze zadat vícekrát.
+
+
+ Named argument '{0}' specifies a parameter for which a positional argument has already been given
+ Pojmenovaný argument {0} určuje parametr, pro který již byl poskytnut poziční argument.
+
+
+
+
+
\ No newline at end of file
diff --git a/src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.de.xlf b/src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.de.xlf
index 3f030fd1ef80f..d95dd6a6e6df8 100644
--- a/src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.de.xlf
+++ b/src/libraries/Microsoft.CSharp/src/MultilingualResources/Microsoft.CSharp.de.xlf
@@ -1,4 +1,5 @@
-
+
+
@@ -7,353 +8,353 @@
An unexpected exception occurred while binding a dynamic operation
- Unerwartete Ausnahme beim Binden eines dynamischen Vorgangs
+ Unerwartete Ausnahme beim Binden eines dynamischen VorgangsCannot bind call with no calling object
- Ein Aufruf ohne aufrufendes Objekt kann nicht gebunden werden.
+ Ein Aufruf ohne aufrufendes Objekt kann nicht gebunden werden.Overload resolution failed
- Fehler bei der Überladungsauflösung
+ Fehler bei der Überladungsauflösung.Binary operators must be invoked with two arguments
- Binäre Operatoren müssen mit zwei Argumenten aufgerufen werden.
+ Binäre Operatoren müssen mit zwei Argumenten aufgerufen werden.Unary operators must be invoked with one argument
- Unäre Operatoren müssen mit einem Argument aufgerufen werden.
+ Unäre Operatoren müssen mit einem Argument aufgerufen werden.The name '{0}' is bound to a method and cannot be used like a property
- Der Name "{0}" ist an eine Methode gebunden und kann nicht wie eine Eigenschaft verwendet werden.
+ Der Name "{0}" ist an eine Methode gebunden und kann nicht wie eine Eigenschaft verwendet werden.The event '{0}' can only appear on the left hand side of +
- Das Ereignis "{0}" kann nur verwendet werden, auf der linken Seite des +
+ Das Ereignis "{0}" kann nur links von "+" verwendet werden.Cannot invoke a non-delegate type
- Ein Nichtdelegattyp kann nicht aufgerufen werden.
+ Ein Nichtdelegattyp kann nicht aufgerufen werden.Binary operators cannot be invoked with one argument
- Binäre Operatoren können nicht mit einem Argument aufgerufen werden.
+ Binäre Operatoren können nicht mit einem Argument aufgerufen werden.Cannot perform member assignment on a null reference
- Für einen NULL-Verweis kann keine Memberzuweisung ausgeführt werden.
+ Für einen NULL-Verweis kann keine Memberzuweisung ausgeführt werden.Cannot perform runtime binding on a null reference
- Die Laufzeitbindung kann für einen NULL-Verweis nicht ausgeführt werden.
+ Die Laufzeitbindung kann für einen NULL-Verweis nicht ausgeführt werden.Cannot dynamically invoke method '{0}' because it has a Conditional attribute
- Die {0}-Methode kann nicht dynamisch aufgerufen werden, da sie ein Conditional-Attribut enthält.
+ Die {0}-Methode kann nicht dynamisch aufgerufen werden, da sie ein Conditional-Attribut enthält.Cannot implicitly convert type 'void' to 'object'
- Der Typ "void" kann nicht implizit in "object" konvertiert werden.
+ Der Typ "void" kann nicht implizit in "object" konvertiert werden.Operator '{0}' cannot be applied to operands of type '{1}' and '{2}'
- Der {0}-Operator kann nicht auf Operanden vom Typ "{1}" und "{2}" angewendet werden.
+ Der {0}-Operator kann nicht auf Operanden vom Typ "{1}" und "{2}" angewendet werden.Cannot apply indexing with [] to an expression of type '{0}'
- Eine Indizierung mit [] kann nicht auf einen Ausdruck vom Typ "{0}" angewendet werden.
+ Eine Indizierung mit [] kann nicht auf einen Ausdruck vom Typ "{0}" angewendet werden.Wrong number of indices inside []; expected '{0}'
- Falsche Indexanzahl in []. {0} wurde erwartet
+ Falsche Indexanzahl in []. {0} wurde erwartetOperator '{0}' cannot be applied to operand of type '{1}'
- Der {0}-Operator kann nicht auf einen Operanden vom Typ "{1}" angewendet werden.
+ Der {0}-Operator kann nicht auf einen Operanden vom Typ "{1}" angewendet werden.Cannot implicitly convert type '{0}' to '{1}'
- Der {0}-Typ kann nicht implizit in {1} konvertiert werden.
+ Der {0}-Typ kann nicht implizit in {1} konvertiert werden.Cannot convert type '{0}' to '{1}'
- Der {0}-Typ kann nicht in {1} konvertiert werden.
+ Der {0}-Typ kann nicht in {1} konvertiert werden.Constant value '{0}' cannot be converted to a '{1}'
- Der Konstantenwert "{0}" kann nicht in {1} konvertiert werden.
+ Der Konstantenwert "{0}" kann nicht in {1} konvertiert werden.Operator '{0}' is ambiguous on operands of type '{1}' and '{2}'
- Der {0}-Operator ist bei Operanden vom Typ "{1}" und "{2}" mehrdeutig.
+ Der {0}-Operator ist bei Operanden vom Typ "{1}" und "{2}" mehrdeutig.Operator '{0}' is ambiguous on an operand of type '{1}'
- Der {0}-Operator ist für einen Operanden vom Typ "{1}" mehrdeutig.
+ Der {0}-Operator ist für einen Operanden vom Typ "{1}" mehrdeutig.Cannot convert null to '{0}' because it is a non-nullable value type
- NULL kann nicht in {0} konvertiert werden, da dieser Werttyp nicht auf NULL festgelegt werden kann.
+ NULL kann nicht in {0} konvertiert werden, da dieser Werttyp nicht auf NULL festgelegt werden kann.Cannot access a non-static member of outer type '{0}' via nested type '{1}'
- Auf einen nicht statischen Member des äußeren {0}-Typs kann nicht über den geschachtelten {1}-Typ zugegriffen werden.
+ Auf einen nicht statischen Member des äußeren {0}-Typs kann nicht über den geschachtelten {1}-Typ zugegriffen werden.'{0}' does not contain a definition for '{1}'
- {0} enthält keine Definition für {1}.
+ "{0}" enthält keine Definition für "{1}".An object reference is required for the non-static field, method, or property '{0}'
- Für das nicht statische Feld, die Methode oder die Eigenschaft "{0}" ist ein Objektverweis erforderlich.
+ Für das nicht statische Feld, die Methode oder die Eigenschaft "{0}" ist ein Objektverweis erforderlich.The call is ambiguous between the following methods or properties: '{0}' and '{1}'
- Der Aufruf unterscheidet nicht eindeutig zwischen den folgenden Methoden oder Eigenschaften: {0} und {1}
+ Der Aufruf unterscheidet nicht eindeutig zwischen den folgenden Methoden oder Eigenschaften: {0} und {1}'{0}' is inaccessible due to its protection level
- Der Zugriff auf "{0}" ist aufgrund des Schutzgrads nicht möglich.
+ Der Zugriff auf "{0}" ist aufgrund des Schutzgrads nicht möglich.No overload for '{0}' matches delegate '{1}'
- Keine Überladung für {0} stimmt mit dem Delegaten "{1}" überein.
+ Keine Überladung für {0} stimmt mit dem Delegaten "{1}" überein.The left-hand side of an assignment must be a variable, property or indexer
- Die linke Seite einer Zuweisung muss eine Variable, eine Eigenschaft oder ein Indexer sein.
+ Die linke Seite einer Zuweisung muss eine Variable, eine Eigenschaft oder ein Indexer sein.The type '{0}' has no constructors defined
- Für den {0}-Typ sind keine Konstruktoren definiert.
+ Für den {0}-Typ sind keine Konstruktoren definiert.The property or indexer '{0}' cannot be used in this context because it lacks the get accessor
- Die Eigenschaft oder der Indexer "{0}" kann in diesem Kontext nicht verwendet werden, weil der get-Accessor fehlt.
+ Die Eigenschaft oder der Indexer "{0}" kann in diesem Kontext nicht verwendet werden, weil der get-Accessor fehlt.Member '{0}' cannot be accessed with an instance reference; qualify it with a type name instead
- Auf den Member "{0}" kann nicht mit einem Instanzverweis zugegriffen werden. Qualifizieren Sie ihn stattdessen mit einem Typnamen.
+ Auf den Member "{0}" kann nicht mit einem Instanzverweis zugegriffen werden. Qualifizieren Sie ihn stattdessen mit einem Typnamen.A readonly field cannot be assigned to (except in a constructor or a variable initializer)
- Einem schreibgeschützten Feld kann nichts zugewiesen werden (außer in einem Konstruktor oder Variableninitialisierer).
+ Für ein schreibgeschütztes Feld ist eine Zuweisung nicht möglich (außer in einem Konstruktor oder Variableninitialisierer).A readonly field cannot be passed ref or out (except in a constructor)
- Einem schreibgeschützten Feld kann kein Verweis und keine Ausgabe übergeben werden (außer in einem Konstruktor).
+ An ein schreibgeschütztes Feld können keine ref- oder out-Argumente übergeben werden (außer in einem Konstruktor).A static readonly field cannot be assigned to (except in a static constructor or a variable initializer)
- Einem statischen, schreibgeschützten Feld kann nichts zugewiesen werden (außer in einem statischen Konstruktor oder einem Variableninitialisierer).
+ Für ein statisches schreibgeschütztes Feld ist eine Zuweisung nicht möglich (außer in einem statischen Konstruktor oder einem Variableninitialisierer).A static readonly field cannot be passed ref or out (except in a static constructor)
- Einem statischen, schreibgeschützten Feld kann kein Verweis und keine Ausgabe übergeben werden (außer in einem statischen Konstruktor)
+ An ein statisches schreibgeschütztes Feld können keine ref- oder out-Argumente übergeben werden (außer in einem Konstruktor).Property or indexer '{0}' cannot be assigned to -- it is read only
- Für die Eigenschaft oder den Indexer "{0}" ist eine Zuweisung nicht möglich -- sie sind schreibgeschützt.
+ Für die Eigenschaft oder den Indexer "{0}" ist eine Zuweisung nicht möglich -- sie sind schreibgeschützt.A property or indexer may not be passed as an out or ref parameter
- Eine Eigenschaft oder ein Indexer kann nicht als out- oder ref-Parameter übergeben werden.
+ Eine Eigenschaft oder ein Indexer kann nicht als out- oder ref-Parameter übergeben werden.Dynamic calls cannot be used in conjunction with pointers
- Dynamische Aufrufe können nicht in Verbindung mit Zeigern verwendet werden.
+ Dynamische Aufrufe können nicht in Verbindung mit Zeigern verwendet werden.In order to be applicable as a short circuit operator a user-defined logical operator ('{0}') must have the same return type as the type of its 2 parameters
- Um als Kurzschlussoperator anwendbar zu sein, muss der Rückgabetyp eines benutzerdefinierten logischen Operators ({0}) mit dem Typ seiner zwei Parameter übereinstimmen.
+ Um als Kurzschlussoperator anwendbar zu sein, muss der Rückgabetyp eines benutzerdefinierten logischen Operators ({0}) mit dem Typ seiner zwei Parameter übereinstimmen.The type ('{0}') must contain declarations of operator true and operator false
- Der Typ ({0}) muss Deklarationen des True- und des False-Operators enthalten.
+ Der Typ ({0}) muss Deklarationen des True- und des False-Operators enthalten.Constant value '{0}' cannot be converted to a '{1}' (use 'unchecked' syntax to override)
- Der Konstantenwert "{0}" kann nicht in {1} konvertiert werden (verwenden Sie zum Außerkraftsetzen die unchecked-Syntax).
+ Der Konstantenwert "{0}" kann nicht in {1} konvertiert werden (verwenden Sie zum Außerkraftsetzen die unchecked-Syntax).Ambiguity between '{0}' and '{1}'
- Mehrdeutigkeit zwischen {0} und {1}
+ Mehrdeutigkeit zwischen {0} und {1}Cannot implicitly convert type '{0}' to '{1}'. An explicit conversion exists (are you missing a cast?)
- Der {0}-Typ kann nicht implizit in {1} konvertiert werden. Es ist bereits eine explizite Konvertierung vorhanden (möglicherweise fehlt eine Umwandlung).
+ Der {0}-Typ kann nicht implizit in {1} konvertiert werden. Es ist bereits eine explizite Konvertierung vorhanden (möglicherweise fehlt eine Umwandlung).The property or indexer '{0}' cannot be used in this context because the get accessor is inaccessible
- Die Eigenschaft oder der Indexer "{0}" kann in diesem Kontext nicht verwendet werden, da nicht auf den get-Accessor zugegriffen werden kann.
+ Die Eigenschaft oder der Indexer "{0}" kann in diesem Kontext nicht verwendet werden, da nicht auf den get-Accessor zugegriffen werden kann.The property or indexer '{0}' cannot be used in this context because the set accessor is inaccessible
- Die Eigenschaft oder der Indexer "{0}" kann in diesem Kontext nicht verwendet werden, da nicht auf den set-Accessor zugegriffen werden kann.
+ Die Eigenschaft oder der Indexer "{0}" kann in diesem Kontext nicht verwendet werden, da nicht auf den set-Accessor zugegriffen werden kann.Using the generic {1} '{0}' requires '{2}' type arguments
- Die Verwendung von {1} "{0}" (generisch) erfordert {2}-Typargumente.
+ Die Verwendung von {1} "{0}" (generisch) erfordert {2}-Typargumente.The {1} '{0}' cannot be used with type arguments
- {1} "{0}" kann nicht mit Typargumenten verwendet werden.
+ {1} "{0}" kann nicht mit Typargumenten verwendet werden.The non-generic {1} '{0}' cannot be used with type arguments
- {1} "{0}" ist nicht generisch und kann daher nicht mit Typargumenten verwendet werden.
+ {1} "{0}" ist nicht generisch und kann daher nicht mit Typargumenten verwendet werden.'{2}' must be a non-abstract type with a public parameterless constructor in order to use it as parameter '{1}' in the generic type or method '{0}'
- {2} muss ein nicht abstrakter Typ mit einem öffentlichen parameterlosen Konstruktor sein, um im generischen Typ oder in der generischen {0}-Methode als {1}-Parameter verwendet werden zu können.
+ "{2}" muss ein nicht abstrakter Typ mit einem öffentlichen parameterlosen Konstruktor sein, um im generischen Typ oder in der generischen {0}-Methode als {1}-Parameter verwendet werden zu können.The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no implicit reference conversion from '{3}' to '{1}'.
- Der {3}-Typ kann nicht als {2}-Typparameter im generischen Typ oder in der generischen {0}-Methode verwendet werden. Es ist keine implizite Verweiskonvertierung von {3} in {1} vorhanden.
+ Der {3}-Typ kann nicht als {2}-Typparameter im generischen Typ oder in der generischen {0}-Methode verwendet werden. Es ist keine implizite Verweiskonvertierung von {3} in {1} vorhanden.The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not satisfy the constraint of '{1}'.
- Der {3}-Typ kann nicht als {2}-Typparameter im generischen Typ oder in der generischen {0}-Methode verwendet werden. Der {3}-Typ, der NULL-Werte zulässt, entspricht nicht der Einschränkung von {1}.
+ Der {3}-Typ kann nicht als {2}-Typparameter im generischen Typ oder in der generischen {0}-Methode verwendet werden. Der {3}-Typ, der NULL-Werte zulässt, entspricht nicht der Einschränkung von {1}.The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not satisfy the constraint of '{1}'. Nullable types can not satisfy any interface constraints.
- Der {3}-Typ kann nicht als {2}-Typparameter im generischen Typ oder in der generischen {0}-Methode verwendet werden. Der {3}-Typ, der NULL-Werte zulässt, entspricht nicht der Einschränkung von {1}. Typen, die NULL-Werte zulassen, können Schnittstelleneinschränkungen nicht entsprechen.
+ Der {3}-Typ kann nicht als {2}-Typparameter im generischen Typ oder in der generischen {0}-Methode verwendet werden. Der {3}-Typ, der NULL-Werte zulässt, entspricht nicht der Einschränkung von {1}. Typen, die NULL-Werte zulassen, können Schnittstelleneinschränkungen nicht entsprechen.The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no boxing conversion from '{3}' to '{1}'.
- Der {3}-Typ kann nicht als {2}-Typparameter im generischen Typ oder in der generischen {0}-Methode verwendet werden. Es ist keine Boxing-Konvertierung von {3} in {1} vorhanden.
+ Der {3}-Typ kann nicht als {2}-Typparameter im generischen Typ oder in der generischen {0}-Methode verwendet werden. Es ist keine Boxing-Konvertierung von {3} in {1} vorhanden.The type arguments for method '{0}' cannot be inferred from the usage. Try specifying the type arguments explicitly.
- Die Typargumente der {0}-Methode können nicht per Rückschluss aus der Syntax abgeleitet werden. Geben Sie die Typargumente explizit an.
+ Die Typargumente der {0}-Methode können nicht per Rückschluss aus der Syntax abgeleitet werden. Geben Sie die Typargumente explizit an.The type '{2}' must be a reference type in order to use it as parameter '{1}' in the generic type or method '{0}'
- Der {2}-Typ muss ein Referenztyp sein, damit er als {1}-Parameter im generischen Typ oder in der generischen {0}-Methode verwendet werden kann.
+ Der {2}-Typ muss ein Referenztyp sein, damit er als {1}-Parameter im generischen Typ oder in der generischen {0}-Methode verwendet werden kann.The type '{2}' must be a non-nullable value type in order to use it as parameter '{1}' in the generic type or method '{0}'
- Der {2}-Typ darf keine NULL-Werte zulassen, wenn er als {1}-Parameter im generischen Typ oder in der generischen {0}-Methode verwendet werden soll.
+ Der {2}-Typ darf keine NULL-Werte zulassen, wenn er als {1}-Parameter im generischen Typ oder in der generischen {0}-Methode verwendet werden soll.Ambiguous user defined conversions '{0}' and '{1}' when converting from '{2}' to '{3}'
- Mehrdeutige benutzerdefinierte Konvertierungen von {0} und {1} bei der Konvertierung von {2} in {3}
+ Mehrdeutige benutzerdefinierte Konvertierungen von {0} und {1} bei der Konvertierung von {2} in {3}'{0}' is not supported by the language
- {0} wird von der Sprache nicht unterstützt.
+ "{0}" wird von der Sprache nicht unterstützt.'{0}': cannot explicitly call operator or accessor
- {0}: Der Operator oder Accessor kann nicht explizit aufgerufen werden.
+ {0}: Der Operator oder Accessor kann nicht explizit aufgerufen werden.Cannot convert to static type '{0}'
- Die Konvertierung in den statischen {0}-Typ ist nicht möglich.
+ Die Konvertierung in den statischen {0}-Typ ist nicht möglich.The operand of an increment or decrement operator must be a variable, property or indexer
- Der Operand eines Inkrement- oder Dekrementoperators muss eine Variable, eine Eigenschaft oder ein Indexer sein.
+ Der Operand eines Inkrement- oder Dekrementoperators muss eine Variable, eine Eigenschaft oder ein Indexer sein.No overload for method '{0}' takes '{1}' arguments
- Keine Überladung für die {0}-Methode nimmt {1}-Argumente an.
+ Keine Überladung für die {0}-Methode nimmt {1}-Argumente an.The best overloaded method match for '{0}' has some invalid arguments
- Die beste Übereinstimmung für die überladene {0}-Methode enthält einige ungültige Argumente.
+ Die beste Übereinstimmung für die überladene {0}-Methode enthält einige ungültige Argumente.A ref or out argument must be an assignable variable
- Ein ref- oder out-Argument muss eine zuweisbare Variable sein.
+ Ein ref- oder out-Argument muss eine zuweisbare Variable sein.Cannot access protected member '{0}' via a qualifier of type '{1}'; the qualifier must be of type '{2}' (or derived from it)
- Auf den geschützten Member "{0}" kann nicht über einen Qualifizierer vom Typ "{1}" zugegriffen werden. Der Qualifizierer muss vom Typ "{2}" (oder von ihm abgeleitet) sein.
+ Auf den geschützten Member "{0}" kann nicht über einen Qualifizierer vom Typ "{1}" zugegriffen werden. Der Qualifizierer muss vom Typ "{2}" (oder von ihm abgeleitet) sein.Property, indexer, or event '{0}' is not supported by the language; try directly calling accessor methods '{1}' or '{2}'
- Die Eigenschaft, der Indexer oder das Ereignis "{0}" wird von der Sprache nicht unterstützt. Rufen Sie die {1}- oder {2}-Accessormethoden direkt auf.
+ Die Eigenschaft, der Indexer oder das Ereignis "{0}" wird von der Sprache nicht unterstützt. Rufen Sie die {1}- oder {2}-Accessormethoden direkt auf.Property, indexer, or event '{0}' is not supported by the language; try directly calling accessor method '{1}'
- Die Eigenschaft, der Indexer oder das Ereignis "{0}" wird von der Sprache nicht unterstützt. Rufen Sie die {1}-Accessormethode direkt auf.
+ Die Eigenschaft, der Indexer oder das Ereignis "{0}" wird von der Sprache nicht unterstützt. Rufen Sie die {1}-Accessormethode direkt auf.Delegate '{0}' does not take '{1}' arguments
- Der Delegat "{0}" akzeptiert {1}-Argumente nicht.
+ Der Delegat "{0}" akzeptiert {1}-Argumente nicht.Delegate '{0}' has some invalid arguments
- Der Delegat "{0}" enthält einige ungültige Argumente.
+ Der Delegat "{0}" enthält einige ungültige Argumente.Cannot assign to '{0}' because it is read-only
- {0} ist schreibgeschützt. Eine Zuweisung ist daher nicht möglich.
+ {0} ist schreibgeschützt. Eine Zuweisung ist daher nicht möglich.Cannot pass '{0}' as a ref or out argument because it is read-only
- {0} ist schreibgeschützt und kann daher nicht als ref- oder out-Argument übergeben werden.
+ {0} ist schreibgeschützt und kann daher nicht als ref- oder out-Argument übergeben werden.Cannot modify the return value of '{0}' because it is not a variable
- Der Rückgabewert von {0} ist keine Variable und kann daher nicht geändert werden.
+ Der Rückgabewert von {0} ist keine Variable und kann daher nicht geändert werden.Members of readonly field '{0}' cannot be modified (except in a constructor or a variable initializer)
- Member des schreibgeschützten Felds "{0}" können nicht geändert werden (außer in einem Konstruktor oder Variableninitialisierer).
+ Member des schreibgeschützten Felds "{0}" können nicht geändert werden (außer in einem Konstruktor oder Variableninitialisierer).Members of readonly field '{0}' cannot be passed ref or out (except in a constructor)
- An Member des schreibgeschützten Felds "{0}" können keine ref- oder out-Argumente übergeben werden (außer in einem Konstruktor).
+ An Member des schreibgeschützten Felds "{0}" können keine ref- oder out-Argumente übergeben werden (außer in einem Konstruktor).Fields of static readonly field '{0}' cannot be assigned to (except in a static constructor or a variable initializer)
- Für Felder eines statischen schreibgeschützten Felds "{0}" ist eine Zuweisung nicht möglich (außer in einem statischen Konstruktor oder einem Variableninitialisierer).
+ Für Felder eines statischen schreibgeschützten Felds "{0}" ist eine Zuweisung nicht möglich (außer in einem statischen Konstruktor oder einem Variableninitialisierer).Fields of static readonly field '{0}' cannot be passed ref or out (except in a static constructor)
- An Felder des schreibgeschützten Felds "{0}" können keine ref- oder out-Argumente übergeben werden (außer in einem Konstruktor).
+ An Felder des schreibgeschützten Felds "{0}" können keine ref- oder out-Argumente übergeben werden (außer in einem Konstruktor).Cannot assign to '{0}' because it is a '{1}'
- {0} ist ein(e) {1}. Eine Zuweisung ist daher nicht möglich.
+ {0} ist ein(e) {1}. Eine Zuweisung ist daher nicht möglich.Cannot pass '{0}' as a ref or out argument because it is a '{1}'
- {0} ist ein(e) {1} und kann daher nicht als ref- oder out-Argument übergeben werden.
+ {0} ist ein(e) {1} und kann daher nicht als ref- oder out-Argument übergeben werden.'{0}' does not contain a constructor that takes '{1}' arguments
- "{0}" enthält keinen Konstruktor, der {1}-Argumente akzeptiert.
+ "{0}" enthält keinen Konstruktor, der {1}-Argumente akzeptiert.Non-invocable member '{0}' cannot be used like a method.
- Der nicht aufrufbare Member "{0}" kann nicht wie eine Methode verwendet werden.
+ Der nicht aufrufbare Member "{0}" kann nicht wie eine Methode verwendet werden.Named argument specifications must appear after all fixed arguments have been specified
- Die Spezifikationen für benannte Argumente müssen nach Angabe aller festen Argumente angezeigt werden.
+ Benannte Argumente müssen nach allen festen Argumenten angegeben werden.The best overload for '{0}' does not have a parameter named '{1}'
- Die beste Überladung für {0} enthält keinen Parameter mit dem Namen "{1}".
+ Die beste Überladung für {0} enthält keinen Parameter mit dem Namen "{1}".The delegate '{0}' does not have a parameter named '{1}'
- Der Delegat "{0}" enthält keinen Parameter mit dem Namen "{1}".
+ Der Delegat "{0}" enthält keinen Parameter mit dem Namen "{1}".Named argument '{0}' cannot be specified multiple times
- Das benannte {0}-Argument kann nicht mehrmals angegeben werden.
+ Das benannte {0}-Argument kann nicht mehrmals angegeben werden.Named argument '{0}' specifies a parameter for which a positional argument has already been given
- Das benannte {0}-Argument legt einen Parameter fest, für den bereits ein positionelles Argument angegeben wurde.
+ Das benannte {0}-Argument legt einen Parameter fest, für den bereits ein positionelles Argument angegeben wurde.
Argument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ Na argument {0} se ve zprávě o protokolování neodkazuje.Argument is not referenced from the logging message
- Argument is not referenced from the logging message
+ Na argument se zpráva o protokolování neodkazujeGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ Generování více než 6 argumentů se nepodporuje.Can't have the same template with different casing
- Can't have the same template with different casing
+ Nemůže mít stejnou šablonu s různým zápisem velkých a malých písmen.Logging method names cannot start with _
- Logging method names cannot start with _
+ Názvy metod protokolování nemůžou začínat podtržítkem (_).Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ Názvy parametrů metody protokolování nemůžou začínat podtržítkem (_).Logging methods cannot have a body
- Logging methods cannot have a body
+ Metody protokolování nemůžou obsahovat tělo.Logging methods cannot be generic
- Logging methods cannot be generic
+ Metody protokolování nemůžou být obecné.Logging methods must be partial
- Logging methods must be partial
+ Metody protokolování musí být částečné.Logging methods must return void
- Logging methods must return void
+ Metody protokolování musí vracet void.Logging methods must be static
- Logging methods must be static
+ Metody protokolování musí být statické.Can't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ Nemůže mít chybně formátované řetězce (třeba neuzavřené závorky { atd.).A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ Hodnota LogLevel musí být zadaná v atributu LoggerMessage, nebo jako parametr metody protokolování.One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ Jeden z argumentů metody statického protokolování {0} musí implementovat rozhraní Microsoft.Extensions.Logging.ILogger.{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ Jeden z argumentů metody statického protokolování musí implementovat rozhraní Microsoft.Extensions.Logging.ILogger.{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Ve třídě {0} se nepovedlo najít pole typu Microsoft.Extensions.Logging.ILogger.{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Nepovedlo se najít pole typu Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ Nepovedlo se najít definici pro typ {0}.Could not find a required type definition
- Could not find a required type definition
+ Nepovedlo se najít požadovanou definici typuFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Ve třídě {0} se našlo několik polí typu Microsoft.Extensions.Logging.ILogger.{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Našlo se několik polí typu Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ Odeberte redundantní kvalifikátor (Informace:, Upozornění:, Chyba: atd.) ze zprávy o protokolování, protože je na zadané úrovni protokolu implicitní.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ Redundantní kvalifikátor ve zprávě o protokolováníDon't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ Nezahrnovat parametry výjimek jako šablony do zprávy o protokolováníDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ Nezahrnovat do zprávy o protokolování šablonu pro {0}, protože se zpracovává implicitně.Don't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ Nezahrnovat parametry úrovně protokolu jako šablony do zprávy o protokolováníDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ Nezahrnovat parametry protokolovacího nástroje jako šablony do zprávy o protokolováníMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ Více než jedna metoda protokolování používá ve třídě {1} ID události {0}.Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ Více než jedna metoda protokolování nemůže v rámci třídy používat stejné ID události.Template '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ Šablona {0} se neposkytuje jako argument pro metodu protokolování.Logging template has no corresponding method argument
- Logging template has no corresponding method argument
+ Šablona protokolování nemá žádný odpovídající argument metodyArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ Auf das Argument „{0}“ wird in der Protokollierungsnachricht nicht verwiesen.Argument is not referenced from the logging message
- Argument is not referenced from the logging message
+ Auf das Argument wird in der Protokollierungsmeldung nicht verwiesenGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ Das Generieren von mehr als 6 Argumenten wird nicht unterstützt.Can't have the same template with different casing
- Can't have the same template with different casing
+ Die gleiche Vorlage darf nicht mit einer anderen Groß-/Kleinschreibung vorliegen.Logging method names cannot start with _
- Logging method names cannot start with _
+ Namen für die Protokollierungsmethode dürfen nicht mit "_" beginnen.Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ Parameternamen für die Protokollierungsmethode dürfen nicht mit "_" beginnen.Logging methods cannot have a body
- Logging methods cannot have a body
+ Protokollierungsmethoden dürfen keinen Text enthalten.Logging methods cannot be generic
- Logging methods cannot be generic
+ Protokollierungsmethoden können nicht generisch sein.Logging methods must be partial
- Logging methods must be partial
+ Protokollierungsmethoden müssen partiell sein.Logging methods must return void
- Logging methods must return void
+ Protokollierungsmethoden müssen leer zurückgegeben werden.Logging methods must be static
- Logging methods must be static
+ Protokollierungsmethoden müssen statisch sein.Can't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ Nicht wohlgeformte Formatzeichenfolgen (beispielsweise mit überzähligen geschweiften Klammern) sind unzulässig.A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ Ein LogLevel-Wert muss im LoggerMessage-Attribut oder als Parameter für die Protokollierungsmethode angegeben werden.One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ Eines der Argumente für die statische Protokollierungsmethode „{0}“ muss die Microsoft.Extensions.Logging.ILogger-Schnittstelle implementieren.{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ Eines der Argumente für eine statische Protokollierungsmethode muss die Microsoft.Extensions.Logging.ILogger-Schnittstelle implementieren.{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ In der Klasse "{0}" wurde kein Feld vom Typ "Microsoft.Extensions.Logging.ILogger" gefunden.{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Feld vom Typ "Microsoft.Extensions.Logging.ILogger" nicht gefunden{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ Die Definition für den Typ "{0}" wurde nicht gefunden.Could not find a required type definition
- Could not find a required type definition
+ Erforderliche Typdefinition nicht gefundenFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ In der Klasse "{0}" wurden mehrere Felder vom Typ "Microsoft.Extensions.Logging.ILogger" gefunden.{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Mehrere Felder vom Typ "Microsoft.Extensions.Logging.ILogger" gefunden{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ Entfernen Sie den redundanten Qualifizierer (z. B. "Info:", "Warnung:" oder "Fehler:") aus der Protokollierungsmeldung, weil er auf der angegebenen Protokollebene implizit enthalten ist.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ Redundanter Qualifizierer in ProtokollierungsmeldungDon't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ Ausnahmeparameter nicht als Vorlagen in die Protokollierungsmeldung einbeziehenDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ Fügen Sie in der Protokollierungsmeldung keine Vorlage für "{0}" ein, weil dies implizit berücksichtigt wird.Don't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ Protokolliergradparameter nicht als Vorlagen in die Protokollierungsmeldung einbeziehenDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ Protokollierungsparameter nicht als Vorlagen in die Protokollierungsmeldung einbeziehenMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ Die Ereignis-ID "{0}" wird von mehreren Protokollierungsmethoden in der Klasse "{1}" verwendet.Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ Dieselbe Ereignis-ID kann nicht von mehreren Protokollierungsmethoden innerhalb einer Klasse verwendet werdenTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ Die Vorlage „{0}“ wird nicht als Argument für die Protokollierungsmethode bereitgestelltLogging template has no corresponding method argument
- Logging template has no corresponding method argument
+ Protokollierungsvorlage weist kein entsprechendes Methodenargument aufArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ No se hace referencia al argumento "{0}" en el mensaje de registroArgument is not referenced from the logging message
- Argument is not referenced from the logging message
+ No se hace referencia al argumento en el mensaje de registroGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ No se admite la generación de más de 6 argumentosCan't have the same template with different casing
- Can't have the same template with different casing
+ No se puede tener la misma plantilla con mayúsculas distintasLogging method names cannot start with _
- Logging method names cannot start with _
+ Los nombres del método de registro no pueden empezar con _Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ Los nombres de parámetro del método de registro no pueden empezar por _Logging methods cannot have a body
- Logging methods cannot have a body
+ Los métodos de registro no pueden tener cuerpoLogging methods cannot be generic
- Logging methods cannot be generic
+ Los métodos de registro no pueden ser genéricosLogging methods must be partial
- Logging methods must be partial
+ Los métodos de registro deben ser parcialesLogging methods must return void
- Logging methods must return void
+ Los métodos de registro deben devolver un valor vacíoLogging methods must be static
- Logging methods must be static
+ Los métodos de registro deben ser estáticosCan't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ No puede tener cadenas con formato incorrecto (como { final, etc.)A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ Debe proporcionarse un valor LogLevel en el atributo LoggerMessage o como parámetro en el método de registroOne of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ Uno de los argumentos para el método de registro estático "{0}" debe implementar la interfaz Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ Uno de los argumentos para un método de registro estático debe implementar la interfaz Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ No se encontró ningún campo de tipo Microsoft.Extensions.Logging.ILogger en la clase {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ No se encontró ningún campo de tipo Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ No se pudo encontrar la definición para el tipo {0}Could not find a required type definition
- Could not find a required type definition
+ No se encontró ninguna definición de tipo necesariaFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Se encontraron varios campos del tipo Microsoft.Extensions.Logging.ILogger en la clase {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Se encontraron varios campos de tipo Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ Quitar calificadores redundantes (Información:, Advertencia:, Error:, etc.) del mensaje de registro, ya que está implícito en el nivel de registro especificado.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ Calificador redundante en el mensaje de registroDon't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ No incluya parámetros de excepción como plantillas en el mensaje de registroDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ No incluya ninguna plantilla para {0} en el mensaje de registro, ya que está resuelto implícitamenteDon't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ No incluya parámetros de nivel de registro como plantillas en el mensaje de registroDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ No incluya parámetros del registrador como plantillas en el mensaje de registroMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ Varios métodos de registro usan el id. de evento {0} en la clase {1}Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ Varios métodos de registro no pueden usar un mismo id. de evento en una claseTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ La plantilla "{0}" no se proporciona como argumento para el método de registroLogging template has no corresponding method argument
- Logging template has no corresponding method argument
+ La plantilla de registro no tiene ningún argumento de método correspondienteArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ L’argument « {0} » n’est pas référencé à partir du message de journalisationArgument is not referenced from the logging message
- Argument is not referenced from the logging message
+ L’argument n’est pas référencé à partir du message de journalisationGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ La génération de plus de 6 arguments n’est pas prise en chargeCan't have the same template with different casing
- Can't have the same template with different casing
+ Impossible d’avoir le même modèle avec une casse différenteLogging method names cannot start with _
- Logging method names cannot start with _
+ Les noms de méthode de journalisation ne peuvent pas commencer par _Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ Les noms de paramètres de méthode de journalisation ne peuvent pas commencer par _Logging methods cannot have a body
- Logging methods cannot have a body
+ Les méthodes de journalisation ne peuvent pas avoir de corpsLogging methods cannot be generic
- Logging methods cannot be generic
+ Les méthodes de journalisation ne peuvent pas être génériquesLogging methods must be partial
- Logging methods must be partial
+ Les méthodes de journalisation doivent être partiellesLogging methods must return void
- Logging methods must return void
+ Les méthodes de journalisation doivent retourner voidLogging methods must be static
- Logging methods must be static
+ Les méthodes de journalisation doivent être statiquesCan't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ Chaînes de format incorrect (par exemple { non fermée, etc.)A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ Une valeur LogLevel doit être fournie dans l’attribut LoggerMessage ou en tant que paramètre de la méthode de journalisationOne of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ L’un des arguments d’une méthode de journalisation statique « {0} » doit implémenter l’interface Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ L’un des arguments d’une méthode de journalisation statique doit implémenter l’interface Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Impossible de trouver un champ de type Microsoft.Extensions.Logging.ILogger dans la classe {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Impossible de trouver un champ de type Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ La définition du type {0} n’a pas été trouvéeCould not find a required type definition
- Could not find a required type definition
+ Impossible de trouver la définition d’un type requisFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Plusieurs champs de type Microsoft.Extensions.Logging.ILogger ont été trouvés dans la classe {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Plusieurs champs de type Microsoft.Extensions.Logging.ILogger ont été trouvés{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ Supprimez le qualificateur redondant (Info:, Warning:, Error:, etc.) du message de journalisation, car il est implicite dans le niveau de journalisation spécifié.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ Qualificateur redondant dans le message de journalisationDon't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ Ne pas ajouter de paramètres d’exception comme modèles dans le message de journalisationDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ Ne pas ajouter de modèle pour {0} dans le message de journalisation, car il est implicitement pris en chargeDon't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ Ne pas ajouter de paramètres de niveau de journalisation comme modèles dans le message de journalisationDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ Ne pas ajouter de paramètres d’enregistreur de journalisation comme modèles dans le message de journalisationMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ Plusieurs méthodes de journalisation utilisent l’ID d’événement {0} dans la classe {1}Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ Le même ID d’événement dans une classe ne peut pas être utilisé par plusieurs méthodes de journalisationTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ Le modèle « {0} » n’est pas fourni comme argument de la méthode de journalisationLogging template has no corresponding method argument
- Logging template has no corresponding method argument
+ Le modèle de journalisation n’a pas d’argument de méthode correspondantArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ Il messaggio di registrazione non fa riferimento all'argomento '{0}'Argument is not referenced from the logging message
- Argument is not referenced from the logging message
+ Il messaggio di registrazione non fa riferimento all'argomentoGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ La creazione di più di 6 argomenti non è supportataCan't have the same template with different casing
- Can't have the same template with different casing
+ Impossibile avere lo stesso modello con un utilizzo di maiuscole e minuscole diversoLogging method names cannot start with _
- Logging method names cannot start with _
+ I nomi dei metodi di registrazione non possono iniziare con _Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ I nomi dei parametri del metodo di registrazione non possono iniziare con _Logging methods cannot have a body
- Logging methods cannot have a body
+ I metodi di registrazione non possono avere un corpoLogging methods cannot be generic
- Logging methods cannot be generic
+ I metodi di registrazione non possono essere genericiLogging methods must be partial
- Logging methods must be partial
+ I metodi di registrazione devono essere parzialiLogging methods must return void
- Logging methods must return void
+ I metodi di registrazione devono restituire voidLogging methods must be static
- Logging methods must be static
+ I metodi di registrazione devono essere staticiCan't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ Impossibile avere stringhe di formato non valido (ad esempio, { tralasciato e così via)A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ È necessario specificare un valore LogLevel nell'attributo LoggerMessage o come parametro per il metodo di registrazioneOne of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ Uno degli argomenti del metodo di registrazione statico '{0}' deve implementare l'interfaccia Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ Uno degli argomenti del metodo di registrazione statico deve implementare l'interfaccia Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Non è stato possibile trovare un campo di tipo Microsoft.Extensions.Logging.ILogger nella classe {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Non è stato possibile trovare un campo di tipo Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ Non è stato possibile trovare una definizione per il tipo {0}Could not find a required type definition
- Could not find a required type definition
+ Non è stato possibile trovare una definizione del tipo richiestoFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Sono stati trovati più campi di tipo Microsoft.Extensions.Logging.ILogger nella classe {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Sono stati trovati più campi di tipo Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ Rimuovere il qualificatore ridondante (Informazioni:, Avviso:, Errore: e così via) dal messaggio di registrazione perché è implicito nel livello di log specificato.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ Qualificatore ridondante nel messaggio di registrazioneDon't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ Non includere i parametri di eccezione come modelli nel messaggio di registrazioneDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ Non includere un modello per {0} nel messaggio di registrazione perché è gestito in modo implicitoDon't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ Non includere i parametri del livello di log come modelli nel messaggio di registrazioneDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ Non includere i parametri del logger come modelli nel messaggio di registrazioneMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ Più metodi di registrazione stanno utilizzando l'ID evento {0} nella classe {1}Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ Più metodi di registrazione non possono utilizzare lo stesso ID evento all'interno di una classeTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ Il modello ‘{0}’ non è specificato come argomento per il metodo di registrazioneLogging template has no corresponding method argument
- Logging template has no corresponding method argument
+ Il modello di registrazione non ha alcun argomento del metodo corrispondenteArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ 引数 '{0}' はログ メッセージから参照されていませんArgument is not referenced from the logging message
- Argument is not referenced from the logging message
+ 引数はログ メッセージから参照されていませんGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ 6 つ以上の引数の生成はサポートされませんCan't have the same template with different casing
- Can't have the same template with different casing
+ 大文字と小文字に対して同じテンプレートを使用できませんLogging method names cannot start with _
- Logging method names cannot start with _
+ ログ メソッド名は「 _ 」で始まることはできませんLogging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ Logging method パラメーター名は「 _ 」で始まることはできませんLogging methods cannot have a body
- Logging methods cannot have a body
+ ログ メソッドは本文を含めることができませんLogging methods cannot be generic
- Logging methods cannot be generic
+ ログ メソッドを汎用にすることはできませんLogging methods must be partial
- Logging methods must be partial
+ ログ記録方法の一部が必要ですLogging methods must return void
- Logging methods must return void
+ ログ メソッドは無効を返す必要がありますLogging methods must be static
- Logging methods must be static
+ ログ メソッドは静的である必要がありますCan't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ (dangling {など) 誤った形式の文字列を持つことはできませんA LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ LogLevel 値は、LoggingMessage 属性または logging メソッドのパラメーターとして指定する必要がありますOne of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ 静的ログ メソッド '{0}' への引数の 1 つには、Microsoft.Extensions.Logging.ILogger インターフェイスを実装する必要があります。{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ 静的ログ メソッドへの引数の 1 つには、Microsoft.Extensions.Logging.ILogger インターフェイスを実装する必要があります。{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ クラスで Microsoft.Extensions.Logging.ILogger 型のフィールドが見つかりませんでした {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Microsoft.Extensions.Logging.ILogger 型のフィールドが見つかりませんでした{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ {0} 型の定義が見つかりませんCould not find a required type definition
- Could not find a required type definition
+ 必要な型の定義が見つかりませんでしたFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ クラスに Microsoft.Extensions.Logging.ILogger という種類の複数のフィールドがあります {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Microsoft.Extensions.Logging.ILogger という種類の複数のフィールドが見つかりました{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ 指定されたログ レベルでは暗黙的であるため、冗長な修飾子 (Info:、Warning:、Error: など) をログ メッセージから削除します。Redundant qualifier in logging message
- Redundant qualifier in logging message
+ ログ メッセージ内の冗長な修飾子Don't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ ログ メッセージに例外パラメーターをテンプレートとして含めませんDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ 暗黙的に処理が行 われているため、ログ メッセージに {0} のテンプレートを含めませんDon't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ ログ メッセージには、ログ レベル パラメーターをテンプレートとして含めることはできませんDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ ログ メッセージにロガー パラメーターをテンプレートとして含めませんMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ 複数のログ記録方法でクラス {1}内のイベント ID {0} を使用していますMultiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ 複数のログ記録方法では、クラス内で同じイベント ID を使用できませんTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ テンプレート '{0}' は、ログ メソッドの引数として提供されませんLogging template has no corresponding method argument
- Logging template has no corresponding method argument
+ ログ テンプレートに対応するメソッド引数がありませんArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ 로깅 메시지에서 ‘{0}’ 인수를 참조하지 않습니다.Argument is not referenced from the logging message
- Argument is not referenced from the logging message
+ 로깅 메시지에서 인수를 참조하지 않음Generating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ 6개가 넘는 인수 생성은 지원되지 않음Can't have the same template with different casing
- Can't have the same template with different casing
+ 동일한 템플릿을 대/소문자를 다르게 하여 사용할 수는 없음Logging method names cannot start with _
- Logging method names cannot start with _
+ 로깅 메서드 이름은 _로 시작할 수 없음Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ 로깅 메서드 매개 변수 이름은 _로 시작할 수 없음Logging methods cannot have a body
- Logging methods cannot have a body
+ 로깅 메서드에는 본문을 사용할 수 없음Logging methods cannot be generic
- Logging methods cannot be generic
+ 로깅 메서드는 제네릭일 수 없음Logging methods must be partial
- Logging methods must be partial
+ 로깅 메서드는 부분이어야 함Logging methods must return void
- Logging methods must return void
+ 로깅 메서드는 void를 반환해야 함Logging methods must be static
- Logging methods must be static
+ 로깅 메서드는 정적이어야 함Can't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ 잘못된 형식의 문자열(예: 짝이 맞지 않는 중괄호({))은 사용할 수 없음A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ LogLevel 값은 LoggerMessage 특성에 지정하거나 로깅 메서드에 대한 매개 변수로 제공해야 함One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ 정적 로깅 메서드 ‘{0}’의 인수 중 하나가 Microsoft.Extensions.Logging.ILogger 인터페이스를 구현해야 함{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ 정적 로깅 메서드 인수 중 하나가 Microsoft.Extensions.Logging.ILogger 인터페이스를 구현해야 함{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ {0} 클래스에서 Microsoft.Extensions.Logging.ILogger 형식의 필드를 찾을 수 없음{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Microsoft.Extensions.Logging.ILogger 형식의 필드를 찾을 수 없음{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ 형식 {0}에 대한 정의를 찾을 수 없음Could not find a required type definition
- Could not find a required type definition
+ 필요한 형식 정의를 찾을 수 없음Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ {0} 클래스에 Microsoft.Extensions.Logging.ILogger 형식의 필드가 여러 개 있음{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Microsoft.Extensions.Logging.ILogger 형식의 필드가 여러 개 있음{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ 중복 한정자(정보:, 경고:, 오류: 등)가 지정된 로그 수준에서 암시적이기 때문에 로깅 메시지에서 제거합니다.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ 로깅 메시지에 중복 한정자가 있음Don't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ 로깅 메시지에 템플릿으로 예외 매개 변수를 포함하지 않음Don't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ {0}에 대한 템플릿은 암시적으로 처리되므로 로깅 메시지에 포함하지 않음Don't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ 로깅 메시지에 템플릿으로 로그 수준 매개 변수를 포함하지 않음Don't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ 로깅 메시지에 템플릿으로 로거 매개 변수를 포함하지 않음Multiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ {1} 클래스에서 여러 로깅 메서드가 이벤트 ID {0}을(를) 사용함Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ 여러 로깅 메서드가 한 클래스 내에서 동일한 이벤트 ID를 사용할 수는 없음Template '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ 템플릿 {0}이(가) 로깅 메서드에 인수로 제공되지 않음Logging template has no corresponding method argument
- Logging template has no corresponding method argument
+ 로깅 템플릿에 해당 하는 메서드 인수가 없음Argument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ Do argumentu „{0}” nie odwołuje się komunikat rejestrowaniaArgument is not referenced from the logging message
- Argument is not referenced from the logging message
+ Do argumentu nie odwołuje się komunikat rejestrowaniaGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ Generowanie więcej niż 6 argumentów nie jest obsługiwaneCan't have the same template with different casing
- Can't have the same template with different casing
+ Nie można mieć tego samego szablonu z różną wielkością literLogging method names cannot start with _
- Logging method names cannot start with _
+ Nazwy metody rejestrowania nie mogą rozpoczynać się od znaku „_”Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ Nazwy parametrów metody rejestrowania nie mogą rozpoczynać się od znaku „_”Logging methods cannot have a body
- Logging methods cannot have a body
+ Metody rejestrowania nie mogą mieć treściLogging methods cannot be generic
- Logging methods cannot be generic
+ Metody rejestrowania nie mogą być ogólneLogging methods must be partial
- Logging methods must be partial
+ Metody rejestrowania muszą być częścioweLogging methods must return void
- Logging methods must return void
+ Metody rejestrowania muszą zwracać wartość typu voidLogging methods must be static
- Logging methods must be static
+ Metody rejestrowania muszą być statyczneCan't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ Nie może zawierać źle sformułowanego formatu ciągów (takich jak zawieszonego znaku „{”, itp.)A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ Wartość LogLevel musi być podana w atrybucie LoggerMessage lub jako parametr metody rejestrowaniaOne of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ Jeden z argumentów statycznej metody rejestrowania „{0}” musi implementować interfejs Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ Jeden z argumentów statycznej metody rejestrowania musi implementować interfejs Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Nie można znaleźć pola typu Microsoft.Extensions.Logging.ILogger w klasie {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Nie można znaleźć pola typu Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ Nie można znaleźć definicji dla typu {0}Could not find a required type definition
- Could not find a required type definition
+ Nie można znaleźć wymaganej definicji typuFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Znaleziono wiele pól typu Microsoft.Extensions.Logging.ILogger w klasie {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Znaleziono wiele pól typu Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ Usuń nadmiarowy kwalifikator (Info:, Warning:, Error: itp.) z komunikatu rejestrowania, ponieważ jest on domyślny na określonym poziomie dziennika.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ Nadmiarowy kwalifikator w komunikacie rejestrowaniaDon't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ Nie dołączać parametrów wyjątków jako szablonów w komunikatach rejestrowaniaDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ Nie dołączać szablonu dla {0} do komunikatu o rejestracji, ponieważ jest to wykonywane domyślnieDon't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ Nie dołączać parametrów poziomu dziennika jako szablonów w komunikatach rejestrowaniaDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ Nie dołączać parametrów rejestratora jako szablonów do komunikatu rejestrowaniaMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ Wiele metod rejestrowania używa identyfikatora zdarzenia {0} w klasie {1}Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ Wiele metod rejestrowania nie może używać tego samego identyfikatora zdarzenia w obrębie klasyTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ Nie podano szablonu „{0}” jako argumentu dla metody rejestrowaniaLogging template has no corresponding method argument
- Logging template has no corresponding method argument
+ Szablon rejestrowania nie ma odpowiadającego mu argumentu metodyArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ O argumento '{0}' não é referenciado na mensagem de registro em logArgument is not referenced from the logging message
- Argument is not referenced from the logging message
+ O argumento não é referenciado na mensagem de registro em logGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ A geração de mais de 6 argumentos não é suportadaCan't have the same template with different casing
- Can't have the same template with different casing
+ Não é possível ter o mesmo modelo com diferenças entre maiúsculas e minúsculas.Logging method names cannot start with _
- Logging method names cannot start with _
+ Os nomes dos métodos de registro em log não podem começar com _Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ Os nomes dos parâmetros do método de registro em log não podem começar com _Logging methods cannot have a body
- Logging methods cannot have a body
+ Os métodos de registro em log não podem ter um corpoLogging methods cannot be generic
- Logging methods cannot be generic
+ Os métodos de registro em log não podem ser genéricosLogging methods must be partial
- Logging methods must be partial
+ Os métodos de registro em log devem ser parciaisLogging methods must return void
- Logging methods must return void
+ Os métodos de registro em log devem retornar nulosLogging methods must be static
- Logging methods must be static
+ Os métodos de registro em log devem ser estáticosCan't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ Não pode ter cadeia de caracteres de formato malformadas (como final {, etc)A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ Um valor LogLevel deve ser fornecido no atributo LoggerMessage ou como um parâmetro para o método de registro em logOne of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ Um dos argumentos para um método de log estático '{0}' deve implementar a interface Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ Um dos argumentos para um método de log estático deve implementar a interface Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Não foi possível encontrar um campo do tipo Microsoft.Extensions.Logging.ILogger na classe {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Não foi possível encontrar um campo do tipo Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ Não foi possível encontrar a definição para o tipo {0}Could not find a required type definition
- Could not find a required type definition
+ Não foi possível encontrar uma definição de tipo necessáriaFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ Múltiplos campos do tipo Microsoft.Extensions.Logging.ILogger encontrados na classe {0}{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Múltiplos campos encontrados do tipo Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ Remova o qualificador redundante (Info:, Aviso:, Erro:, etc) da mensagem de log, pois está implícito no nível de log especificado.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ Qualificador redundante na mensagem de registro de logDon't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ Não inclua parâmetros de exceção como modelos na mensagem de registro em logDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ Não inclua um modelo para {0} na mensagem de registro em log, pois isso é implicitamente atendidoDon't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ Não inclua parâmetros de nível de registro como modelos na mensagem de registro de logDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ Não inclua parâmetros de agente como modelos na mensagem de registro em logMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ Múltiplos métodos de registro em log estão usando a id de evento {0} na classe {1}Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ Múltiplos métodos de registro em log não podem usar o mesmo id de evento dentro de uma classeTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ O modelo '{0}' não é fornecido como argumento para o método de registroLogging template has no corresponding method argument
- Logging template has no corresponding method argument
+ O modelo de registro em log não tem nenhum argumento de método correspondenteArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ В сообщении ведения журнала нет ссылки на аргумент "{0}"Argument is not referenced from the logging message
- Argument is not referenced from the logging message
+ В сообщении ведения журнала нет ссылки на аргументGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ Формирование более 6 аргументов не поддерживаетсяCan't have the same template with different casing
- Can't have the same template with different casing
+ Невозможно использовать шаблон с таким же именем в другом регистреLogging method names cannot start with _
- Logging method names cannot start with _
+ Имена методов ведения журнала не могут начинаться с символа "_"Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ Имена параметров метода ведения журнала не могут начинаться с символа "_"Logging methods cannot have a body
- Logging methods cannot have a body
+ У методов ведения журнала не может быть текстаLogging methods cannot be generic
- Logging methods cannot be generic
+ Методы ведения журнала не могут быть универсальнымиLogging methods must be partial
- Logging methods must be partial
+ Методы ведения журнала должны быть частичнымиLogging methods must return void
- Logging methods must return void
+ Методы ведения журнала должны возвращать значение voidLogging methods must be static
- Logging methods must be static
+ Методы ведения журнала должны быть статическимиCan't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ Для строк формата не допускается неправильный формат (висячие символы "{" и т. п.)A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ Значение LogLevel должно быть указано в атрибуте LoggerMessage или в качестве параметра метода ведения журналаOne of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ Один из аргументов статического метода ведения журнала "{0}" должен реализовывать интерфейс Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ Один из аргументов статического метода ведения журнала должен реализовывать интерфейс Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ В классе {0} не найдены поля типа Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Не удалось найти поле типа Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ Не найдено определение для типа {0}Could not find a required type definition
- Could not find a required type definition
+ Не найдено требуемое определение типаFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ В классе {0} обнаружено несколько полей типа Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Обнаружено несколько полей типа Microsoft.Extensions.Logging.ILogger{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ Удалите избыточный квалификатор (Info:, Warning:, Error:, и т. п.) из сообщения журнала, поскольку квалификатор подразумевается на указанном уровне ведения журнала.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ Избыточный квалификатор в сообщении журналаDon't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ Не включайте параметры исключений в качестве шаблонов в сообщение ведения журналаDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ Не включайте шаблон для {0} в сообщение ведения журнала, поскольку он используется неявным образомDon't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ Не включайте параметры уровня журнала в качестве шаблонов в сообщение ведения журналаDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ Не включайте параметры средства ведения журнала в качестве шаблонов в сообщение ведения журналаMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ Несколько методов ведения журнала используют идентификатор события {0} в классе {1}Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ Несколько методов ведения журнала не могут использовать одинаковый ИД события в пределах классаTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ Шаблон "{0}" не указан в качестве аргумента для метода ведения журналаLogging template has no corresponding method argument
- Logging template has no corresponding method argument
+ У шаблона журнала нет соответствующего аргумента методаArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ '{0}' bağımsız değişkenine günlük iletisinden başvurulmuyorArgument is not referenced from the logging message
- Argument is not referenced from the logging message
+ Bağımsız değişkene günlüğe kaydetme iletisinden başvurulmuyorGenerating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ 6’dan fazla bağımsız değişken oluşturma özelliği desteklenmiyorCan't have the same template with different casing
- Can't have the same template with different casing
+ Aynı şablon farklı büyük/küçük harfler içeremezLogging method names cannot start with _
- Logging method names cannot start with _
+ Günlüğe kaydetme yöntemi adları _ ile başlayamazLogging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ Günlüğe kaydetme yöntemi parametre adları _ ile başlayamazLogging methods cannot have a body
- Logging methods cannot have a body
+ Günlüğe kaydetme yöntemleri gövde içeremezLogging methods cannot be generic
- Logging methods cannot be generic
+ Günlüğe kaydetme yöntemleri genel olamazLogging methods must be partial
- Logging methods must be partial
+ Günlüğe kaydetme yöntemleri kısmi olmalıdırLogging methods must return void
- Logging methods must return void
+ Günlüğe kaydetme yöntemleri boş değer döndürmelidirLogging methods must be static
- Logging methods must be static
+ Günlüğe kaydetme yöntemleri statik olmalıdırCan't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ Hatalı biçimlendirilmiş biçim dizeleri (aykırı { vb. gibi) içeremezA LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ LoggerMessage özniteliğinde veya günlüğe kaydetme yönteminin parametresi olarak bir LogLevel değerinin belirtilmesi gerekiyorOne of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ '{0}' statik günlük metoduna yönelik bağımsız değişkenlerden biri Microsoft.Extensions.Logging.ILogger arabirimini uygulamalıdır{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ Statik günlük metoduna yönelik bağımsız değişkenlerden biri Microsoft.Extensions.Logging.ILogger arabirimini uygulamalıdır{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ {0} sınıfında Microsoft.Extensions.Logging.ILogger türündeki alan bulunamadı{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ Microsoft.Extensions.Logging.ILogger türündeki alan bulunamadı{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ {0} türü için tanım bulunamadıCould not find a required type definition
- Could not find a required type definition
+ Gerekli bir tür tanımı bulunamadıFound multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ {0} sınıfında Microsoft.Extensions.Logging.ILogger türünde birden çok alan bulundu{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ Microsoft.Extensions.Logging.ILogger türünde birden çok alan bulundu{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ Belirtilen günlük düzeyinde örtük olduğundan gereksiz niteleyiciyi (Bilgi:, Uyarı:, Hata: vb.) günlüğe kaydetme iletisinden kaldırın.Redundant qualifier in logging message
- Redundant qualifier in logging message
+ Günlüğe kaydetme iletisindeki gereksiz niteleyiciDon't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ Özel durum parametrelerini günlüğe kaydetme iletisine şablon olarak eklemeyinDon't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ Örtük olarak dikkate alındığından günlüğe kaydetme iletisine {0} şablonu eklemeyinDon't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ Günlük düzeyi parametrelerini günlüğe kaydetme iletisine şablon olarak eklemeyinDon't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ Günlükçü parametrelerini günlüğe kaydetme iletisine şablon olarak eklemeyinMultiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ Birden çok günlüğe kaydetme yöntemi {1} sınıfında {0} olay kimliğini kullanıyorMultiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ Birden çok günlüğe kaydetme yöntemi bir sınıf içinde aynı olay kimliğini kullanamazTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ ‘{0}’ şablonu günlüğe kaydetme yönteminin bağımsız değişkeni olarak sağlanmadıLogging template has no corresponding method argument
- Logging template has no corresponding method argument
+ Günlüğe kaydetme şablonunda karşılık gelen yöntem bağımsız değişkeni yokArgument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ 未从日志记录消息中引用参数“{0}”Argument is not referenced from the logging message
- Argument is not referenced from the logging message
+ 未从日志记录消息中引用参数Generating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ 不支持生成 6 个以上的参数Can't have the same template with different casing
- Can't have the same template with different casing
+ 不能有大小写不同的相同模板Logging method names cannot start with _
- Logging method names cannot start with _
+ 日志记录方法名称不能以 _ 开头Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ 日志记录方法参数名称不能以 _ 开头Logging methods cannot have a body
- Logging methods cannot have a body
+ 日志记录方法不能有正文Logging methods cannot be generic
- Logging methods cannot be generic
+ 日志记录方法不能为泛型方法Logging methods must be partial
- Logging methods must be partial
+ 日志记录方法必须为分部方法Logging methods must return void
- Logging methods must return void
+ 日志记录方法必须返回 voidLogging methods must be static
- Logging methods must be static
+ 日志记录方法必须为静态方法Can't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ 不能有格式错误的格式字符串(例如悬空 { 等)A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ 必须在 LoggerMessage 属性中提供 LogLevel 值或将其用作日志记录方法的参数One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ 静态日志记录方法“{0}”的参数之一必须实施 Microsoft.Extensions.Logging.ILogger 接口{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ 静态日志记录方法的参数之一必须实现 Microsoft.Extensions.Logging.ILogger 接口{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ 在类 {0} 中找不到 Microsoft.Extensions.Logging.ILogger 类型的字段{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ 找不到 Microsoft.Extensions.Logging.ILogger 类型的字段。{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ 找不到类型 {0} 的定义Could not find a required type definition
- Could not find a required type definition
+ 找不到所需的类型定义Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ 在类 {0} 中找到多个 Microsoft.Extensions.Logging.ILogger 类型的字段{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ 找到 Microsoft.Extensions.Logging.ILogger 类型的多个字段{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ 从日志记录消息中删除冗余限定符(信息:、警告:、错误: 等),因为其在指定的日志级别中为隐式内容。Redundant qualifier in logging message
- Redundant qualifier in logging message
+ 日志消息消息中的冗余限定符Don't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ 不要将异常参数作为模板包含在日志记录消息中Don't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ 不要将 {0} 的模板包含在日志记录消息中,因为其被隐式处理Don't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ 不要将日志级别参数作为模板包含在日志记录消息中Don't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ 不要将记录器参数作为模板包含在日志记录消息中Multiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ 多个日志记录方法正在类 {1} 中使用事件 ID {0}Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ 多个日志记录方法不能在类中使用相同的事件 IDTemplate '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ 未将模板“{0}”作为参数提供给日志记录方法Logging template has no corresponding method argument
- Logging template has no corresponding method argument
+ 日志记录模板无相应的方法参数Argument '{0}' is not referenced from the logging message
- Argument '{0}' is not referenced from the logging message
+ 引數 '{0}' 未參照記錄訊息Argument is not referenced from the logging message
- Argument is not referenced from the logging message
+ 未從記錄訊息參照引數Generating more than 6 arguments is not supported
- Generating more than 6 arguments is not supported
+ 不支援產生 6 個以上的引數Can't have the same template with different casing
- Can't have the same template with different casing
+ 不能有不同大小寫的相同範本Logging method names cannot start with _
- Logging method names cannot start with _
+ 記錄方法名稱的開頭不能為 _Logging method parameter names cannot start with _
- Logging method parameter names cannot start with _
+ 記錄方法參數名稱的開頭不能為 _Logging methods cannot have a body
- Logging methods cannot have a body
+ 記錄方法不能有主體Logging methods cannot be generic
- Logging methods cannot be generic
+ 記錄方法不可為泛型Logging methods must be partial
- Logging methods must be partial
+ 記錄方法必須是部分Logging methods must return void
- Logging methods must return void
+ 記錄方法必須傳回 voidLogging methods must be static
- Logging methods must be static
+ 記錄方法必須是靜態Can't have malformed format strings (like dangling {, etc)
- Can't have malformed format strings (like dangling {, etc)
+ 不能有格式錯誤的格式字串 (例如懸空 {, 等等)A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
- A LogLevel value must be supplied in the LoggerMessage attribute or as a parameter to the logging method
+ 必須在 LoggerMessage 屬性中提供 LogLevel 值,或將其做為記錄方法的參數。One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to the static logging method '{0}' must implement the Microsoft.Extensions.Logging.ILogger interface
+ 靜態記錄方法 '{0}' 的其中一個引數必須實作 Microsoft.Extensions.Logging.ILogger 介面{Locked="Microsoft.Extensions.Logging.ILogger"}One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
- One of the arguments to a static logging method must implement the Microsoft.Extensions.Logging.ILogger interface
+ 靜態記錄方法的其中一個引數必須實作 Microsoft.Extensions.Logging.ILogger 介面{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger in class {0}
+ 找不到類別 {0} 中 Microsoft.Extensions.Logging.ILogger 類型的欄位{Locked="Microsoft.Extensions.Logging.ILogger"}Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
- Couldn't find a field of type Microsoft.Extensions.Logging.ILogger
+ 找不到 Microsoft.Extensions.Logging.ILogger 類型的欄位{Locked="Microsoft.Extensions.Logging.ILogger"}Could not find definition for type {0}
- Could not find definition for type {0}
+ 找不到類型 {0} 的定義Could not find a required type definition
- Could not find a required type definition
+ 找不到所需的類型定義Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger in class {0}
+ 在類別 {0} 中找到多個 Microsoft.Extensions.Logging.ILogger 類型的欄位{Locked="Microsoft.Extensions.Logging.ILogger"}Found multiple fields of type Microsoft.Extensions.Logging.ILogger
- Found multiple fields of type Microsoft.Extensions.Logging.ILogger
+ 找到多個 Microsoft.Extensions.Logging.ILogger 類型的欄位{Locked="Microsoft.Extensions.Logging.ILogger"}Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
- Remove redundant qualifier (Info:, Warning:, Error:, etc) from the logging message since it is implicit in the specified log level.
+ 從記錄訊息中移除備援限定詞 (資訊:、警告:、錯誤: 等等),因為它在指定的記錄層級中為隱含。Redundant qualifier in logging message
- Redundant qualifier in logging message
+ 記錄訊息中的備援限定詞Don't include exception parameters as templates in the logging message
- Don't include exception parameters as templates in the logging message
+ 請勿在記錄訊息中包含做為範本的例外狀況參數Don't include a template for {0} in the logging message since it is implicitly taken care of
- Don't include a template for {0} in the logging message since it is implicitly taken care of
+ 請勿在記錄訊息中包含 {0} 的範本,因為系統是將它隱含處理Don't include log level parameters as templates in the logging message
- Don't include log level parameters as templates in the logging message
+ 請勿在記錄訊息中包含做為範本的記錄層級參數Don't include logger parameters as templates in the logging message
- Don't include logger parameters as templates in the logging message
+ 請勿在記錄訊息中包含做為範本的記錄器參數Multiple logging methods are using event id {0} in class {1}
- Multiple logging methods are using event id {0} in class {1}
+ 多個記錄方法是使用類別 {1} 中的事件識別碼 {0}Multiple logging methods cannot use the same event id within a class
- Multiple logging methods cannot use the same event id within a class
+ 多個記錄方法不能在類別內使用相同的事件識別碼Template '{0}' is not provided as argument to the logging method
- Template '{0}' is not provided as argument to the logging method
+ 未將範本 '{0}' 提供做為記錄方法的引數Logging template has no corresponding method argument
- Logging template has no corresponding method argument
+ 記錄範本沒有對應的方法引數Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ Odvozený typ JsonSerializerContext {0} určuje typy serializovatelné na JSON. Typ a všechny obsahující typy musí být částečné, aby se zahájilo generování zdroje.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ Odvozené typy JsonSerializerContext a všechny obsahující typy musí být částečné.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ Existuje několik typů s názvem {0}. Zdroj se vygeneroval pro první zjištěný typ. Tuto kolizi vyřešíte pomocí JsonSerializableAttribute.TypeInfoPropertyName.Duplicate type name.
- Duplicate type name.
+ Duplicitní název typuDid not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ Nevygenerovala se metadata serializace pro typ {0}.Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ Nevygenerovala se metadata serializace pro typDerived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ Der abgeleitete JsonSerializerContext-Typ "{0}" gibt serialisierbare JSON-Typen an. Der Typ und alle enthaltenden Typen müssen partiell sein, um die Quellgenerierung zu starten.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ Abgeleitete JsonSerializerContext-Typen und alle enthaltenden Typen müssen partiell sein.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ Es sind mehrere Typen namens "{0}" vorhanden. Die Quelle wurde für den ersten festgestellten Typ generiert. Verwenden Sie "JsonSerializableAttribute.TypeInfoPropertyName", um diesen Konflikt zu beheben.Duplicate type name.
- Duplicate type name.
+ Doppelter TypnameDid not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ Die Serialisierungsmetadaten für den Typ "{0}" wurden nicht generiert.Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ Serialisierungsmetadaten für den Typ wurden nicht generiertDerived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ El tipo derivado "JsonSerializerContext" "{0}" especifica tipos de JSON serializables. El tipo y todos los tipos que contienen deben hacerse parciales para iniciar la generación de origen.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ Los tipos derivados "JsonSerializerContext" y todos los tipos que contienen deben ser parciales.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ Hay varios tipos denominados {0}. El origen se generó para el primero detectado. Use "JsonSerializableAttribute.TypeInfoPropertyName" para resolver esta colisión.Duplicate type name.
- Duplicate type name.
+ Nombre de tipo duplicado.Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ No generó metadatos de serialización para el tipo '{0}".Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ No generó metadatos de serialización de metadatos para el tipo.Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ Le type 'JsonSerializerContext' dérivé '{0}' spécifie des types Sérialisables JSON. Le type et tous les types contenants doivent être rendus partiels pour lancer la génération de la source.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ Les types dérivés 'JsonSerializerContext' et tous les types conteneurs doivent être partiels.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ Plusieurs types nommés {0}. La source a été générée pour la première détection détectée. Utilisez « JsonSerializableAttribute.TypeInfoPropertyName » pour résoudre cette collision.Duplicate type name.
- Duplicate type name.
+ Nom de type dupliqué.Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ Les métadonnées de sérialisation pour le type « {0} » n’ont pas été générées.Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ Les métadonnées de sérialisation pour le type n’ont pas été générées.Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ Il tipo 'JsonSerializerContext 'derivato '{0}' specifica i tipi serializzabili JSON. Il tipo e tutti i tipi contenenti devono essere parziali per iniziare la generazione dell'origine.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ I tipi derivati 'JsonSerializerContext' e tutti i tipi contenenti devono essere parziali.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ Sono presenti più tipi denominati {0}. L'origine è stata generata per il primo tipo rilevato. Per risolvere questa collisione, usare 'JsonSerializableAttribute.TypeInfoPropertyName'.Duplicate type name.
- Duplicate type name.
+ Nome di tipo duplicato.Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ Non sono stati generati metadati di serializzazione per il tipo '{0}'.Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ Non sono stati generati metadati di serializzazione per il tipo.Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ 派生した 'JsonSerializerContext'型 '{0}' は、JSON シリアル化可能な型を指定します。ソース生成を開始するには、型と含まれているすべての型を部分的にする必要があります。Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ 派生した 'JsonSerializerContext' 型と含まれているすべての型は部分的である必要があります。There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ {0} と名前が付けられた種類が複数あります。最初に検出されたものに対してソースが生成されました。この問題を解決するには、'JsonSerializableAttribute.TypeInfoPropertyName' を使用します。Duplicate type name.
- Duplicate type name.
+ 重複した種類名。Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ '{0}'型 のシリアル化メタデータを生成ませんでした。Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ 型のシリアル化メタデータが生成されません。Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ 파생된 'JsonSerializerContext' 유형 '{0}'은(는) JSON 직렬화 가능한 유형을 지정합니다. 소스 생성을 위해 유형 및 모든 포함 유형을 부분적으로 만들어야 합니다.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ 파생된 'JsonSerializerContext' 형식과 포함하는 모든 형식은 부분이어야 합니다.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ 이름이 {0}인 형식이 여러 개 있습니다. 처음 검색한 원본에 대해 원본이 생성되었습니다. 이 충돌을 해결하려면 'JsonSerializableAttribute.TypeInfoPropertyName'을 사용하세요.Duplicate type name.
- Duplicate type name.
+ 중복된 형식 이름입니다.Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ '{0}' 형식에 대한 직렬화 메타데이터가 생성되지 않았습니다.Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ 형식에 대한 직렬화 메타데이터가 생성되지 않았습니다.Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ Pochodny typ "JsonSerializerContext" "{0}" określa typy możliwe do serializacji w notacji JSON. Typ i wszystkie zawierające typy muszą być częściowe, aby uruchomić generowanie źródła.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ Pochodne typy "JsonSerializerContext" i wszystkich zawierające typy muszą być częściowe.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ Istnieje wiele typów o nazwie {0}. Wygenerowano źródło dla pierwszego wykrytego elementu. Aby rozwiązać tę kolizję, użyj „JsonSerializableAttribute. TypeInfoPropertyName”.Duplicate type name.
- Duplicate type name.
+ Zduplikowana nazwa typu.Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ Nie wygenerowano metadanych serializacji dla typu „{0}”.Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ Nie wygenerowano metadanych serializacji dla typu.Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ O tipo 'JsonSerializerContext' derivado '{0}' especifica tipos serializáveis por JSON. O tipo e todos os tipos de contenção devem ser feitos parcialmente para iniciar a geração de origem.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ Os tipos derivados de 'JsonSerializerContext' e todos os tipos contidos devem ser parciais.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ Existem vários tipos chamados {0}. A fonte foi gerada para o primeiro detectado. Use 'JsonSerializableAttribute.TypeInfoPropertyName' para resolver esta colisão.Duplicate type name.
- Duplicate type name.
+ Nome de tipo duplicado.Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ Não gerou metadados de serialização para o tipo '{0}'.Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ Não gerou metadados de serialização para o tipo.Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ Производный тип "JsonSerializerContext"{0}' указывает сериализуемые типы в формате JSON. Тип и все содержащие типы необходимо сделать частичными для начала генерации источника.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ Производные типы "JsonSerializerContext" и все содержащие типы должны быть частичными.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ Существует несколько типов с именем {0}. Исходный код сформирован для первого обнаруженного типа. Используйте JsonSerializableAttribute.TypeInfoPropertyName для устранения этого конфликта.Duplicate type name.
- Duplicate type name.
+ Дублирующееся имя типа.Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ Метаданные сериализации для типа "{0}" не сформированы.Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ Метаданные сериализации для типа не сформированы.Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ Türetilmiş 'JsonSerializerContext' türü '{0}' JSON ile seri hale getirilebilir türleri belirtir. kaynak oluşturmayı başlatmak için bu türün ve bu türü içeren tüm türlerin kısmi yapılması gerekir.Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ Türetilmiş 'JsonSerializerContext' türleri ve bunları içeren tüm türler kısmi olmalıdır.There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ {0} adını taşıyan birden çok tür var. Kaynak, algılanan ilk tür için oluşturuldu. Bu çarpışmayı çözmek için 'JsonSerializableAttribute.TypeInfoPropertyName' özelliğini kullanın.Duplicate type name.
- Duplicate type name.
+ Yinelenen tür adı.Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ '{0}' türü için serileştirme meta verileri oluşturulmadı.Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ Tür için serileştirme meta verileri oluşturulmadı.Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ 派生的 “JsonSerializerContext” 类型“{0}”指定 JSON-serializable 类型。该类型和所有包含类型必须设为部分,以启动源生成。Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ 派生的 “JsonSerializerContext” 类型以及所有包含类型必须是部分。There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ 有多个名为 {0} 的类型。已为第一个检测到类型的生成源。请使用 'JsonSerializableAttribute.TypeInfoPropertyName' 以解决此冲突。Duplicate type name.
- Duplicate type name.
+ 重复的类型名称。Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ 未生成类型 '{0}' 的序列化元数据。Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ 未生成类型的序列化元数据。Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
- Derived 'JsonSerializerContext' type '{0}' specifies JSON-serializable types. The type and all containing types must be made partial to kick off source generation.
+ 衍生的 'JsonSerializerContext' 型別 '{0}' 指定了 JSON 可序列化類型。類型和所有包含類型必須設為部份,才可開始產生原始檔。Derived 'JsonSerializerContext' types and all containing types must be partial.
- Derived 'JsonSerializerContext' types and all containing types must be partial.
+ 衍生的 'JsonSerializerContext' 類型和所有包含類型必須是部份。There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
- There are multiple types named {0}. Source was generated for the first one detected. Use 'JsonSerializableAttribute.TypeInfoPropertyName' to resolve this collision.
+ 有多個名為 {0} 的類型。已為偵測到的第一個項目產生來源。請使用 'JsonSerializableAttribute.TypeInfoPropertyName' 解決此衝突。Duplicate type name.
- Duplicate type name.
+ 重複類型名稱。Did not generate serialization metadata for type '{0}'.
- Did not generate serialization metadata for type '{0}'.
+ 未產生類型 '{0}' 的序列化中繼資料。Did not generate serialization metadata for type.
- Did not generate serialization metadata for type.
+ 未產生類型的序列化中繼資料。