diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/MicrosoftCodeQualityAnalyzersResources.resx b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/MicrosoftCodeQualityAnalyzersResources.resx index 0f2e968289..30fe460d09 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/MicrosoftCodeQualityAnalyzersResources.resx +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/MicrosoftCodeQualityAnalyzersResources.resx @@ -240,30 +240,15 @@ ComVisibleAttribute determines how COM clients access managed code. Good design dictates that assemblies explicitly indicate COM visibility. COM visibility can be set for the whole assembly and then overridden for individual types and type members. If this attribute is not present, the contents of the assembly are visible to COM clients. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - Mark attributes with AttributeUsageAttribute - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Specify AttributeUsage on {0} - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - Define accessors for attribute arguments - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Add a public read-only property accessor for positional argument {0} of Attribute {1} @@ -385,9 +370,6 @@ A type implements the equality or inequality operator and does not implement the opposite operator. - - Operators should have symmetrical overloads - Collection properties should be read only @@ -523,9 +505,6 @@ Add the following constructor to {0}: {1} - - Change the accessibility of {0} to {1}. - Nested types should not be visible @@ -932,18 +911,6 @@ Avoid using cref tags with a prefix - - Review unused parameters - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - - - Remove unused parameter - Do not ignore method results diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.cs.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.cs.xlf index a70fbc9a1a..57315650ef 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.cs.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.cs.xlf @@ -457,46 +457,21 @@ Atribut ComVisible určuje, jak klienti modelu COM přistupují ke spravovanému kódu. Správný návrh vyžaduje, aby sestavení explicitně označovala viditelnost modelu COM. Viditelnost modelu COM lze nastavit pro celé sestavení a následně přepsat pro jednotlivé typy a členy typů. Pokud tento atribut neexistuje, je obsah sestavení viditelný klientům modelu COM. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - Protože sestavení {0} zpřístupňuje externě viditelné typy, označte ho pomocí ComVisible(false) na úrovni sestavení a pak označte všechny typy v tomto sestavení, které mají být zpřístupněny klientům modelu COM, pomocí ComVisible(true). - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - Zvažte změnu atributu ComVisible u sestavení {0} na false a jeho připojení na úrovni typu. - - Mark attributes with AttributeUsageAttribute Označte atributy atributem AttributeUsage. - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Když definujete vlastní atribut, označte ho atributem AttributeUsage, který označuje, kde ve zdrojovém kódu se dá tento vlastní atribut použít. Význam a zamýšlené použití atributu určí jeho platné umístění v kódu. - - Specify AttributeUsage on {0} Určete AttributeUsage pro {0}. - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - Přestože atribut {0} dědí AttributeUsage od svého základního typu, měli byste zvážit explicitní určení AttributeUsage u tohoto typu kvůli zlepšení přehlednosti a dokumentace kódu. - - Define accessors for attribute arguments Definujte přístupové objekty pro argumenty atributů. - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Atributy mohou definovat povinné argumenty, které musí být zadané, když atribut použijete u nějakého cíle. Označují se také jako poziční argumenty, protože se konstruktorům atributů předávají jako poziční parametry. Pro každý povinný argument má tento atribut poskytovat také odpovídající vlastnost jen pro čtení, aby se hodnota argumentu dala načíst v době provádění. Atributy můžou definovat rovněž nepovinné argumenty, které se označují také jako pojmenované argumenty. Tyto argumenty se předávají konstruktorům atributů pomocí názvu a mají mít odpovídající vlastnost pro čtení a zápis. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} Přidejte přístupový objekt veřejné vlastnosti jen pro čtení pro poziční argument {0} atributu {1}. @@ -697,11 +672,6 @@ Některý typ implementuje operátor rovnosti nebo nerovnosti, ale neimplementuje opačný operátor. - - Operators should have symmetrical overloads - Operátory mají mít symetrická přetížení. - - Collection properties should be read only Vlastnosti kolekce mají být jen pro čtení. @@ -927,11 +897,6 @@ Přidejte k {0} následující konstruktor: {1}. - - Change the accessibility of {0} to {1}. - Změňte přístupnost {0} na {1}. - - Nested types should not be visible Vnořené typy nemají být viditelné. @@ -1682,26 +1647,6 @@ Neplatná položka v souboru specifikace pravidel metrik kódu - - Review unused parameters - Zkontrolujte nepoužité parametry. - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - Vyhněte se v kódu nepoužitým parametrům. Pokud parametr nelze odebrat, změňte jeho název tak, aby začínal podtržítkem, za kterým volitelně následuje celé číslo, například _, _1, _2 atd. Tyto řetězce se považují za názvy speciálních symbolů pro vyřazení. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - Parametr {0} metody {1} se vůbec nepoužívá. Odeberte tento parametr nebo ho použijte v těle metody. - - - - Remove unused parameter - Odebrat nepoužívaný parametr - - Do not ignore method results Neignorujte výsledky metod. diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.de.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.de.xlf index c08c1acd32..d5f8cc0336 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.de.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.de.xlf @@ -457,46 +457,21 @@ Über ComVisibleAttribute wird festgelegt, wie COM-Clients auf verwalteten Code zugreifen. Ein gutes Design gibt vor, dass Assemblys explizit auf COM-Sichtbarkeit hinweisen. COM-Sichtbarkeit kann für die ganze Assembly festgelegt und dann für einzelne Typen und Typenmember außer Kraft gesetzt werden. Wenn dieses Attribut nicht vorhanden ist, ist der Inhalt der Assembly für COM-Clients sichtbar. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - Da "{0}" extern sichtbare Typen verfügbar macht, setzen Sie auf Assemblyebene eine Markierung mit "ComVisible(false)", und markieren Sie dann alle Typen innerhalb der Assembly, die für COM-Clients verfügbar gemacht werden sollen, mit "ComVisible(true)". - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - Ziehen Sie in Betracht, das ComVisible-Attribut für "{0}" in "false" zu ändern und auf Typebene zu aktivieren. - - Mark attributes with AttributeUsageAttribute Attribute mit AttributeUsageAttribute markieren - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Wenn Sie ein benutzerdefiniertes Attribut definieren, markieren Sie es mit "AttributeUsageAttribute", um darauf hinzuweisen, wo im Quellcode das benutzerdefinierte Attribut angewendet werden kann. Die gültigen Stellen im Code werden durch die Bedeutung und beabsichtigte Verwendung eines Attributs festgelegt. - - Specify AttributeUsage on {0} Geben Sie "AttributeUsage" für "{0}" an. - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - Auch wenn das Attribut "{0}" die AttributeUsage von seinem Basistyp erbt, sollten Sie erwägen, AttributeUsage für den Typ explizit anzugeben, um die Lesbarkeit und Dokumentation des Codes zu verbessern. - - Define accessors for attribute arguments Zugriffsmethoden für Attributargumente definieren - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Attribute können obligatorische Argumente definieren, die beim Anwenden des Attributs auf ein Ziel angegeben werden müssen. Diese werden auch als positionelle Argumente bezeichnet, weil sie den Attributkonstruktoren als Positionsparameter bereitgestellt werden. Für jedes obligatorische Argument muss das Attribut auch eine entsprechende schreibgeschützte Eigenschaft angeben, damit der Wert des Arguments bei Ausführungszeit abgerufen werden kann. Attribute können zudem optionale Argumente definieren, die auch als benannte Argumente bezeichnet werden. Diese Argumente werden Attributkonstruktoren mit Namen angegeben und benötigen eine entsprechende Lese-/Schreibeigenschaft. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} Fügen Sie eine öffentliche schreibgeschützte Zugriffsmethode für das positionelle Argument "{0}" des Attributs "{1}" hinzu. @@ -697,11 +672,6 @@ Ein Typ implementiert den Operator für Gleichheit oder Ungleichheit und implementiert nicht den gegenteiligen Operator. - - Operators should have symmetrical overloads - Operatoren müssen symmetrische Überladungen aufweisen - - Collection properties should be read only Sammlungseigenschaften müssen schreibgeschützt sein @@ -927,11 +897,6 @@ Fügen Sie "{0}" den folgenden Konstruktor hinzu: {1}. - - Change the accessibility of {0} to {1}. - Ändern Sie die Zugänglichkeit von "{0}" in "{1}". - - Nested types should not be visible Geschachtelte Typen dürfen nicht sichtbar sein @@ -1682,26 +1647,6 @@ Ungültiger Eintrag in der Spezifikationsdatei für die Codemetrikregeln. - - Review unused parameters - Nicht verwendete Parameter überprüfen - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - Vermeiden Sie nicht verwendete Parameter in Ihrem Code. Wenn der Parameter nicht entfernt werden kann, ändern Sie dessen Namen so, dass er mit einem Unterstrich beginnt, dem optional eine Zahl angefügt wird. Beispiel: "_", "_1", "_2" usw. Diese werden als spezielle Symbolnamen für Ausschussparameter behandelt. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - Der Parameter "{0}" der Methode "{1}" wird niemals verwendet. Entfernen Sie den Parameter, oder verwenden Sie ihn im Methodentext. - - - - Remove unused parameter - Nicht verwendete Parameter entfernen - - Do not ignore method results Methodenergebnisse nicht ignorieren diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.es.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.es.xlf index 363d384a75..0cc9839165 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.es.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.es.xlf @@ -457,46 +457,21 @@ El atributo ComVisibleAttribute determina cómo acceden los clientes COM al código administrado. Los procedimientos de diseño recomendados dictan que los ensamblados indiquen explícitamente la visibilidad COM. La visibilidad COM se puede establecer para un ensamblado completo y, después, invalidarse para miembros de tipo y tipos individuales. Si este atributo no está presente, el contenido del ensamblado es visible para los clientes COM. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - Puesto que {0} expone tipos visibles externamente, márquelo con ComVisible(false) en el nivel de ensamblado y, después, marque todos los tipos del ensamblado que se deben exponer a clientes COM con ComVisible(true). - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - Considere cambiar el atributo ComVisible de {0} a false e incluirlo en el nivel de tipo. - - Mark attributes with AttributeUsageAttribute Marcar atributos con AttributeUsageAttribute - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Al definir un atributo personalizado, márquelo con AttributeUsageAttribute para indicar dónde se puede aplicar el atributo personalizado en el código fuente. El significado de un atributo y el uso que se le va a dar determinará sus ubicaciones válidas en el código. - - Specify AttributeUsage on {0} Especifique AttributeUsage en {0}. - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - Aunque el atributo {0} hereda AttributeUsage del tipo base, debe considerar especificar de forma explícita AttributeUsage en el tipo para mejorar la legibilidad del código y la documentación. - - Define accessors for attribute arguments Definir descriptores de acceso para los argumentos de atributo - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Los atributos pueden definir argumentos obligatorios que deben especificarse al aplicar el atributo a un destino. Estos también se conocen como argumentos posicionales porque se proporcionan a los constructores de atributos como parámetros posicionales. Para cada argumento obligatorio, el atributo debe proporcionar también una propiedad de solo lectura correspondiente, de modo que el valor del argumento se pueda recuperar en tiempo de ejecución. Los atributos pueden definir además argumentos opcionales, también conocidos como argumentos con nombre. Estos argumentos se proporcionan a los constructores de atributos por nombre y deben tener una propiedad de lectura/escritura correspondiente. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} Agregue un descriptor de acceso de propiedades público de solo lectura para el argumento posicional {0} del atributo {1}. @@ -697,11 +672,6 @@ Un tipo implementa el operador de igualdad o de desigualdad y no implementa el operador opuesto. - - Operators should have symmetrical overloads - Los operadores deben tener sobrecargas simétricas - - Collection properties should be read only Las propiedades de colección deben ser de solo lectura @@ -927,11 +897,6 @@ Agregue el constructor siguiente a {0}: {1}. - - Change the accessibility of {0} to {1}. - Cambie la accesibilidad de {0} a {1}. - - Nested types should not be visible Los tipos anidados no deben ser visibles @@ -1682,26 +1647,6 @@ Entrada no válida en el archivo de especificación de regla de métricas de código - - Review unused parameters - Revisar parámetros sin utilizar - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - Evite los parámetros sin usar en el código. Si el parámetro no se puede quitar, cámbielo de nombre para que empiece por un carácter de subrayado, seguido opcionalmente por un entero, como "_", "_1", "_2", etc. Estos se tratan como nombres de símbolos de descarte especiales. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - El parámetro {0} del método {1} no se usa nunca. Quite el parámetro o úselo en el cuerpo del método. - - - - Remove unused parameter - Quitar parámetro no utilizado - - Do not ignore method results No omitir resultados del método diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.fr.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.fr.xlf index cf5a6d7a60..8f0aa2f868 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.fr.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.fr.xlf @@ -457,46 +457,21 @@ ComVisibleAttribute détermine la façon dont les clients COM accèdent à du code managé. Un design est correct quand les assemblys indiquent explicitement la visibilité COM. La visibilité COM peut être définie pour l'assembly tout entier, puis être remplacée pour des types et des membres de type individuels. Si cet attribut n'est pas présent, les clients COM peuvent voir le contenu de l'assembly. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - Dans la mesure où {0} expose les types visibles de manière externe, marquez-le avec ComVisible(false) au niveau de l'assembly, puis marquez tous les types dans l'assembly qui doivent être exposés aux clients COM avec ComVisible(true). - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - Changez éventuellement l'attribut ComVisible sur {0} en lui affectant la valeur false, puis intervenez au niveau du type. - - Mark attributes with AttributeUsageAttribute Marquer les attributs avec AttributeUsageAttribute - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Quand vous définissez un attribut personnalisé, marquez-le avec AttributeUsageAttribute pour indiquer où l'attribut personnalisé peut être appliqué dans le code source. La signification et l'utilisation prévue d'un attribut déterminent ses emplacements valides dans le code. - - Specify AttributeUsage on {0} Spécifiez AttributeUsage sur {0} - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - Même si l'attribut {0} hérite de AttributeUsage à partir de son type de base, vous devez spécifier explicitement AttributeUsage sur le type pour améliorer la documentation et la lisibilité du code. - - Define accessors for attribute arguments Définir des accesseurs pour les arguments d'attribut - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Les attributs peuvent définir des arguments obligatoires qui doivent être spécifiés quand vous appliquez l'attribut à une cible. Ceux-ci sont également appelés arguments positionnels, car ils sont fournis aux constructeurs d'attributs en tant que paramètres positionnels. Pour chaque argument obligatoire, l'attribut doit également fournir une propriété en lecture seule correspondante pour que la valeur de l'argument puisse être récupérée au moment de l'exécution. Les attributs peuvent également définir des arguments facultatifs, qui sont également appelés arguments nommés. Ces arguments sont fournis aux constructeurs d'attributs par nom et doivent disposer d'une propriété en lecture/écriture correspondante. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} Ajoutez un accesseur de propriété en lecture seule pour l'argument positionnel {0} de l'attribut {1} @@ -697,11 +672,6 @@ Un type implémente l'opérateur d'égalité ou d'inégalité, et n'implémente pas l'opérateur opposé. - - Operators should have symmetrical overloads - Les opérateurs doivent contenir des surcharges symétriques - - Collection properties should be read only Les propriétés de collection doivent être en lecture seule @@ -927,11 +897,6 @@ Ajoutez le constructeur suivant à {0} : {1} - - Change the accessibility of {0} to {1}. - Changez l'accessibilité de {0} en {1}. - - Nested types should not be visible Les types imbriqués ne doivent pas être visibles @@ -1682,26 +1647,6 @@ Entrée non valide dans le fichier de spécification de règle de métrique du code - - Review unused parameters - Passer en revue les paramètres inutilisés - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - Évitez les paramètres inutilisés dans votre code. Évitez les paramètres inutilisés dans votre code. Si vous ne pouvez pas supprimer un paramètre, changez son nom en le faisant commencer par un trait de soulignement éventuellement suivi d'un entier, par exemple '_', '_1', '_2', etc. Ces types d'élément sont traités en tant que noms de symboles discard spéciaux. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - Le paramètre {0} de la méthode {1} n'est jamais utilisé. Supprimez le paramètre ou utilisez-le dans le corps de la méthode. - - - - Remove unused parameter - Supprimer le paramètre inutilisé - - Do not ignore method results Ne pas ignorer les résultats des méthodes diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.it.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.it.xlf index 479ed27b77..c79ac37014 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.it.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.it.xlf @@ -457,46 +457,21 @@ ComVisibleAttribute determina il modo in cui i client COM accedono al codice gestito. In una buona progettazione gli assembly devono indicare in modo esplicito la visibilità COM. È possibile impostare la visibilità COM per l'intero assembly e quindi eseguirne l'override per singoli tipi e membri dei tipi. Se questo attributo non è presente, il contenuto dell'assembly è visibile ai client COM. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - Dal momento che {0} espone tipi visibili esternamente, contrassegnarlo con ComVisible(false) a livello di assembly e quindi contrassegnare con ComVisible(true) tutti i tipi all'interno dell'assembly che devono essere esposti ai client COM. - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - Provare a impostare su false l'attributo ComVisible su {0} e ad acconsentire in modo esplicito a livello di tipo. - - Mark attributes with AttributeUsageAttribute Contrassegnare gli attributi con AttributeUsageAttribute - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Quando si definisce un attributo personalizzato, contrassegnarlo usando AttributeUsageAttribute per indicare la posizione in cui applicare l'attributo personalizzato nel codice sorgente. Il significato e l'utilizzo previsto di un attributo ne determinano le posizioni valide nel codice. - - Specify AttributeUsage on {0} Specificare AttributeUsage su {0} - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - Anche se l'attributo {0} eredita AttributeUsage dal relativo tipo di base, è consigliabile provare a specificare esplicitamente AttributeUsage sul tipo per migliorare la documentazione e la leggibilità del codice. - - Define accessors for attribute arguments Definire le funzioni di accesso per gli argomenti degli attributi - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Gli attributi possono definire argomenti obbligatori che devono essere specificati quando si applica l'attributo a una destinazione. Sono inoltre noti come argomenti posizionali perché vengono forniti ai costruttori di attributi come parametri posizionali. Per ogni argomento obbligatorio l'attributo deve fornire anche una proprietà di sola lettura corrispondente, in modo che il valore dell'argomento possa essere recuperato in fase di esecuzione. Gli attributi possono inoltre definire argomenti facoltativi, noti anche come argomenti predefiniti. Questi argomenti vengono forniti ai costruttori di attributi in base al nome e devono includere una proprietà di lettura/scrittura corrispondente. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} Aggiungere una funzione di accesso alla proprietà di sola lettura public per l'argomento posizionale {0} dell'attributo {1} @@ -697,11 +672,6 @@ Un tipo implementa l'operatore di uguaglianza o di disuguaglianza e non implementa l'operatore opposto. - - Operators should have symmetrical overloads - Per gli operatori devono esistere overload simmetrici - - Collection properties should be read only Le proprietà delle raccolte devono essere di sola lettura @@ -927,11 +897,6 @@ Aggiungere il costruttore seguente a {0}: {1} - - Change the accessibility of {0} to {1}. - Modificare l'accessibilità di {0} in {1}. - - Nested types should not be visible I tipi nidificati non devono essere visibili @@ -1682,26 +1647,6 @@ Voce non valida nel file di specifica delle regole per la metrica del codice - - Review unused parameters - Esaminare i parametri inutilizzati - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - Evitare parametri inutilizzati nel codice. Se non è possibile rimuovere il parametro, modificarne il nome in modo che inizi con un carattere di sottolineatura e, facoltativamente, sia seguito da un numero intero, seguito da un numero intero, ad esempio '_', '_1', '_1', '_2' e così via. Questi vengono considerati come nomi di simboli speciali di rimozione. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - Il parametro {0} del metodo {1} non viene mai usato. Rimuovere il parametro o usarlo nel corpo del metodo. - - - - Remove unused parameter - Rimuovere il parametro inutilizzato - - Do not ignore method results Non ignorare i risultati del metodo diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ja.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ja.xlf index a376e27e26..218888569f 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ja.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ja.xlf @@ -457,46 +457,21 @@ ComVisibleAttribute によって、COM クライアントからマネージ コードにアクセスする方法を決定します。この場合、アセンブリが COM の参照可能性を明示的に示すことが推奨されます。COM の参照可能性は、アセンブリ全体で設定した後、個々の型と型メンバーに対してオーバーライドできます。この属性が存在しない場合、アセンブリのコンテンツは COM クライアントから参照できます。 - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - {0} は外部から参照可能な型を公開するため、アセンブリ レベルで ComVisible(false) に設定し、COM クライアントに公開する必要があるアセンブリ内のすべての型を ComVisible(true) に設定します。 - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - {0} の ComVisible 属性を false に変更してから、各型レベルで調節することを検討してください。 - - Mark attributes with AttributeUsageAttribute 属性を AttributeUsageAttribute に設定します - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - カスタム属性を定義する場合、AttributeUsageAttribute を使用して、ソース コード内でカスタム属性を適用できる位置を示すように設定します。属性の意味と用途により、コード内での有効な位置が決まります。 - - Specify AttributeUsage on {0} AttributeUsage を {0} で指定してください - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - 属性 {0} がその基本データ型から AttributeUsage を継承した場合でも、コードの読みやすさ、ドキュメントを改善するために、AttributeUsage をその型で明示的に指定することを検討してください。 - - Define accessors for attribute arguments 属性引数にアクセサーを定義します - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - 属性は、対象に適用するときに指定する必要のある必須の引数を定義できます。これらは、属性コンストラクターに位置指定パラメーターとして指定されるため、位置指定引数とも呼ばれます。必須の属性ごとに、属性は、引数の値を実行時に取得できるように、対応する読み取り専用プロパティも提供する必要があります。また、属性は省略可能な引数も定義できます。これは名前付き引数とも呼ばれます。これらの引数は、名前で属性コンストラクターに指定され、対応する読み取り/書き込みプロパティが必要です。 - - Add a public read-only property accessor for positional argument {0} of Attribute {1} 属性 {1} の位置引数 {0} 用にパブリックな読み取り専用プロパティ アクセサーを追加します @@ -697,11 +672,6 @@ 型で等値演算子または非等値演算子を実装し、逆の働きをする演算子を実装しません。 - - Operators should have symmetrical overloads - 演算子は対称型オーバーロードを含まなければなりません - - Collection properties should be read only コレクション プロパティは読み取り専用でなければなりません @@ -927,11 +897,6 @@ 次のコンストラクターを {0} に追加してください。{1} - - Change the accessibility of {0} to {1}. - {0} のアクセシビリティを {1} に変更します。 - - Nested types should not be visible 入れ子にされた型を参照可能にすることはできません @@ -1682,26 +1647,6 @@ コード メトリック ルール仕様ファイル内のエントリが無効です - - Review unused parameters - 使用されていないパラメーターの確認 - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - コード内に使用されないパラメーターを指定しないでください。パラメーターを削除できない場合は、パラメーターの名前をアンダースコアの後にオプションで整数が続く名前 ('_'、'_1'、'_2' など) に変更してください。これらは、特別なディスカード シンボル名として扱われます。 - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - {1} のパラメーター {0} は使用されていません。パラメーターを削除するか、メソッド本体で使用してください。 - - - - Remove unused parameter - 使用されていないパラメーターの削除 - - Do not ignore method results メソッドの結果を無視しない diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ko.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ko.xlf index 308bb64755..203171119b 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ko.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ko.xlf @@ -457,46 +457,21 @@ ComVisibleAttribute는 COM 클라이언트가 관리 코드에 액세스하는 방법을 결정합니다. 어셈블리가 명시적으로 COM 표시 유형 지정하는 것이 좋습니다. COM 표시 유형은 전체 어셈블리에 대해 설정된 다음 개별 형식과 형식 멤버에 대해 재정의될 수 있습니다. 이 특성이 표시되지 않는 경우 어셈블리 콘텐츠는 COM 클라이언트에 표시되지 않습니다. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - {0}이(가) 외부에 표시되는 형식을 노출하므로 어셈블리 수준에서 ComVisible(false)로 표시한 다음 COM 클라이언트에서 ComVisible(true)로 노출되어야 하는 어셈블리 내에서 모든 형식을 표시하세요. - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - {0}에서 ComVisible 특성을 false로 변경하고 형식 수준에서 선택하세요. - - Mark attributes with AttributeUsageAttribute AttributeUsageAttribute로 특성을 표시하세요. - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - 사용자 지정 특성을 정의하는 경우 AttributeUsageAttribute를 사용하여 표시하고 사용자 지정 특성이 적용될 수 있는 소스 코드 위치를 나타내세요. 특성의 의미와 용도가 해당 특성의 유효한 코드 위치를 결정합니다. - - Specify AttributeUsage on {0} {0}에서 AttributeUsage를 지정하세요. - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - {0} 특성이 해당 특성의 기본 형식에서 AttributeUsage를 상속해도 형식에서 AttributeUsage를 명시적으로 지정하여 코드 가독성과 문서 품질을 향상시켜야 합니다. - - Define accessors for attribute arguments 특성 인수의 접근자를 정의하세요. - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - 특성은 대상에 특성을 적용할 때 지정되어야 하는 필수 인수를 정의할 수 있습니다. 필수 인수는 위치 매개 변수로 특성 생성자에 제공되기 때문에 위치 인수라고도 알려져 있습니다. 모든 필수 인수에 대해 특성은 인수 값이 실행 시간에 검색될 수 있도록 해당 읽기 전용 속성도 제공해야 합니다. 특성은 명명된 인수라고도 알려진 선택적 인수를 정의할 수도 있습니다. 선택적 인수는 특성 생성자에 이름별로 제공되며 해당 읽기/쓰기 속성을 가지고 있어야 합니다. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} {1} 특성의 위치 인수 {0}에 대한 공개 읽기 전용 속성 접근자를 추가하세요. @@ -697,11 +672,6 @@ 형식은 같음 또는 같지 않음 연산자를 구현하지만 반대 연산자는 구현하지 않습니다. - - Operators should have symmetrical overloads - 연산자에는 대칭 오버로드가 있어야 합니다. - - Collection properties should be read only 컬렉션 속성은 읽기 전용이어야 합니다. @@ -927,11 +897,6 @@ {1} 생성자를 {0}에 추가하세요. - - Change the accessibility of {0} to {1}. - {0}의 접근성을 {1}(으)로 변경하세요. - - Nested types should not be visible 중첩 형식을 표시하지 않아야 합니다. @@ -1682,26 +1647,6 @@ 코드 메트릭 규착 사양 파일의 잘못된 항목 - - Review unused parameters - 사용하지 않는 매개 변수를 검토하세요. - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - 코드에 사용되지 않는 매개 변수를 사용하지 않도록 합니다. 매개 변수를 제거할 수 없는 경우 이름을 변경하여 밑줄로 시작하고 필요에 따라 뒤에 정수가 있도록 합니다(예: '_', '_1', '_2' 등). 해당 이름은 특수 무시 기호 이름으로 처리됩니다. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - {1} 메서드의 {0} 매개 변수가 사용되지 않았습니다. 매개 변수를 제거하거나 메서드 본문에 사용하세요. - - - - Remove unused parameter - 사용하지 않는 매개 변수를 제거하세요. - - Do not ignore method results 메서드 결과를 무시하지 마세요. diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.pl.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.pl.xlf index fcaa9c2969..5f12afd635 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.pl.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.pl.xlf @@ -457,46 +457,21 @@ Atrybut ComVisibleAttribute określa, w jaki sposób klienci modelu COM uzyskują dostęp do kodu zarządzanego. Zasady poprawnego projektowania nakazują, aby zestawy jawnie deklarowały widoczność modelu COM. Widoczność modelu COM można ustawić dla całego zestawu, a następnie przesłonić dla poszczególnych typów i elementów członkowskich typów. Jeśli nie ma tego atrybutu, zawartość zestawu jest widoczna dla klientów modelu COM. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - Ponieważ zestaw {0} udostępnia typy widoczne zewnętrznie, oznacz go atrybutem ComVisible(false) na poziomie zestawu, a następnie oznacz atrybutem ComVisible(true) wszystkie typy w zestawie, które powinny być dostępne dla klientów modelu COM. - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - Rozważ zmianę atrybutu ComVisible dla zestawu {0} na wartość false i użycie wartości true na poziomie typów. - - Mark attributes with AttributeUsageAttribute Oznacz atrybuty za pomocą atrybutu AttributeUsageAttribute - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Przy definiowaniu atrybutu niestandardowego oznacz go za pomocą atrybutu AttributeUsageAttribute, aby wskazać, gdzie można stosować ten atrybut niestandardowy w kodzie źródłowym. Znaczenie i zamierzone użycie atrybutu określi jego prawidłowe lokalizacje w kodzie. - - Specify AttributeUsage on {0} Określ atrybut AttributeUsage dla elementu {0} - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - Mimo że atrybut {0} dziedziczy atrybut AttributeUsage ze swojego typu podstawowego, rozważ jawne określenie atrybutu AttributeUsage dla typu w celu ulepszenia czytelności kodu i dokumentacji. - - Define accessors for attribute arguments Zdefiniuj metody dostępu dla argumentów atrybutów - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Atrybuty mogą definiować argumenty obowiązkowe, które muszą zostać określone podczas stosowania atrybutu do elementu docelowego. Są one też nazywane argumentami pozycyjnymi, ponieważ są przekazywane do konstruktorów atrybutu jako parametry pozycyjne. Dla każdego argumentu obowiązkowego atrybut powinien także określać odpowiednią właściwość tylko do odczytu, która umożliwia pobranie wartości argumentu w czasie wykonywania. Atrybuty mogą także definiować argumenty opcjonalne, określane też jako argumenty nazwane. Te argumenty są przekazywane do konstruktorów atrybutu za pomocą nazwy i powinny mieć odpowiednią właściwość do odczytu i zapisu. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} Dodaj publiczną metodę dostępu do właściwości tylko do odczytu dla argumentu pozycyjnego {0} atrybutu {1} @@ -697,11 +672,6 @@ Typ implementuje operator równości lub nierówności i nie implementuje operatora przeciwnego. - - Operators should have symmetrical overloads - Operatory powinny mieć symetryczne przeciążenia - - Collection properties should be read only Właściwości kolekcji powinny być dostępne tylko do odczytu @@ -927,11 +897,6 @@ Dodaj następujący konstruktor do elementu {0}: {1} - - Change the accessibility of {0} to {1}. - Zmień dostępność elementu {0} na {1}. - - Nested types should not be visible Typy zagnieżdżone nie powinny być widoczne @@ -1682,26 +1647,6 @@ Nieprawidłowy wpis w pliku specyfikacji reguły metryk kodu - - Review unused parameters - Sprawdź nieużywane parametry - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - Unikaj nieużywanych parametrów w kodzie. Jeśli nie można usunąć parametru, zmień jego nazwę, tak aby rozpoczynała się od znaku podkreślenia, a opcjonalnie następowała po niej liczba całkowita, taka jak „_”, „_1”, „_2” itp. Są one traktowane jako specjalne nazwy symboli odrzucenia. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - Parametr {0} metody {1} nie jest nigdy używany. Usuń parametr lub użyj go w treści metody. - - - - Remove unused parameter - Usuń nieużywany parametr - - Do not ignore method results Nie ignoruj wyników metody diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.pt-BR.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.pt-BR.xlf index cb02e49551..fa3a522681 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.pt-BR.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.pt-BR.xlf @@ -457,46 +457,21 @@ ComVisibleAttribute determina como os clientes COM acessam o código gerenciado. O bom design dita que os assemblies indicam explicitamente a visibilidade COM. A visibilidade COM pode ser definida para todo o assembly e, em seguida, substituída para tipos individuais e membros de tipo. Se o atributo não estiver presente, o conteúdo do assembly estará visível para clientes COM. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - Já que {0} expõe os tipos visíveis externamente, marque-o com ComVisible(false) no nível de assembly e marque todos os tipos dentro do assembly que devem ser expostos a clientes COM com ComVisible(true). - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - Considere alterar o atributo ComVisible em {0} para false e aceitá-lo no nível de tipo. - - Mark attributes with AttributeUsageAttribute Marcar atributos com AttributeUsageAttribute - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Quando você definir um atributo personalizado, marque-o usando AttributeUsageAttribute para indicar o local no código-fonte em que o atributo personalizado poderá ser aplicado. O significado e o uso pretendido de um atributo determinará seus locais válidos no código. - - Specify AttributeUsage on {0} Especifique AttributeUsage em {0} - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - Mesmo que o atributo {0} herde AttributeUsage de seu tipo base, você deve considerar especificar explicitamente AttributeUsage no tipo para melhorar a documentação e a legibilidade do código. - - Define accessors for attribute arguments Definir acessadores para argumentos de atributo - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Os atributos podem definir argumentos obrigatórios que devem ser especificados quando você aplica o atributo a um destino. Eles também são conhecidos como argumentos posicionais porque são fornecidos para construtores de atributo como parâmetros posicionais. Para todo argumento obrigatório, o atributo também deve fornecer uma propriedade somente leitura correspondente para que o valor do argumento possa ser recuperado no tempo de execução. Os atributos também podem definir argumentos opcionais, também conhecidos como argumentos nomeados. Esses argumentos são fornecidos aos construtores de atributo por nome e devem ter uma propriedade leitura/gravação correspondente. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} Adicione um acessador de propriedade pública somente leitura para o argumento posicional {0} do atributo {1} @@ -697,11 +672,6 @@ Um tipo implementa o operador de igualdade ou desigualdade e não implementa o operador oposto. - - Operators should have symmetrical overloads - Os operadores devem ter sobrecargas simétricas - - Collection properties should be read only As propriedades de coleção devem ser somente leitura @@ -927,11 +897,6 @@ Adicione o construtor a seguir para {0}: {1} - - Change the accessibility of {0} to {1}. - Altere a acessibilidade de {0} para {1}. - - Nested types should not be visible Tipos aninhados não devem ser visíveis @@ -1682,26 +1647,6 @@ Entrada inválida no arquivo de especificação de regra de métricas de código - - Review unused parameters - Examinar parâmetros não utilizados - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - Evite parâmetros não usados no código. Se o parâmetro não puder ser removido, altere seu nome para que ele comece com um sublinhado e seja seguido opcionalmente por um inteiro, como '_', '_1', '_2' etc. Esses nomes são tratados como nomes de símbolo de descarte especiais. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - O parâmetro {0} do método {1} nunca é usado. Remova o parâmetro ou use-o no corpo do método. - - - - Remove unused parameter - Remover o parâmetro não utilizado - - Do not ignore method results Não ignorar resultados de métodos diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ru.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ru.xlf index 37ee1ede25..b8a2470f74 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ru.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.ru.xlf @@ -457,46 +457,21 @@ ComVisibleAttribute определяет, как COM-клиенты обращаются к управляемому коду. Принципы хорошего проектирования требуют, чтобы сборки явно указывали COM-видимость. COM-видимость можно задать для всей сборки и затем переопределить для отдельных типов и их членов. Если этот атрибут отсутствует, COM-клиенты видят содержимое сборки. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - Так как {0} публикует типы, видимые извне, пометьте его как ComVisible(false) на уровне сборки, а затем пометьте все типы в сборке, которые должны быть предоставлены COM-клиентам как ComVisible(true). - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - Рекомендуется присвоить атрибуту ComVisible {0} значение "false" и дать согласие на уровне типов. - - Mark attributes with AttributeUsageAttribute Пометить атрибуты как AttributeUsageAttribute - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Определяя настраиваемый атрибут, пометьте его с помощью AttributeUsageAttribute, чтобы указать, где можно применять исходный код этого атрибута. Значение и предназначение атрибута определяют допустимые расположения для него в коде. - - Specify AttributeUsage on {0} Укажите AttributeUsage в {0}. - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - Хотя атрибут {0} наследует AttributeUsage от своего базового типа, следует рассмотреть вариант явного указания AttributeUsage для типа, чтобы улучшить читаемость кода и его документирование. - - Define accessors for attribute arguments Определите методы доступа для аргументов атрибута - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Атрибуты могут определять обязательные аргументы, которые требуется указать при применении атрибута к целевому объекту. Их также называют позиционными аргументами, так как они предоставляются конструкторам атрибутов в качестве позиционных параметров. Для каждого обязательного аргумента атрибут должен также предоставлять соответствующее свойство доступа только для чтения, чтобы значение аргумента можно было извлечь во время выполнения. Кроме того, атрибуты могут предоставлять необязательные аргументы, которые также называются именованными. Они предоставляются конструкторам атрибутов по имени и должны иметь соответствующее свойство чтения/записи. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} Добавьте открытый метод доступа для свойства доступа только для чтения к позиционному аргументу {0} для атрибута {1}. @@ -697,11 +672,6 @@ Тип реализует оператор равенства или неравенства и не реализует противоположный оператор. - - Operators should have symmetrical overloads - Перегрузки операторов должны быть симметричными - - Collection properties should be read only Свойства коллекций должны быть доступны только для чтения @@ -927,11 +897,6 @@ Добавьте в {0} следующий конструктор: {1} - - Change the accessibility of {0} to {1}. - Измените доступность {0} на {1}. - - Nested types should not be visible Вложенные типы не должны быть видимыми @@ -1682,26 +1647,6 @@ Недопустимая запись в файле спецификации правила метрик кода - - Review unused parameters - Проверьте неиспользуемые параметры - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - Избегайте неиспользуемых параметров в коде. Если параметр не может быть удален, измените его имя так, чтобы оно начиналось с символа подчеркивания, за которым при необходимости следует целое число, например, "_", "_1", "_2" и т. д. Эти имена рассматриваются как специальные имена для освобождаемых параметров. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - Параметр {0} метода {1} не используется. Удалите этот параметр или используйте его в теле метода. - - - - Remove unused parameter - Удалите неиспользуемый параметр - - Do not ignore method results Не игнорируйте результаты метода diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.tr.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.tr.xlf index 71d317618d..f6c9709a49 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.tr.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.tr.xlf @@ -457,46 +457,21 @@ ComVisibleAttribute, COM istemcilerinin yönetilen koda nasıl erişeceğini belirler. İyi bir tasarım için bütünleştirilmiş kodlar COM görünürlüğünü açıkça belirtmelidir. COM görünürlüğü bütünleştirilmiş kodun tamamı için ayarlanabilir ve sonra tek tek türler ve tür üyeleri için geçersiz kılınabilir. Bu öznitelik yoksa, bütünleştirilmiş kodun içeriğini COM istemcileri görebilir. - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - {0} öğesi dışarıdan görünen türleri kullanıma sunduğundan, bunu bütünleştirilmiş kod düzeyinde ComVisible(false) ile işaretleyin, sonra bütünleştirilmiş kodda bulunan ve COM istemcilerinin kullanımına sunulması gereken tüm türleri ComVisible(true) ile işaretleyin. - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - {0} öğesindeki ComVisible özniteliğini false olarak değiştirmeyi ve tür düzeyinde kabul etmeyi deneyin. - - Mark attributes with AttributeUsageAttribute Öznitelikleri AttributeUsageAttribute ile işaretleyin - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - Özel bir öznitelik tanımladığınızda, özel özniteliğin kaynak kodunun neresinde uygulanabileceğini belirtmek için bunu AttributeUsageAttribute kullanarak işaretleyin. Bir özniteliğin anlamı ve amaçlanan kullanımı, koddaki geçerli konumlarını belirler. - - Specify AttributeUsage on {0} {0} üzerinde AttributeUsage belirtin - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - {0} özniteliği AttributeUsage’ı temel türünden devralsa da kodun okunabilirliğini e belgeleri geliştirmek için AttributeUsage’ı açıkça belirtmeyi göz önünde bulundurmalısınız. - - Define accessors for attribute arguments Öznitelik bağımsız değişkenleri için erişimciler tanımlayın - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - Öznitelikler, özniteliği bir hedefe uygularken belirtilmesi gereken zorunlu bağımsız değişkenler tanımlayabilir. Bunlar öznitelik oluşturuculara konumsal parametreler olarak sağlandığından konumsal bağımsız değişkenler olarak da bilinir. Her zorunlu bağımsız değişken için yürütme zamanında bağımsız değişkenin değerinin alınabilmesi amacıyla öznitelik tarafından buna karşılık gelen salt okunur bir özellik de sağlanmalıdır. Öznitelikler, adlandırılmış bağımsız değişkenler olarak da bilinen isteğe bağlı bağımsız değişkenler de tanımlayabilir. Bu bağımsız değişkenler, öznitelik oluşturuculara ada göre sağlanır ve karşılık gelen bir okuma/yazma özelliğine sahip olmalıdır. - - Add a public read-only property accessor for positional argument {0} of Attribute {1} {1} Özniteliğinin {0} konumsal bağımsız değişkeni için genel bir salt okunur özellik erişimcisi ekleyin @@ -697,11 +672,6 @@ Bir tür, eşitlik veya eşitsizlik işlecini uygular ve zıt işleci uygulamaz. - - Operators should have symmetrical overloads - İşleçler simetrik aşırı yüklemelere sahip olmalıdır - - Collection properties should be read only Koleksiyon özellikleri salt okunur olmalıdır @@ -927,11 +897,6 @@ {0} öğesine şu oluşturucuyu ekleyin: {1} - - Change the accessibility of {0} to {1}. - {0} öğesinin erişilebilirliğini {1} olarak değiştirin. - - Nested types should not be visible İç içe türler görünür olmamalıdır @@ -1682,26 +1647,6 @@ Ölçüm kuralı belirtim dosyasında geçersiz giriş - - Review unused parameters - Kullanılmayan parametreleri gözden geçirin - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - Kodunuzda, kullanılmayan parametrelerden kaçının. Parametre kaldırılamıyorsa adını, bir alt çizgiyle başlayan ve isteğe bağlı olarak ardından tamsayı gelen ('_', '_1', '_2' gibi) bir değerle değiştirin. Bu değerler özel atılabilir değişken sembolü olarak işlenir. - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - {1} yönteminin {0} parametresi hiçbir zaman kullanılmıyor. Parametreyi kaldırın veya yöntem gövdesinde kullanın. - - - - Remove unused parameter - Kullanılmayan parametreyi kaldırma - - Do not ignore method results Yöntem sonuçlarını yoksaymayın diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.zh-Hans.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.zh-Hans.xlf index 8a247c7a70..7eaaf84f64 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.zh-Hans.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.zh-Hans.xlf @@ -457,46 +457,21 @@ ComVisibleAttribute 确定 COM 客户端访问托管代码的方法。好的设计要求程序集显式指示 COM 可见性。可为整个程序集设置 COM 可见性，然后为单个类型和类型成员重写。如果此属性不存在，则程序集的内容对 COM 客户端可见。 - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - 因为 {0} 公开外部可见的类型，请在程序集级别使用 ComVisible(false) 来标记它，然后使用 ComVisible(true) 来标记该程序集内应当向 COM 客户端公开的所有类型。 - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - 考虑将 {0} 的 ComVisible 属性改为 false，然后在类型级别进行选择。 - - Mark attributes with AttributeUsageAttribute 用 AttributeUsageAttribute 标记属性 - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - 定义自定义属性时，使用 AttributeUsageAttribute 标记该属性，指示可在源代码中应用该自定义属性的位置。属性的含义和目标用途确定其在代码中的有效位置。 - - Specify AttributeUsage on {0} 在 {0} 上指定 AttributeUsage - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - 虽然属性 {0} 从其基类型继承了 AttributeUsage 属性，但你还是应该考虑在该类型中显式指定 AttributeUsage 属性，以便提高代码可读性和便于文档制作。 - - Define accessors for attribute arguments 定义属性参数的访问器 - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - 属性可以定义必需参数(在向目标应用属性时，必须指定这些参数)。这些参数也称为位置参数，因为它们被作为位置参数提供给属性构造函数。对于每个必需参数，属性还应提供相应的只读属性，以便可以在执行时检索参数值。属性还可以定义可选参数，这些参数也称为命名参数。这些参数按名称提供给属性构造函数，且应具有相应的读/写属性。 - - Add a public read-only property accessor for positional argument {0} of Attribute {1} 为特性 {1} 的位置参数 {0} 添加一个公共的只读属性访问器 @@ -697,11 +672,6 @@ 类型实现相等运算符或不相等运算符，但不实现相反运算符。 - - Operators should have symmetrical overloads - 运算符应有对称重载 - - Collection properties should be read only 集合属性应为只读 @@ -927,11 +897,6 @@ 将下列构造函数添加到 {0}: {1} - - Change the accessibility of {0} to {1}. - 将 {0} 的可访问性更改为 {1}。 - - Nested types should not be visible 嵌套类型应不可见 @@ -1682,26 +1647,6 @@ 代码度量规则规范文件中的条目无效 - - Review unused parameters - 检查未使用的参数 - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - 请避免在代码中使用未使用的参数。如果无法删除该参数，请更改其名称，使其以下划线开头，也可在下划线后面跟一个整数(如 "_"、"_1"、"_2" 等)。这些被视为特殊丢弃符号名。 - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - 从未用过方法 {1} 的参数 {0}。请删除该参数或在方法体中使用它。 - - - - Remove unused parameter - 删除未使用的参数 - - Do not ignore method results 不要忽略方法结果 diff --git a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.zh-Hant.xlf b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.zh-Hant.xlf index 8d6276b1ff..62acdb514b 100644 --- a/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.zh-Hant.xlf +++ b/src/NetAnalyzers/Core/Microsoft.CodeQuality.Analyzers/xlf/MicrosoftCodeQualityAnalyzersResources.zh-Hant.xlf @@ -457,46 +457,21 @@ ComVisibleAttribute 會判斷 COM 用戶端如何存取受控程式碼。良好的設計會要求組件明確表示 COM 的可見度。可以為整個組件設定COM 的可見度，然後再對個別的類型與類型成員進行覆寫。若此屬性不存在，則 COM 用戶端可以看到組件的內容。 - - Because {0} exposes externally visible types, mark it with ComVisible(false) at the assembly level and then mark all types within the assembly that should be exposed to COM clients with ComVisible(true). - 因為 {0} 會公開外部可見的類型，所以請在組件層級將其標記為 ComVisible(false)，然後將應公開給 COM 用戶端之組件內的所有類型，標記為 ComVisible(true)。 - - - - Consider changing the ComVisible attribute on {0} to false, and opting in at the type level. - 請考慮將 {0} 上的 ComVisible 屬性變更為 false，並於類型層級選擇加入。 - - Mark attributes with AttributeUsageAttribute 將屬性標記為 AttributeUsageAttribute - - When you define a custom attribute, mark it by using AttributeUsageAttribute to indicate where in the source code the custom attribute can be applied. The meaning and intended usage of an attribute will determine its valid locations in code. - 當您定義自訂屬性時，請使用 AttributeUsageAttribute 進行標記，以指出可以在原始程式碼的何處套用自訂屬性。屬性的意義與預期用法將可決定其在程式碼中的有效位置。 - - Specify AttributeUsage on {0} 在 {0} 上指定 AttributeUsage - - Even though attribute {0} inherits AttributeUsage from its base type, you should consider explicitly specifying AttributeUsage on the type to improve code readability and documentation. - 即使屬性 {0} 自其基底類型繼承 AttributeUsage，仍應考慮在類型上明確指定 AttributeUsage，以改善程式碼可讀性與記錄功能。 - - Define accessors for attribute arguments 為屬性引數定義存取子 - - Attributes can define mandatory arguments that must be specified when you apply the attribute to a target. These are also known as positional arguments because they are supplied to attribute constructors as positional parameters. For every mandatory argument, the attribute should also provide a corresponding read-only property so that the value of the argument can be retrieved at execution time. Attributes can also define optional arguments, which are also known as named arguments. These arguments are supplied to attribute constructors by name and should have a corresponding read/write property. - 屬性可以定義在將屬性套用至目標時所必須指定的強制引數。因為這些引數會以位置參數提供給屬性建構函式，所以它們也稱為位置引數。對於每個強制引數而言，屬性 (Attribute) 還需提供對應的唯讀屬性 (Property)，才可以在執行時期擷取引數值。屬性也可定義選擇性引數，也稱為具名引數。這些引數會依照名稱提供給屬性 (Attribute) 建構函式，且應要有相對應的讀取/寫入屬性 (Property)。 - - Add a public read-only property accessor for positional argument {0} of Attribute {1} 為屬性 (Attribute) {1} 的位置引數 {0} 新增公用唯讀屬性 (Property) 存取子 @@ -697,11 +672,6 @@ 類型會實作等號比較運算子或不等比較運算子，但不會實作相反運算子。 - - Operators should have symmetrical overloads - 運算子應有對稱的多載 - - Collection properties should be read only 集合屬性應為唯讀 @@ -927,11 +897,6 @@ 將下列建構函式新增至 {0}: {1} - - Change the accessibility of {0} to {1}. - 將 {0} 的存取範圍變更為 {1}。 - - Nested types should not be visible 巢狀型別不應可見 @@ -1682,26 +1647,6 @@ 程式碼度量規則規格檔案中的項目無效 - - Review unused parameters - 檢閱未使用的參數 - - - - Avoid unused paramereters in your code. If the parameter cannot be removed, then change its name so it starts with an underscore and is optionally followed by an integer, such as '_', '_1', '_2', etc. These are treated as special discard symbol names. - 請避免在您的程式碼中使用參數。如果無法移除參數，請變更其名稱，使其以底線開頭，並可選擇在後面接著整數，例如 '_'、'_1'、'_2' 等。這些會視為特殊的捨棄符號名稱。 - - - - Parameter {0} of method {1} is never used. Remove the parameter or use it in the method body. - 方法 {1} 的參數 {0} 從未使用過。請移除此參數，或將其用於方法主體中。 - - - - Remove unused parameter - 移除未使用的參數 - - Do not ignore method results 請勿略過方法結果 diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/MicrosoftNetCoreAnalyzersResources.resx b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/MicrosoftNetCoreAnalyzersResources.resx index 71925b2dc4..50fc967554 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/MicrosoftNetCoreAnalyzersResources.resx +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/MicrosoftNetCoreAnalyzersResources.resx @@ -132,9 +132,6 @@ Do not call {0} on an {1} value - - Reliability - Remove redundant call @@ -147,36 +144,12 @@ P/Invoke method '{0}' should not be visible - - PInvoke declarations should be portable - - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Specify marshaling for P/Invoke string arguments A platform invoke member allows partially trusted callers, has a string parameter, and does not explicitly marshal the string. This can cause a potential security vulnerability. - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Use managed equivalents of win32 api @@ -213,12 +186,6 @@ A string comparison operation that is nonlinguistic does not set the StringComparison parameter to either Ordinal or OrdinalIgnoreCase. By explicitly setting the parameter to either StringComparison.Ordinal or StringComparison.OrdinalIgnoreCase, your code often gains speed, becomes more correct, and becomes more reliable. - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - For non-empty collections, Count() and LongCount() enumerate the entire sequence, while Any() stops at the first item or the first item that satisfies a condition. @@ -264,24 +231,6 @@ Do not lock on objects with weak identity - - Do not catch corrupted state exceptions in general handlers. - - - Do not author general catch handlers in code that receives corrupted state exceptions. - - - Do not catch corrupted state exceptions in general handlers. - - - Rethrow to preserve stack details - - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - - - Rethrow to preserve stack details - Do not raise reserved exception types @@ -309,15 +258,6 @@ Initialize all static fields in '{0}' when those fields are declared and remove the explicit static constructor - - Do not call overridable methods in constructors - - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - - - Do not call overridable methods in constructors - Disposable types should declare finalizer @@ -327,15 +267,6 @@ Disposable types should declare finalizer - - Finalizers should call base class finalizer - - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - - - Finalizers should call base class finalizer - Provide correct arguments to formatting methods @@ -915,12 +846,6 @@ Asymmetric encryption algorithm {0} is weak. Switch to an RSA with at least 2048 key size, ECDH or ECDSA algorithm instead. - - Do not use insecure cryptographic algorithm MD5. - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Do not use obsolete key derivation function @@ -942,12 +867,6 @@ Do not use ReferenceEquals with value types - - Do not use insecure cryptographic algorithm SHA1. - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Do Not Use Weak Cryptographic Algorithms @@ -1695,9 +1614,6 @@ Provide a parameterless constructor that is as visible as the containing type for concrete types derived from 'System.Runtime.InteropServices.SafeHandle' - - Add a public constructor that takes zero parameters - Make the constructor that takes zero parameters 'public' diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.cs.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.cs.xlf index 463c232cfc..cb9bc75c7e 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.cs.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.cs.xlf @@ -7,11 +7,6 @@ Přidejte k tomuto poli atribut NonSerialized - - Add a public constructor that takes zero parameters - Přidat veřejný konstruktor, který přijímá nulové parametry - - Add Serializable attribute Přidat atribut Serializable @@ -172,11 +167,6 @@ Metody Dispose by měly volat SuppressFinalize - - Reliability - Spolehlivost - - , , @@ -562,21 +552,6 @@ Při deserializaci instance třídy {0} může metoda {1} volat nebezpečnou metodu {2}. Možná volání metod: {3} - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - Když konstruktor zavolá virtuální metodu, konstruktor dané instance, která metodu vyvolala, se nemusí spustit. - - - - Do not call overridable methods in constructors - Nevolejte přepsatelné metody v konstruktorech - - - - Do not call overridable methods in constructors - Nevolejte přepsatelné metody v konstruktorech - - Do not call {0} on an {1} value Nevolejte {0} pro hodnotu {1}. @@ -587,21 +562,6 @@ Nevolejte ToImmutableCollection pro hodnotu ImmutableCollection - - Do not author general catch handlers in code that receives corrupted state exceptions. - Nevytvářejte v kódu obecné zachytávací bloky, které přijímají výjimky poškozující stav procesu. - - - - Do not catch corrupted state exceptions in general handlers. - Nezachytávejte v obecných obslužných rutinách výjimky poškozující stav procesu. - - - - Do not catch corrupted state exceptions in general handlers. - Nezachytávejte v obecných obslužných rutinách výjimky poškozující stav procesu. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource má konstruktory, které přijímají možnosti TaskCreationOptions určující příslušnou úlohu, a konstruktory, které přijímají stav objektu uložený v úloze. Když se místo TaskCreationOptions omylem předá TaskContinuationOptions, způsobí to, že volání bude možnosti považovat za stav. @@ -982,16 +942,6 @@ {0} je nezabezpečený generátor náhodných čísel. Pokud se pro zabezpečení vyžaduje náhodnost, používejte kryptograficky zabezpečené generátory náhodných čísel. - - Do not use insecure cryptographic algorithm MD5. - Nepoužívejte nezabezpečený kryptografický algoritmus MD5 - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Tento typ implementuje MD5, což je kryptograficky nezabezpečená hashovací funkce. Kolize hashovací funkce jsou výpočetně schůdné u algoritmů MD5 a HMACMD5. Nahraďte toto použití hashovacím algoritmem z řady SHA-2 (SHA512, SHA384, SHA256). - - Do not use obsolete key derivation function Nepoužívat zastaralou funkci pro odvození klíče @@ -1042,16 +992,6 @@ Nepoužívejte ReferenceEquals s typy hodnot - - Do not use insecure cryptographic algorithm SHA1. - Nepoužívejte nezabezpečený kryptografický algoritmus SHA1 - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Tento typ implementuje SHA1, což je kryptograficky nezabezpečená hashovací funkce. Kolize hashovací funkce jsou výpočetně schůdné u algoritmů SHA-1 a SHA-0. Nahraďte toto použití hashovacím algoritmem z řady SHA-2 (SHA512, SHA384, SHA256). - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. Prostor zásobníku přidělený operací stackalloc se uvolní jen na konci volání aktuální metody. Když se použije ve smyčce, může to způsobit neomezený růst zásobníku a nakonec i jeho přetečení. @@ -1247,21 +1187,6 @@ Typ {3}{0} obsahuje typ preview {1} a vyžaduje vyjádření výslovného souhlasu s funkcemi preview. Další informace najdete v {2}. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - Finalizace se musí rozšířit v hierarchii dědičnosti. Aby k tomu došlo, typy musí ve svých vlastních metodách Finalize volat metodu Finalize základní třídy. - - - - Finalizers should call base class finalizer - Finalizační metody by měly volat finalizační metodu základní třídy - - - - Finalizers should call base class finalizer - Finalizační metody by měly volat finalizační metodu základní třídy - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. Přepošlete parametr CancellationToken do metod, aby se zajistilo, že se správně rozšíří oznámení o zrušení operací. Nebo můžete předat explicitně CancellationToken.None a označit tak, že se token záměrně nebude šířit. @@ -1872,26 +1797,6 @@ {3}{0} přepíše metodu preview {1} a proto vyžaduje vyjádření výslovného souhlasu s funkcemi preview. Další informace najdete v {2}. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - Toto pravidlo vyhodnotí velikost jednotlivých parametrů a vrátí hodnotu metody P/Invoke. Při zařazení do nespravovaného kódu v 32bitových a 64bitových operačních systémech ověří, zda je velikost parametru správná. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - Podle deklarace ve vašem kódu bude mít parametr {0} metody P/Invoke {1} na platformách {3} šířku {2} bajtů. To není správné, protože skutečná nativní deklarace tohoto rozhraní API naznačuje, že na platformách {3} by měl mít šířku {4} bajtů. Nahlédněte do dokumentace k sadě MSDN Platform SDK. Pomůže vám určit datový typ, který byste měli použít místo {5}. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Podle deklarace ve vašem kódu bude mít návratový typ metody P/Invoke {0} na platformách {2} šířku {1} bajtů. To není správné, protože skutečná nativní deklarace tohoto rozhraní API naznačuje, že na platformách {2} by měl mít šířku {3} bajtů. Nahlédněte do dokumentace k sadě MSDN Platform SDK. Pomůže vám určit datový typ, který byste měli použít místo {4}. - - - - PInvoke declarations should be portable - Deklarace PInvoke by měly být přenosné - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. Veřejná nebo chráněná metoda ve veřejném typu má atribut System.Runtime.InteropServices.DllImportAttribute (také implementovaný klíčovým slovem Declare ve Visual Basicu). Tyto metody by neměly být vystaveny. @@ -2287,21 +2192,6 @@ Nahradit řetězcový literál s literálem char - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - Výjimka se vyvolá znovu s tím, že se explicitně určí ve výrazu throw. Pokud se výjimka znovu vyvolá tak, že se určí ve výrazu throw, ztratí se seznam volání metod mezi původní metodou, která výjimku vyvolala, a aktuální metodou. - - - - Rethrow to preserve stack details - Vyvolat znovu, aby se zachovaly podrobnosti zásobníku - - - - Rethrow to preserve stack details - Vyvolat znovu, aby se zachovaly podrobnosti zásobníku - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. Našlo se potenciální ohrožení zabezpečení injektáží knihovny DLL, kde {0} v metodě {1} je možné poškodit uživatelem řízenými daty z {2} v metodě {3}. @@ -2562,26 +2452,6 @@ Člen invoke platformy povoluje částečně důvěryhodné volající, má parametr řetězce a daný řetězec explicitně nezařazuje. To může potenciálně způsobit ohrožení zabezpečení. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - Pokud chcete zmenšit bezpečnostní riziko, zařaďte pole {0} jako Unicode tak, že StructLayout.CharSet na {1} nastavíte na CharSet.Unicode nebo explicitně zařadíte pole jako UnmanagedType.LPWStr. Pokud potřebujete tento řetězec zařadit jako ANSI nebo jako systémově závislý, vypněte pomocí atributu BestFitMapping přizpůsobené mapování. Pokud chcete zabezpečení ještě zvýšit, zapněte ThrowOnUnmappableChar. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Pokud chcete zmenšit bezpečnostní riziko, zařaďte pole {0} jako Unicode tak, že StructLayout.CharSet na {1} nastavíte na CharSet.Unicode nebo explicitně zařadíte pole jako UnmanagedType.LPWStr. Pokud potřebujete tento řetězec zařadit jako ANSI nebo jako systémově závislý, zadejte explicitně MarshalAs a pomocí atributu BestFitMapping vypněte přizpůsobené mapování. Zabezpečení můžete ještě zvýšit tak, že zapnete ThrowOnUnmappableChar. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Pokud chcete zmenšit bezpečnostní riziko, zařaďte parametr {0} jako Unicode tak, že DllImport.CharSet nastavíte na CharSet.Unicode nebo explicitně zařadíte parametr jako UnmanagedType.LPWStr. Pokud potřebujete tento řetězec zařadit jako ANSI nebo jako systémově závislý, nastavte BestFitMapping=false. Zabezpečení ještě zvýšíte nastavením ThrowOnUnmappableChar=true. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Pokud chcete zmenšit bezpečnostní riziko, zařaďte parametr {0} jako Unicode tak, že DllImport.CharSet nastavíte na CharSet.Unicode nebo explicitně zařadíte parametr jako UnmanagedType.LPWStr. Pokud potřebujete tento řetězec zařadit jako ANSI nebo jako systémově závislý, zadejte explicitně MarshalAs a nastavte BestFitMapping=false. Zabezpečení můžete ještě zvýšit, když nastavíte ThrowOnUnmappableChar=true. - - Specify marshaling for P/Invoke string arguments Zadání zařazení pro argumenty řetězce P/Invoke @@ -2922,16 +2792,6 @@ Operace porovnání řetězců, která není jazyková, nenastavuje parametr StringComparison na hodnotu Ordinal nebo OrdinalIgnoreCase. Explicitním nastavením parametru na hodnotu StringComparison.Ordinal nebo StringComparison.OrdinalIgnoreCase se kód často urychlí a bývá správnější a spolehlivější. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0} předává {1} jako parametr StringComparer do {2}. Pokud chcete provést jiné než jazykové porovnání, zadejte místo toho StringComparer.Ordinal StringComparer.OrdinalIgnoreCase. - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0} předává {1} jako parametr StringComparison do {2}. Pokud chcete provést jiné než jazykové porovnání, zadejte místo toho StringComparison.Ordinal StringComparison.OrdinalIgnoreCase. - - Use ordinal string comparison Použít porovnání ordinálních řetězců diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.de.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.de.xlf index e3cb170861..43bbf617cc 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.de.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.de.xlf @@ -7,11 +7,6 @@ Fügen Sie diesem Feld das Attribut "NonSerialized" hinzu. - - Add a public constructor that takes zero parameters - Öffentlichen Konstruktor ohne Parameter hinzufügen - - Add Serializable attribute Serializable-Attribut hinzufügen @@ -172,11 +167,6 @@ Dispose-Methoden müssen SuppressFinalize aufrufen - - Reliability - Zuverlässigkeit - - , , @@ -562,21 +552,6 @@ Wenn eine Instanz der Klasse "{0}" deserialisiert wird, kann die Methode "{1}" die gefährliche Methode "{2}" aufrufen. Mögliche Methodenaufrufe: {3} - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - Wenn ein Konstruktor eine virtuelle Methode aufruft, wurde der Konstruktor für die Instanz, die die Methode aufruft, möglicherweise nicht ausgeführt. - - - - Do not call overridable methods in constructors - Überschreibbare Methoden in Konstruktoren nicht aufrufen - - - - Do not call overridable methods in constructors - Überschreibbare Methoden in Konstruktoren nicht aufrufen - - Do not call {0} on an {1} value "{0}" nicht für einen {1}-Wert aufrufen @@ -587,21 +562,6 @@ "ToImmutableCollection" nicht für einen ImmutableCollection-Wert aufrufen - - Do not author general catch handlers in code that receives corrupted state exceptions. - Erstellen Sie keine allgemeinen catch-Handler in Code, der Corrupted State Exceptions erhält. - - - - Do not catch corrupted state exceptions in general handlers. - Fangen Sie in allgemeinen Handlern keine Corrupted State Exceptions ab. - - - - Do not catch corrupted state exceptions in general handlers. - Fangen Sie in allgemeinen Handlern keine Corrupted State Exceptions ab. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource verfügt über Konstruktoren, die TaskCreationOptions zum Steuern der zugrunde liegenden Aufgabe akzeptieren, und Konstruktoren, die den in der Aufgabe gespeicherten Objektzustand übernehmen. Das versehentliche Übergeben von TaskContinuationOptions anstelle von TaskCreationOptions führt dazu, dass der Aufruf die Optionen als Zustand behandelt. @@ -982,16 +942,6 @@ "{0}" ist ein unsicherer Zufallszahlen-Generator. Verwenden Sie kryptografisch sichere Zufallszahlen-Generatoren, wenn Zufallszahlen für die Sicherheit erforderlich sind. - - Do not use insecure cryptographic algorithm MD5. - Verwenden Sie nicht den unsicheren kryptografischen Algorithmus MD5. - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Dieser Typ implementiert MD5, eine kryptografisch unsichere Hashfunktion. Hashkollisionen sind für die Algorithmen MD5 und HMACMD5 rechnerisch möglich. Ersetzen Sie diese Verwendung durch einen Hashalgorithmus der SHA-2-Familie (SHA512, SHA384, SHA256). - - Do not use obsolete key derivation function Keine veraltete Schlüsselableitungsfunktion verwenden @@ -1042,16 +992,6 @@ ReferenceEquals nicht mit Werttypen verwenden - - Do not use insecure cryptographic algorithm SHA1. - Verwenden Sie nicht den unsicheren kryptografischen SHA1-Algorithmus. - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Dieser Typ implementiert SHA1, eine kryptografisch unsichere Hashfunktion. Hashkollisionen sind für die Algorithmen SHA-1 und SHA-0 rechnerisch möglich. Ersetzen Sie diese Verwendung durch einen Hashalgorithmus der SHA-2-Familie (SHA512, SHA384, SHA256). - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. Der über stackalloc zugewiesene Stapelspeicherplatz wird erst am Ende des Aufrufs der aktuellen Methode freigegeben. Die Verwendung in einer Schleife kann zu einer unbegrenzten Stapelvergrößerung und letztlich zu Stapelüberlaufbedingungen führen. @@ -1247,21 +1187,6 @@ {3} Der Typ von „{0}“ enthält den Vorschautyp „{1}“, daher müssen Vorschaufeatures abonniert werden. Weitere Informationen finden Sie unter {2}. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - Die Finalisierung muss über die Vererbungshierarchie verteilt werden. Um dies zu gewährleisten, müssen Typen in ihrer eigenen Finalize-Methode die Finalize-Methode ihrer Basisklasse aufrufen. - - - - Finalizers should call base class finalizer - Finalizer sollten Basisklassen-Finalizer aufrufen - - - - Finalizers should call base class finalizer - Finalizer sollten Basisklassen-Finalizer aufrufen - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. Hiermit wird der Parameter "CancellationToken" an Methoden weitergeleitet. So stellen Sie sicher, dass Benachrichtigungen zum Abbruch des Vorgangs ordnungsgemäß verteilt werden. Alternativ dazu können Sie explizit "CancellationToken.None" übergeben, um festzulegen, dass das Token nicht verteilt werden soll. @@ -1872,26 +1797,6 @@ {3} „{0}“ überschreibt die Vorschaumethode „{1}“, daher müssen Vorschaufeatures abonniert werden. Weitere Informationen finden Sie unter {2}. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - Diese Regel bewertet die Größe der einzelnen Parameter sowie den Rückgabewert eines P/Invoke und stellt sicher, dass die Größe des Parameters korrekt ist, wenn er an nicht verwalteten Code auf 32-Bit- und 64-Bit-Betriebssystemen gemarshallt wird. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - Gemäß der Deklaration in Ihrem Code ist der Parameter "{0}" von P/Invoke "{1}" auf {3}-Plattformen {2} Byte breit. Das ist nicht korrekt, da in der eigentlichen nativen Deklaration dieser API für {3}-Plattformen eine Sollbreite von {4} Byte angegeben ist. In der MSDN-Dokumentation zum Plattform-SDK finden Sie Informationen zum Ermitteln des Datentyps, den Sie anstatt "{5}" verwenden sollten. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Gemäß der Deklaration in Ihrem Code ist der Rückgabetyp von P/Invoke "{0}" auf {2}-Plattformen {1} Byte breit. Das ist nicht korrekt, da in der eigentlichen nativen Deklaration dieser API für {3}-Plattformen eine Sollbreite von {2} Byte angegeben ist. In der MSDN-Dokumentation zum Plattform-SDK finden Sie Informationen zum Ermitteln des Datentyps, den Sie anstatt "{4}" verwenden sollten. - - - - PInvoke declarations should be portable - PInvoke-Deklarationen müssen portierbar sein - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. Eine öffentliche oder geschützte Methode in einem öffentlichen Typ weist das Attribut "System.Runtime.InteropServices.DllImportAttribute" auf (auch durch das Declare-Schlüsselwort in Visual Basic implementiert). Solche Methoden dürfen nicht verfügbar gemacht werden. @@ -2287,21 +2192,6 @@ Zeichenfolgenliteral durch Zeichenliteral ersetzen - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - Eine Ausnahme wird erneut ausgelöst, und die Ausnahme wird in der throw-Anweisung explizit angegeben. Wenn eine Ausnahme durch Angabe in der throw-Anweisung erneut ausgelöst wird, geht die Liste von Methodenaufrufen zwischen der ursprünglichen Methode, die die Ausnahme ausgelöst hat, und der aktuellen Methode verloren. - - - - Rethrow to preserve stack details - Erneut ausführen, um Stapeldetails beizubehalten - - - - Rethrow to preserve stack details - Erneut ausführen, um Stapeldetails beizubehalten - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. Es wurde ein potenzielles Sicherheitsrisiko durch DLL-Einschleusung gefunden. "{0}" in der Methode "{1}" wurde möglicherweise durch benutzergesteuerte Daten aus "{2}" in Methode "{3}" verändert. @@ -2562,26 +2452,6 @@ Ein Member zum Plattformaufruf ermöglicht teilweise vertrauenswürdige Aufrufer, weist einen Zeichenfolgenparameter auf und führt kein explizites Marshalling der Zeichenfolge durch. Dies kann ein potenzielles Sicherheitsrisiko darstellen. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - Um das Sicherheitsrisiko zu verringern, marshallen Sie das Feld "{0}" als Unicode, indem Sie "StructLayout.CharSet" für "{1}" auf "CharSet.Unicode" festlegen oder das Feld explizit als "UnmanagedType.LPWStr" marshallen. Wenn Sie diese Zeichenfolge als ANSI oder systemunabhängig marshallen müssen, deaktivieren Sie die optimierte Zuordnung mithilfe des BestFitMapping-Attributs, und stellen Sie zur Erhöhung der Sicherheit sicher, dass ThrowOnUnmappableChar aktiviert ist. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Um das Sicherheitsrisiko zu verringern, marshallen Sie das Feld "{0}" als Unicode, indem Sie "StructLayout.CharSet" für "{1}" auf "CharSet.Unicode" festlegen oder das Feld explizit als "UnmanagedType.LPWStr" marshallen. Wenn Sie diese Zeichenfolge als ANSI oder systemunabhängig marshallen müssen, geben Sie MarshalAs explizit an, deaktivieren Sie die optimierte Zuordnung mithilfe des BestFitMapping-Attributs, und stellen Sie zur Erhöhung der Sicherheit sicher, dass ThrowOnUnmappableChar aktiviert ist. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Um das Sicherheitsrisiko zu verringern, marshallen Sie den Parameter "{0}" als Unicode, indem Sie "DllImport.CharSet" auf "CharSet.Unicode" festlegen oder den Parameter explizit als "UnmanagedType.LPWStr" marshallen. Wenn Sie diese Zeichenfolge als ANSI oder systemunabhängig marshallen müssen, legen Sie "BestFitMapping=false" fest. Für zusätzliche Sicherheit legen Sie außerdem "ThrowOnUnmappableChar=true" fest. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Um das Sicherheitsrisiko zu verringern, marshallen Sie den Parameter "{0}" als Unicode, indem Sie "DllImport.CharSet" auf "CharSet.Unicode" festlegen oder den Parameter explizit als "UnmanagedType.LPWStr" marshallen. Wenn Sie diese Zeichenfolge als ANSI oder systemunabhängig marshallen müssen, geben Sie MarshalAs explizit an, und legen Sie "BestFitMapping=false" fest. Für zusätzliche Sicherheit legen Sie außerdem "ThrowOnUnmappableChar=true" fest. - - Specify marshaling for P/Invoke string arguments Marshalling für P/Invoke-Zeichenfolgenargumente angeben @@ -2922,16 +2792,6 @@ Bei einem nicht linguistischen Vorgang zum Zeichenfolgenvergleich wird der StringComparison-Parameter nicht auf "Ordinal" oder "OrdinalIgnoreCase" festgelegt. Indem der Parameter explizit auf "StringComparison.Ordinal" oder "StringComparison.OrdinalIgnoreCase" festgelegt wird, gewinnt Ihr Code häufig an Geschwindigkeit und ist zudem korrekter und zuverlässiger. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - "{0}" übergibt "{1}" als StringComparer-Parameter an "{2}". Um einen nicht linguistischen Vergleich durchzuführen, geben Sie stattdessen "StringComparer.Ordinal" oder "StringComparer.OrdinalIgnoreCase" an. - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - "{0}" übergibt "{1}" als StringComparison-Parameter an "{2}". Um einen nicht linguistischen Vergleich durchzuführen, geben Sie stattdessen "StringComparison.Ordinal" oder "StringComparison.OrdinalIgnoreCase" an. - - Use ordinal string comparison Ordinalzeichenfolgenvergleich verwenden diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.es.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.es.xlf index 42e2bf8748..0d7c18ebc3 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.es.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.es.xlf @@ -7,11 +7,6 @@ Agregue el atributo "NonSerialized" a este campo. - - Add a public constructor that takes zero parameters - Agregar un constructor público que toma cero parámetros - - Add Serializable attribute Agregar el atributo Serializable @@ -172,11 +167,6 @@ Los métodos Dispose deberían llamar a SuppressFinalize - - Reliability - Fiabilidad - - , , @@ -562,21 +552,6 @@ Al deserializar una instancia de la clase {0}, el método {1} puede llamar al método peligroso {2}. Invocaciones de métodos posibles: {3}. - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - Cuando un constructor llama a un método virtual, es posible que no se haya ejecutado el constructor para la instancia que invoca el método. - - - - Do not call overridable methods in constructors - No llamar a métodos reemplazables en constructores - - - - Do not call overridable methods in constructors - No llamar a métodos reemplazables en constructores - - Do not call {0} on an {1} value No llame a {0} en un valor {1} @@ -587,21 +562,6 @@ No llame a ToImmutableCollection en un valor ImmutableCollection - - Do not author general catch handlers in code that receives corrupted state exceptions. - No cree controladores catch en código que reciba excepciones de estado dañado. - - - - Do not catch corrupted state exceptions in general handlers. - No aplique catch a excepciones de estado dañado en controladores generales. - - - - Do not catch corrupted state exceptions in general handlers. - No aplique catch a excepciones de estado dañado en controladores generales. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource tiene constructores que toman elementos TaskCreationOption para controlar la tarea subyacente y constructores que toman el estado del objeto que se almacena en la tarea. Si se pasa accidentalmente un elemento TaskContinuationOption en lugar de un objeto TaskCreationOption, la llamada trata las opciones como estado. @@ -982,16 +942,6 @@ {0} es un generador de números aleatorios no seguro. Use generadores de números aleatorios que sean criptográficamente seguros cuando se requiera aleatoriedad por seguridad. - - Do not use insecure cryptographic algorithm MD5. - No use el algoritmo criptográfico no seguro MD5. - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Este tipo implementa MD5, una función hash no segura criptográficamente. Las colisiones de hash son computacionalmente factibles para los algoritmos MD5 y HMACMD5. Reemplace este uso por un algoritmo de hash de la familia SHA-2 (SHA512, SHA384, SHA256). - - Do not use obsolete key derivation function No utilizar la función de derivación de claves obsoleta @@ -1042,16 +992,6 @@ No use ReferenceEquals con tipos de valor - - Do not use insecure cryptographic algorithm SHA1. - No use el algoritmo criptográfico no seguro SHA1. - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Este tipo implementa SHA1, una función hash no segura criptográficamente. Las colisiones de hash son computacionalmente factibles para los algoritmos SHA-1 y SHA-0. Reemplace este uso por un algoritmo de hash de la familia SHA-2 (SHA512, SHA384, SHA256). - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. El espacio de pila asignado por una instancia de stackalloc solo se libera al final de la invocación del método actual. Si se usa en un bucle, puede producirse un crecimiento ilimitado de la pila y alcanzar condiciones de desbordamiento de esta. @@ -1247,21 +1187,6 @@ {3} '{0}''' contiene el tipo de vista previa '{1}' y requiere la participación en las características en versión preliminar. Consulte {2} para obtener más información. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - La finalización se debe difundir a través de la jerarquía de herencia. Para garantizar esto, los tipos deben llamar al método Finalize de su clase base desde su propio método Finalize. - - - - Finalizers should call base class finalizer - Los finalizadores deben llamar al finalizador de la clase base - - - - Finalizers should call base class finalizer - Los finalizadores deben llamar al finalizador de la clase base - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. Reenvíe el parámetro "CancellationToken" a los métodos para garantizar que las notificaciones de cancelación de operaciones se propagan correctamente, o bien pase "CancellationToken.None" explícitamente para indicar que no se propagará el token intencionalmente. @@ -1872,26 +1797,6 @@ {3} '{0}' invalida el método de vista previa '{1}' y, por lo tanto, debe participar en las características en versión preliminar. Consulte {2} para obtener más información. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - Esta regla evalúa el tamaño de cada parámetro y el valor devuelto de un PInvoke y comprueba que su tamaño sea correcto al calcular las referencias para su conversión al código no administrado en plataformas de 32 y 64 bits. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - Como se declara en el código, el parámetro '{0}' de P/Invoke {1} será de {2} bytes en {3} plataformas. Esto no es correcto, puesto que la declaración nativa actual de API indica que debería ser de {4} bytes en {3} plataformas. Consulte la documentación de Platform SDK de MSDN para obtener ayuda para determinar qué tipo de datos debería utilizarse en lugar de {5}. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Como se declara en el código, el valor devuelto de P/Invoke {0} será de {1} bytes en {2} plataformas. Esto no es correcto puesto que la declaración nativa actual de esta API indica que debería ser de {3} bytes en {2} plataformas. Consulte la documentación de Platform SDK de MSDN para obtener ayuda para determinar qué tipo de datos debería utilizarse en lugar de {4}. - - - - PInvoke declarations should be portable - Las declaraciones de PInvoke deben ser portables - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. Un método público o protegido en un tipo público tiene el atributo System.Runtime.InteropServices.DllImportAttribute (también se implementa por la palabra clave Declare en Visual Basic). Estos métodos no deben exponerse. @@ -2287,21 +2192,6 @@ Reemplazar literal de cadena por literal char - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - Se vuelve a producir una excepción y se especifica explícitamente en la instrucción throw. Si se vuelve a producir una excepción especificándola en la instrucción throw, se pierde la lista de llamadas al método entre el método original que produjo la excepción y el método actual. - - - - Rethrow to preserve stack details - Iniciar de nuevo para preservar los detalles de la pila - - - - Rethrow to preserve stack details - Iniciar de nuevo para preservar los detalles de la pila - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. Se encontró una vulnerabilidad potencial de inyección de DLL en la que "{0}" en el método "{1}" puede contaminarse por datos controlados por el usuario de "{2}" en el método "{3}". @@ -2562,26 +2452,6 @@ Un miembro de invocación de plataforma permite llamadores que no son de plena confianza, tiene un parámetro de cadena y no calcula explícitamente las referencias a la cadena. Esto puede provocar una potencial vulnerabilidad de seguridad. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - Para reducir el riesgo de seguridad, calcule las referencias del campo {0} como Unicode, estableciendo StructLayout.CharSet de {1} en CharSet.Unicode o calculando explícitamente las referencias al campo como UnmanagedType.LPWStr. Si necesita calcular las referencias a esta cadena como ANSI o dependiente del sistema, utilice el atributo BestFitMapping para desactivar la mejor asignación y, para más seguridad, asegúrese de que ThrowOnUnmappableChar está activado. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Para reducir el riesgo de seguridad, calcule las referencias del campo {0} como Unicode, estableciendo StructLayout.CharSet de {1} en CharSet.Unicode o calculando explícitamente las referencias al campo como UnmanagedType.LPWStr. Si necesita calcular las referencias a esta cadena como ANSI o dependiente del sistema, especifique MarshalAs explícitamente, utilice el atributo BestFitMapping para desactivar la mejor asignación y, para más seguridad, active ThrowOnUnmappableChar. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Para reducir el riesgo de seguridad, calcule las referencias del parámetro {0} como Unicode, estableciendo DllImport.CharSet en CharSet.Unicode o calculando explícitamente las referencias al parámetro como UnmanagedType.LPWStr. Si necesita calcular las referencias a esta cadena como ANSI o dependiente del sistema, establezca BestFitMapping=false. Para más seguridad, establezca también ThrowOnUnmappableChar=true. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Para reducir el riesgo de seguridad, calcule las referencias del parámetro {0} como Unicode, estableciendo DllImport.CharSet en CharSet.Unicode o calculando explícitamente las referencias al parámetro como UnmanagedType.LPWStr. Si necesita calcular las referencias a esta cadena como ANSI o dependiente del sistema, especifique MarshalAs explícitamente y establezca BestFitMapping=false. Para más seguridad, establezca también ThrowOnUnmappableChar=true. - - Specify marshaling for P/Invoke string arguments Especificar cálculo de referencias para argumentos de cadena P/Invoke @@ -2922,16 +2792,6 @@ Una operación no lingüística de comparación de cadenas no establece el parámetro StringComparison en Ordinal ni en OrdinalIgnoreCase. Si se establece explícitamente el parámetro en StringComparison.Ordinal o StringComparison.OrdinalIgnoreCase, el código será más rápido y ganará en precisión y confiabilidad. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0} pasa "{1}" como parámetro de "StringComparer" a {2}. Para llevar a cabo una comparación no lingüística, especifique en su lugar "StringComparer.Ordinal" o "StringComparer.OrdinalIgnoreCase". - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0} pasa "{1}" como parámetro de "StringComparison" a {2}. Para llevar a cabo una comparación no lingüística, especifique en su lugar "StringComparison.Ordinal" o "StringComparison.OrdinalIgnoreCase". - - Use ordinal string comparison Usar una comparación de cadena ordinal diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.fr.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.fr.xlf index f5cba463e9..20b631aa5c 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.fr.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.fr.xlf @@ -7,11 +7,6 @@ Ajoutez l'attribut 'NonSerialized' à ce champ. - - Add a public constructor that takes zero parameters - Ajouter un constructeur public qui accepte des paramètres nuls - - Add Serializable attribute Ajouter l'attribut Serializable @@ -172,11 +167,6 @@ Les méthodes Dispose doivent appeler SuppressFinalize - - Reliability - Fiabilité - - , , @@ -562,21 +552,6 @@ Quand vous désérialisez une instance de la classe {0}, la méthode {1} peut appeler une méthode dangereuse {2}. Les appels de méthode potentiels sont : {3}. - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - Quand un constructeur appelle une méthode virtuelle, le constructeur de l'instance qui appelle la méthode n'a peut-être pas été exécuté. - - - - Do not call overridable methods in constructors - N'appelez pas de méthodes substituables dans les constructeurs - - - - Do not call overridable methods in constructors - N'appelez pas de méthodes substituables dans les constructeurs - - Do not call {0} on an {1} value Ne pas appeler {0} sur une valeur {1} @@ -587,21 +562,6 @@ Ne pas appeler ToImmutableCollection sur une valeur ImmutableCollection - - Do not author general catch handlers in code that receives corrupted state exceptions. - Ne créez pas de gestionnaires d'interception généraux dans le code qui reçoit les exceptions état altéré. - - - - Do not catch corrupted state exceptions in general handlers. - N'interceptez pas les exceptions état altéré dans les gestionnaires généraux. - - - - Do not catch corrupted state exceptions in general handlers. - N'interceptez pas les exceptions état altéré dans les gestionnaires généraux. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource a des constructeurs qui prennent des TaskCreationOptions qui contrôlent la tâche sous-jacente, et des constructeurs qui prennent l'état d'objet stocké dans la tâche. La transmission accidentelle de TaskContinuationOptions au lieu de TaskCreationOptions entraîne dans l'appel le traitement des options comme des états. @@ -982,16 +942,6 @@ {0} est un générateur de nombres aléatoires non sécurisé. Utilisez des générateurs de nombres aléatoires sécurisés de manière chiffrée quand une sélection aléatoire est nécessaire pour la sécurité. - - Do not use insecure cryptographic algorithm MD5. - N'utilisez pas d'algorithme de chiffrement MD5 non sécurisé. - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Ce type implémente MD5, une fonction de hachage par chiffrement non sécurisée. Les collisions de hachage peuvent être calculées pour les algorithmes MD5 et HMACMD5. Remplacez cette utilisation par un algorithme de hachage de la famille SHA-2 (SHA512, SHA384, SHA256). - - Do not use obsolete key derivation function Ne pas utiliser de fonction de dérivation de clés obsolète @@ -1042,16 +992,6 @@ Ne pas utiliser ReferenceEquals avec des types valeur - - Do not use insecure cryptographic algorithm SHA1. - N'utilisez pas d'algorithme de chiffrement SHA1 non sécurisé. - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Ce type implémente SHA1, une fonction de hachage par chiffrement non sécurisée. Les collisions de hachage peuvent être calculées pour les algorithmes SHA-1 et SHA-0. Remplacez cette utilisation par un algorithme de hachage de la famille SHA-2 (SHA512, SHA384, SHA256). - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. L'espace de pile alloué par stackalloc est uniquement libéré à la fin de l'appel de la méthode actuelle. Si vous l'utilisez dans une boucle, cela risque d'entraîner une croissance de pile indépendante et des conditions de dépassement de la capacité de la pile. @@ -1247,21 +1187,6 @@ Le type de « {3}{0} » contient le type d’aperçu « {1} » et requiert l’option préverser les fonctionnalités en préversion. Pour plus d’informations, consultez {2}. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - La finalisation doit être propagée via la hiérarchie d'héritage. Pour garantir cette opération, les types doivent appeler leur méthode Finalize de classe de base dans leur propre méthode Finalize. - - - - Finalizers should call base class finalizer - Les finaliseurs doivent appeler un finaliseur de classe de base - - - - Finalizers should call base class finalizer - Les finaliseurs doivent appeler un finaliseur de classe de base - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. Transférez le paramètre 'CancellationToken' aux méthodes appropriées pour avoir la garantie que les notifications d'annulation d'opération sont correctement propagées, ou passez explicitement 'CancellationToken.None' pour indiquer clairement de ne pas propager le jeton. @@ -1872,26 +1797,6 @@ '{3}'{0} contourne la méthode de prévisualisation '{1}' et doit donc opter pour les fonctionnalités de prévisualisation. Voir {2}pour plus d'informations. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - Cette règle évalue la taille de chaque paramètre et la valeur de retour d'un P/Invoke. De plus, elle vérifie que la taille du paramètre est correcte quand il est marshalé en code non managé sur les systèmes d'exploitation 32 bits et 64 bits. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - Comme il est déclaré dans votre code, le paramètre {0} de P/Invoke {1} est de {2} octets sur les plateformes {3}. Cela n'est pas correct, car la déclaration native réelle de cette API indique qu'elle doit être de {4} octets sur les plateformes {3}. Consultez la documentation du kit Platform SDK sur MSDN pour déterminer le type de données à utiliser à la place de {5}. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Comme il est déclaré dans votre code, le type de retour de P/Invoke {0} est de {1} octets sur les plateformes {2}. Cela n'est pas correct, car la déclaration native réelle de cette API indique qu'elle doit être de {3} octets sur les plateformes {2}. Consultez la documentation du kit Platform SDK sur MSDN pour déterminer le type de données à utiliser à la place de {4}. - - - - PInvoke declarations should be portable - Les déclarations de PInvoke doivent être portables - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. Une méthode publique ou protégée dans un type public a l'attribut System.Runtime.InteropServices.DllImportAttribute (également implémenté par le mot clé Declare en Visual Basic). De telles méthodes ne doivent pas être exposées. @@ -2287,21 +2192,6 @@ Remplacer le littéral de chaîne par un littéral de caractère - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - Une exception est à nouveau levée et est spécifiée explicitement dans l'instruction throw. Si une exception est à nouveau levée quand elle est spécifiée dans l'instruction throw, la liste des appels de méthode présents entre la méthode d'origine ayant levé l'exception et la méthode actuelle est perdue. - - - - Rethrow to preserve stack details - Lever à nouveau une exception pour conserver les détails de la pile - - - - Rethrow to preserve stack details - Lever à nouveau une exception pour conserver les détails de la pile - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. Une vulnérabilité potentielle liée à une injection de DLL a été détectée. '{0}' dans la méthode '{1}' peut être altéré par des données contrôlées par l'utilisateur en provenance de '{2}' dans la méthode '{3}'. @@ -2562,26 +2452,6 @@ Un membre d'appel de code non managé autorise les appelants partiellement fiables, comporte un paramètre de chaîne et n'effectue pas de marshaling explicite de la chaîne. Cela peut entraîner une vulnérabilité de sécurité. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - Pour réduire le risque de sécurité, marshalez le champ {0} au format Unicode, en affectant CharSet.Unicode à StructLayout.CharSet sur {1} ou en marshalant explicitement le champ en tant que UnmanagedType.LPWStr. Si vous devez marshaler cette chaîne au format ANSI ou dans un format dépendant du système, utilisez l'attribut BestFitMapping pour désactiver le mappage ajusté. Pour plus de sécurité, vérifiez que ThrowOnUnmappableChar est activé. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Pour réduire le risque de sécurité, marshalez le champ {0} au format Unicode, en affectant CharSet.Unicode à StructLayout.CharSet sur {1} ou en marshalant explicitement le champ en tant que UnmanagedType.LPWStr. Si vous devez marshaler cette chaîne au format ANSI ou dans un format dépendant du système, spécifiez MarshalAs explicitement, puis utilisez l'attribut BestFitMapping pour désactiver le mappage ajusté. Pour plus de sécurité, activez ThrowOnUnmappableChar. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Pour réduire le risque de sécurité, marshalez le paramètre {0} au format Unicode, en affectant CharSet.Unicode à DllImport.CharSet ou en marshalant explicitement le paramètre en tant que UnmanagedType.LPWStr. Si vous devez marshaler cette chaîne au format ANSI ou dans un format dépendant du système, définissez BestFitMapping=false. Pour plus de sécurité, définissez également ThrowOnUnmappableChar=true. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Pour réduire le risque de sécurité, marshalez le paramètre {0} au format Unicode, en affectant CharSet.Unicode à DllImport.CharSet ou en marshalant explicitement le paramètre en tant que UnmanagedType.LPWStr. Si vous devez marshaler cette chaîne au format ANSI ou dans un format dépendant du système, spécifiez MarshalAs explicitement, puis définissez BestFitMapping=false. Pour plus de sécurité, définissez également ThrowOnUnmappableChar=true. - - Specify marshaling for P/Invoke string arguments Spécifier le marshaling pour les arguments de chaîne P/Invoke @@ -2922,16 +2792,6 @@ Une opération de comparaison de chaînes non linguistique n'affecte pas au paramètre StringComparison la valeur Ordinal ou OrdinalIgnoreCase. En affectant explicitement au paramètre la valeur StringComparison.Ordinal ou StringComparison.OrdinalIgnoreCase, votre code gagne souvent en rapidité, tout en devenant plus correct et plus fiable. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0} passe '{1}' en tant que paramètre 'StringComparer' à {2}. Pour effectuer une comparaison non linguistique, spécifiez 'StringComparer.Ordinal' ou 'StringComparer.OrdinalIgnoreCase' à la place. - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0} passe '{1}' en tant que paramètre 'StringComparison' à {2}. Pour effectuer une comparaison non linguistique, spécifiez 'StringComparison.Ordinal' ou 'StringComparison.OrdinalIgnoreCase' à la place. - - Use ordinal string comparison Utiliser la comparaison de chaînes ordinales diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.it.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.it.xlf index 231b5a844e..0b3f1bca22 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.it.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.it.xlf @@ -7,11 +7,6 @@ Aggiungere l'attributo 'NonSerialized' a questo campo. - - Add a public constructor that takes zero parameters - Aggiungere un costruttore pubblico che accetta zero parametri - - Add Serializable attribute Aggiungere l'attributo Serializable @@ -172,11 +167,6 @@ I metodi Dispose devono chiamare SuppressFinalize - - Reliability - Affidabilità - - , , @@ -562,21 +552,6 @@ Durante la deserializzazione di un'istanza della classe {0} il metodo {1} può chiamare il metodo pericoloso {2}. Le potenziali chiamate al metodo sono: {3}. - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - Quando un costruttore chiama un metodo virtuale, è possibile che il costruttore per l'istanza che richiama il metodo non sia stato eseguito. - - - - Do not call overridable methods in constructors - Non chiamare metodi sottoponibili a override nei costruttori - - - - Do not call overridable methods in constructors - Non chiamare metodi sottoponibili a override nei costruttori - - Do not call {0} on an {1} value Non chiamare {0} su un valore {1} @@ -587,21 +562,6 @@ Non chiamare ToImmutableCollection su un valore ImmutableCollection - - Do not author general catch handlers in code that receives corrupted state exceptions. - Non creare gestori catch generali in codice che riceve le eccezioni di stato danneggiato. - - - - Do not catch corrupted state exceptions in general handlers. - Non rilevare eccezioni di stato danneggiato in gestori generali. - - - - Do not catch corrupted state exceptions in general handlers. - Non rilevare eccezioni di stato danneggiato in gestori generali. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource include costruttori che accettano enumerazioni TaskCreationOptions che controllano l'attività sottostante e costruttori che accettano lo stato dell'oggetto archiviato nell'attività. Se si passa accidentalmente un'enumerazione TaskContinuationOptions invece di TaskCreationOptions, la chiamata considererà le opzioni come stato. @@ -982,16 +942,6 @@ {0} è un generatore di numeri casuali non sicuro. Usare generatori di numeri casuali sicuri dal punto di vista della crittografia quando per motivi di sicurezza è richiesta la casualità. - - Do not use insecure cryptographic algorithm MD5. - Non usare l'algoritmo di crittografia non sicuro MD5. - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Questo tipo implementa MD5, una funzione hash crittograficamente non sicura. Da un punto di vista computazionale, le collisioni di hash sono possibili per gli algoritmi MD5 e HMACMD5. Sostituire questo algoritmo con uno hash della famiglia SHA-2 (SHA512, SHA384, SHA256). - - Do not use obsolete key derivation function Non usare la funzione di derivazione di chiave obsoleta @@ -1042,16 +992,6 @@ Non usare ReferenceEquals con tipi valore - - Do not use insecure cryptographic algorithm SHA1. - Non usare l'algoritmo di crittografia non sicuro SHA1. - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Questo tipo implementa SHA1, una funzione hash crittograficamente non sicura. Da un punto di vista computazionale, le collisioni di hash sono possibili per gli algoritmi SHA-1 e SHA-0. Sostituire questo algoritmo con uno hash della famiglia SHA-2 (SHA512, SHA384, SHA256). - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. Lo spazio dello stack allocato da stackalloc viene rilasciato solo alla fine della chiamata del metodo corrente. Se viene usato in un ciclo, possono verificarsi condizioni di crescita illimitata dello stack e eventuale overflow dello stack. @@ -1247,21 +1187,6 @@ Il tipo di '{3} '{0}' contiene il tipo di anteprima '{1}' e richiede il consenso esplicito per le funzionalità di anteprima. Per altre informazioni, vedere {2}. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - La finalizzazione deve essere propagata tramite la gerarchia di ereditarietà. A tale scopo, i tipi devono chiamare il metodo Finalize della classe di base nel proprio metodo Finalize. - - - - Finalizers should call base class finalizer - I finalizzatori devono chiamare il finalizzatore della classe di base - - - - Finalizers should call base class finalizer - I finalizzatori devono chiamare il finalizzatore della classe di base - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. Inoltrare il parametro 'CancellationToken' ai metodi per assicurare la corretta propagazione delle notifiche di annullamento dell'operazione oppure passare 'CancellationToken.None' in modo esplicito per indicare che il token non viene propagato intenzionalmente. @@ -1872,26 +1797,6 @@ '{3} '{0}' sorvrascrive il metodo di anteprima '{1}' e deve quindi acconsentire esplicitamente alle funzionalità di anteprima. Per altre informazioni, vedere {2}. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - Questa regola valuta le dimensioni di ogni parametro e il valore restituito di un metodo P/Invoke e verifica che le dimensioni del parametro siano corrette quando viene eseguito il marshalling a codice non gestito in sistemi operativi a 32 e a 64 bit. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - Come dichiarato nel codice, il valore del parametro {0} di P/Invoke {1} sarà pari a {2} byte sulle piattaforme {3}. Questo non è corretto perché l'effettiva dichiarazione nativa di questa API indica che deve essere pari a {4} byte sulle piattaforme {3}. Consultare la documentazione di MSDN Platform SDK per informazioni su come determinare il tipo di dati da usare al posto di {5}. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Come dichiarato nel codice, il valore del tipo restituito di P/Invoke {0} sarà pari a {1} byte sulle piattaforme {2}. Questo non è corretto perché l'effettiva dichiarazione nativa di questa API indica che deve essere pari a {3} byte sulle piattaforme {2}. Consultare la documentazione di MSDN Platform SDK per informazioni su come determinare il tipo di dati da usare al posto di {4}. - - - - PInvoke declarations should be portable - Le dichiarazioni PInvoke devono essere portabili - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. Un metodo public o protected in un tipo public contiene l'attributo System.Runtime.InteropServices.DllImportAttribute (implementato anche dalla parola chiave Declare in Visual Basic). Questi metodi non devono essere esposti. @@ -2287,21 +2192,6 @@ Sostituire il valore letterale stringa con il valore letterale char - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - Viene generata di nuovo un'eccezione, specificata in modo esplicito nell'istruzione throw. Se viene generata di nuovo un'eccezione specificandola nell'istruzione throw, l'elenco di chiamate del metodo tra il metodo originale che ha generato l'eccezione e il metodo corrente viene perso. - - - - Rethrow to preserve stack details - Eseguire il rethrow per conservare i dettagli dello stack - - - - Rethrow to preserve stack details - Eseguire il rethrow per conservare i dettagli dello stack - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. È stata trovata una potenziale vulnerabilità di tipo DLL injection in cui '{0}' nel metodo '{1}' può essere contaminato da dati controllati dall'utente di '{2}' nel metodo '{3}'. @@ -2562,26 +2452,6 @@ Un membro di platform invoke consente chiamanti parzialmente attendibili, include un parametro di tipo stringa e non esegue il marshalling della stringa. Questo può comportare una potenziale vulnerabilità di sicurezza. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - Per ridurre i problemi di sicurezza, eseguire il marshalling del campo {0} come Unicode impostando StructLayout.CharSet in {1} su CharSet.Unicode o eseguendo in modo esplicito il marshalling del campo come UnmanagedType.LPWStr. Se è necessario eseguire il marshalling della stringa come ANSI o dipendente da sistema, usare l'attributo BestFitMapping per disattivare il mapping più appropriato. Per maggiore sicurezza, assicurarsi che ThrowOnUnmappableChar sia attivato. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Per ridurre i problemi di sicurezza, eseguire il marshalling del campo {0} come Unicode impostando StructLayout.CharSet in {1} su CharSet.Unicode o eseguendo in modo esplicito il marshalling del campo come UnmanagedType.LPWStr. Per eseguire il marshalling della stringa come ANSI o dipendente da sistema, specificare in modo esplicito MarshalAs, usare l'attributo BestFitMapping per disattivare il mapping più appropriato. Per maggiore sicurezza, assicurarsi che ThrowOnUnmappableChar sia attivato. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Per ridurre i problemi di sicurezza, eseguire il marshalling del parametro {0} come Unicode impostando DllImport.CharSet su CharSet.Unicode o eseguendo in modo esplicito il marshalling del parametro come UnmanagedType.LPWStr. Se è necessario eseguire il marshalling della stringa come ANSI o dipendente da sistema, impostare BestFitMapping=false. Per maggiore sicurezza, impostare anche ThrowOnUnmappableChar=true. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Per ridurre i problemi di sicurezza, eseguire il marshalling del parametro {0} come Unicode impostando DllImport.CharSet su CharSet.Unicode o eseguendo in modo esplicito il marshalling del parametro come UnmanagedType.LPWStr. Se è necessario eseguire il marshalling della stringa come ANSI o dipendente da sistema, specificare in modo esplicito MarshalAs e impostare BestFitMapping=false. Per maggiore sicurezza, impostare anche ThrowOnUnmappableChar=true. - - Specify marshaling for P/Invoke string arguments Specificare il marshalling per gli argomenti stringa P/Invoke @@ -2922,16 +2792,6 @@ In un'operazione di confronto tra stringhe di tipo non linguistico il parametro StringComparison non viene impostato su Ordinal o OrdinalIgnoreCase. L'impostazione esplicita del parametro su StringComparison.Ordinal o StringComparison.OrdinalIgnoreCase consente spesso di rendere il codice più veloce, corretto e affidabile. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0} passa '{1}' come parametro 'StringComparer' a {2}. Per eseguire un confronto di tipo non linguistico, specificare 'StringComparer.Ordinal' o 'StringComparer.OrdinalIgnoreCase'. - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0} passa '{1}' come parametro 'StringComparison' a {2}. Per eseguire un confronto di tipo non linguistico, specificare 'StringComparison.Ordinal' o 'StringComparison.OrdinalIgnoreCase'. - - Use ordinal string comparison Usa il confronto di stringhe tra ordinali diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ja.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ja.xlf index 615574f654..9d36651a0c 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ja.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ja.xlf @@ -7,11 +7,6 @@ このフィールドに、'NonSerialized' 属性を追加します。 - - Add a public constructor that takes zero parameters - 0 個のパラメーターを受け取るパブリック コンストラクターを追加する - - Add Serializable attribute Serializable 属性を追加する @@ -172,11 +167,6 @@ Dispose メソッドは、SuppressFinalize を呼び出す必要があります - - Reliability - 信頼性 - - , , @@ -562,21 +552,6 @@ クラス {0} のインスタンスを逆シリアル化すると、メソッド {1} によって危険なメソッド {2} を呼び出されるおそれがあります。考えられるメソッド呼び出し: {3}。 - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - コンストラクターが仮想メソッドを呼び出すときに、メソッドを呼び出すインスタンスのコンストラクターは実行されていない可能性があります。 - - - - Do not call overridable methods in constructors - コンストラクターのオーバーライド可能なメソッドを呼び出しません - - - - Do not call overridable methods in constructors - コンストラクターのオーバーライド可能なメソッドを呼び出しません - - Do not call {0} on an {1} value {1} 値で {0} を呼び出さないでください @@ -587,21 +562,6 @@ ImmutableCollection 値で ToImmutableCollection を呼び出さないでください - - Do not author general catch handlers in code that receives corrupted state exceptions. - 破損状態例外を受け取るコード内に汎用キャッチ ハンドラーを作成しないでください。 - - - - Do not catch corrupted state exceptions in general handlers. - 汎用ハンドラーの破損状態例外をキャッチしません。 - - - - Do not catch corrupted state exceptions in general handlers. - 汎用ハンドラーの破損状態例外をキャッチしません。 - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource には、基になるタスクを制御する TaskCreationOptions を使用するコンストラクターと、そのタスクに格納されているオブジェクトの状態を使用するコンストラクターがあります。TaskCreationOptions の代わりに TaskContinuationOptions を誤って渡すと、呼び出しでオプションが状態として処理されます。 @@ -982,16 +942,6 @@ {0} は安全でない乱数ジェネレーターです。セキュリティにランダム度が必要な場合に、暗号化によってセキュリティで保護された乱数ジェネレーターを使用します。 - - Do not use insecure cryptographic algorithm MD5. - 安全でない暗号アルゴリズム MD5 を使用しない。 - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - この型は、暗号として安全でないハッシュ関数である MD5 を実装しています。MD5 と HMACMD5 アルゴリズムでは、計算上、ハッシュの競合が起こる可能性があります。この使用を SHA-2 ファミリのハッシュ アルゴリズム (SHA512、SHA384、SHA256) に置き換えてください。 - - Do not use obsolete key derivation function 非推奨のキー派生関数を使用しないでください @@ -1042,16 +992,6 @@ 値の型で ReferenceEquals を使用しない - - Do not use insecure cryptographic algorithm SHA1. - 安全でない暗号アルゴリズム SHA1 を使用しない。 - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - この型は、暗号として安全でないハッシュ関数である SHA1 を実装しています。SHA-1 と SHA-0 アルゴリズムでは、計算上、ハッシュの競合が起こる可能性があります。この使用を SHA-2 ファミリのハッシュ アルゴリズム (SHA512、SHA384、SHA256) に置き換えてください。 - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. stackalloc によって割り当てられたスタック領域は、現在のメソッドの呼び出しの終了時にのみ解放されます。これをループ内で使用すると、スタックが無限に増加し、最終的にスタック オーバーフロー状態が発生する可能性があります。 @@ -1247,21 +1187,6 @@ {3} '{0}' の型には、プレビューの種類 '{1}' が含まれており、プレビュー機能を選択する必要があります。詳細については、「{2}」を参照してください。 - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - 終了処理は、継承階層を通じて伝達される必要があります。これを保証するには、型が独自の Finalize メソッド内で基底クラスの Finalize メソッドを呼び出す必要があります。 - - - - Finalizers should call base class finalizer - ファイナライザーは基底クラスのファイナライザーを呼び出さなければなりません - - - - Finalizers should call base class finalizer - ファイナライザーは基底クラスのファイナライザーを呼び出さなければなりません - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. 'CancellationToken' パラメーターをメソッドに転送して操作のキャンセル通知が適切に伝達されるようにするか、または 'CancellationToken.None' を明示的に渡して意図的にトークンを伝達しないことを指定します。 @@ -1872,26 +1797,6 @@ {3} '{0}' はプレビュー メソッド '{1}' を上書きするため、プレビュー機能を選択する必要があります。詳細については、「{2}」を参照してください。 - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - この規則では、各パラメーターのサイズと P/Invoke の戻り値を評価し、32 ビットおよび 64 ビットのオペレーティング システム上のアンマネージ コードにマーシャリングされた場合にパラメーターのサイズが正しいことを確認します。 - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - コードで宣言されているとおり、P/Invoke {1} のパラメーター {0} は {3} プラットフォームで {2} バイトになります。この API の実際のネイティブ宣言は {3} プラットフォームで {4} バイトでなければならないことを示しているため、この状態は正しくありません。{5} の代わりにどのデータ型を使用する必要があるかを判断するには、MSDN のプラットフォーム SDK ドキュメントを参照してください。 - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - コードで宣言されているとおり、P/Invoke {0} の戻り値の型は {2} プラットフォームで {1} バイトになります。この API の実際のネイティブ宣言は {2} プラットフォームで {3} バイトでなければならないことを示しているため、この状態は正しくありません。{4} の代わりにどのデータ型を使用する必要があるかを判断するには、MSDN のプラットフォーム SDK ドキュメントを参照してください。 - - - - PInvoke declarations should be portable - PInvoke 宣言は移植可能なでなければなりません - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. パブリック型にあるパブリック メソッドまたは保護されたメソッドには、System.Runtime.InteropServices.DllImportAttribute 属性 (Visual Basic では、Declare キーワードによっても実装されています) があります。このようなメソッドは公開しないでください。 @@ -2287,21 +2192,6 @@ 文字列リテラルを char リテラルに置き換える - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - 例外が再スローされ、その例外が throw ステートメント内に明示的に指定されます。throw ステートメント内で例外を指定することによって例外が再スローされる場合、例外をスローした元のメソッドと現在のメソッドの間のメソッド呼び出しのリストは失われます。 - - - - Rethrow to preserve stack details - スタック詳細を保持するために再度スローします - - - - Rethrow to preserve stack details - スタック詳細を保持するために再度スローします - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. 潜在的な DLL インジェクションの脆弱性が見つかりました。メソッド '{1}' の '{0}' は、メソッド '{3}' の '{2}' からのユーザーが制御するデータによって悪用される可能性があります。 @@ -2562,26 +2452,6 @@ プラットフォーム呼び出しメンバーは、部分的に信頼された呼び出し元を許可し、文字列パラメーターを持ち、文字列を明示的にはマーシャリングしません。このために、セキュリティの脆弱性が生じる場合があります。 - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - セキュリティ上の問題を軽減するには、{1} の StructLayout.CharSet on を CharSet.Unicode に設定するか、またはフィールドを明示的に UnmanagedType.LPWStr としてマーシャリングすることで、フィールド {0} を Unicode としてマーシャリングします。この文字列を ANSI またはシステム依存としてマーシャリングする必要がある場合は、BestFitMapping 属性を使用して最適なマッピングを無効にし、セキュリティ強化のために ThrowOnUnmappableChar が有効に設定されていることを確認します。 - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - セキュリティ上の問題を軽減するには、{1} の StructLayout.CharSet on を CharSet.Unicode に設定するか、またはフィールドを明示的に UnmanagedType.LPWStr としてマーシャリングすることで、フィールド {0} を Unicode としてマーシャリングします。この文字列を ANSI またはシステム依存としてマーシャリングする必要がある場合は、MarshalAs を明示的に指定し、BestFitMapping 属性を使用して最適なマッピングを無効にし、セキュリティ強化のために ThrowOnUnmappableChar を有効にします。 - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - セキュリティ上の問題を軽減するには、DllImport.CharSet を CharSet.Unicode に設定するか、またはパラメーターを明示的に UnmanagedType.LPWStr としてマーシャリングすることで、パラメーター {0} を Unicode としてマーシャリングします。この文字列を ANSI またはシステム依存としてマーシャリングする必要がある場合は、セキュリティ強化のために BestFitMapping=false と設定し、さらに ThrowOnUnmappableChar=true と設定します。 - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - セキュリティ上の問題を軽減するには、DllImport.CharSet を CharSet.Unicode に設定するか、またはパラメーターを明示的に UnmanagedType.LPWStr としてマーシャリングすることで、パラメーター {0} を Unicode としてマーシャリングします。この文字列を ANSI またはシステム依存としてマーシャリングする必要がある場合は、MarshalAs を明示的に指定し、セキュリティ強化のために BestFitMapping=false と設定し、さらに ThrowOnUnmappableChar=true と設定します。 - - Specify marshaling for P/Invoke string arguments P/Invoke 文字列引数に対してマーシャリングを指定します @@ -2922,16 +2792,6 @@ 非言語的な文字列比較操作では、StringComparison パラメーターが Ordinal にも OrdinalIgnoreCase にも設定されません。パラメーターを StringComparison.Ordinal または StringComparison.OrdinalIgnoreCase に明示的に設定することによって、コードは多くの場合、高速で正確になり、信頼性が向上します。 - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0} は '{1}' を 'StringComparer' パラメーターとして {2} に渡します。非言語的な比較を実行するには、代わりに 'StringComparer.Ordinal' または 'StringComparer.OrdinalIgnoreCase' を指定してください。 - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0} は '{1}' を 'StringComparison' パラメーターとして {2} に渡します。非言語的な比較を実行するには、代わりに 'StringComparison.Ordinal' または 'StringComparison.OrdinalIgnoreCase' を指定してください。 - - Use ordinal string comparison 序数の文字列比較を使用してください diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ko.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ko.xlf index f9af4de2c4..8a4dc32207 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ko.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ko.xlf @@ -7,11 +7,6 @@ 이 필드에 'NonSerialized' 특성을 추가합니다. - - Add a public constructor that takes zero parameters - 매개 변수가 0인 공개 생성자를 추가합니다. - - Add Serializable attribute Serializable 특성 추가 @@ -172,11 +167,6 @@ Dispose 메서드는 SuppressFinalize를 호출해야 합니다. - - Reliability - 안정성 - - , , @@ -562,21 +552,6 @@ {0} 클래스의 인스턴스를 역직렬화할 때 {1} 메서드가 위험한 메서드 {2}을(를) 호출할 수 있습니다. 잠재적인 메서드 호출은 {3}입니다. - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - 생성자에서 가상 메서드를 호출하면 메서드를 호출하는 인스턴스에 대한 생성자가 실행되지 않을 수 있습니다. - - - - Do not call overridable methods in constructors - 생성자에서 재정의 가능한 메서드를 호출하지 마세요. - - - - Do not call overridable methods in constructors - 생성자에서 재정의 가능한 메서드를 호출하지 마세요. - - Do not call {0} on an {1} value {1} 값의 {0}을(를) 호출하지 마세요. @@ -587,21 +562,6 @@ ImmutableCollection 값의 ToImmutableCollection을 호출하지 마세요. - - Do not author general catch handlers in code that receives corrupted state exceptions. - 손상된 상태 예외를 수신하는 코드에서 일반 catch 처리기를 작성하지 마세요. - - - - Do not catch corrupted state exceptions in general handlers. - 일반 처리기에서 손상된 상태 예외를 catch하지 마세요. - - - - Do not catch corrupted state exceptions in general handlers. - 일반 처리기에서 손상된 상태 예외를 catch하지 마세요. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource에는 기본 작업을 제어하는 TaskCreationOptions를 사용하는 생성자와 이 작업에 저장된 상태 개체를 사용하는 생성자가 있습니다. 실수로 TaskCreationOptions 대신 TaskContinuationOptions를 전달하면 이 옵션을 상태로 처리하는 호출이 발생합니다. @@ -982,16 +942,6 @@ {0}은(는) 비보안 난수 생성기입니다. 보안을 위해 임의성이 필요한 경우 암호화된 보안 난수 생성기를 사용하세요. - - Do not use insecure cryptographic algorithm MD5. - 안전하지 않은 암호화 알고리즘 MD5를 사용하지 마세요. - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - 이 형식은 안전하지 않게 암호화된 해시 알고리즘인 MD5를 구현합니다. MD5 및 HMACMD5 알고리즘에서 계산상 해시 충돌이 발생할 수 있습니다. 이 사용법을 SHA-2 패밀리 해시 알고리즘(SHA512, SHA384, SHA256)으로 바꾸세요. - - Do not use obsolete key derivation function 사용되지 않는 키 파생 함수 사용 안 함 @@ -1042,16 +992,6 @@ 값 형식이 있는 ReferenceEquals를 사용하면 안 됨 - - Do not use insecure cryptographic algorithm SHA1. - 안전하지 않은 암호화 알고리즘 SHA1을 사용하지 마세요. - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - 이 형식은 안전하지 않게 암호화된 해시 알고리즘인 SHA1을 구현합니다. SHA-1 및 SHA-0 알고리즘에서 계산상 해시 충돌이 발생할 수 있습니다. 이 사용법을 SHA-2 패밀리 해시 알고리즘(SHA512, SHA384, SHA256)으로 바꾸세요. - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. stackalloc에서 할당된 스택 공간은 현재 메서드의 호출이 끝날 때만 릴리스됩니다. 루프에서 stackalloc를 사용하면 바인딩되지 않은 스택 증가 및 최종 스택 오버플로 조건이 발생할 수 있습니다. @@ -1247,21 +1187,6 @@ {3} '{0}'의 유형에 '{1}' 미리 보기 유형이 포함되어 있으며 미리 보기 기능을 선택해야 합니다. 자세한 내용은 {2}를 참조하세요. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - 종료는 상속 계층 구조를 통해 전파되어야 합니다. 이를 보장하려면 형식은 고유 Finalize 메서드에서 기본 클래스 Finalize 메서드를 호출해야 합니다. - - - - Finalizers should call base class finalizer - 종료자가 기본 클래스 종료자를 호출해야 합니다. - - - - Finalizers should call base class finalizer - 종료자가 기본 클래스 종료자를 호출해야 합니다. - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. 'CancellationToken' 매개 변수를 메서드로 전달하여 작업 취소 알림이 올바르게 전파되도록 하거나, 명시적으로 'CancellationToken.None'을 전달하여 의도적으로 토큰을 전파하지 않음을 나타냅니다. @@ -1872,26 +1797,6 @@ {3} '{0}'은(는) 미리 보기 방법 '{1}'을(를) 재정의하므로 미리 보기 기능을 선택해야 합니다. 자세한 내용은 {2}를 참조하세요. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - 이 규칙은 각 매개 변수 및 P/Invoke의 반환 값의 크기를 평가하며 32비트 및 64비트 운영 체제에서 비관리 코드로 마샬링된 경우 매개 변수의 크기가 올바른지 확인합니다. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - 코드에 선언된 것처럼 P/Invoke {1}의 {0} 매개 변수는 {3} 플랫폼에서 {2}바이트가 됩니다. 이 API의 실제 네이티브 선언에 따르면 {3} 플랫폼에서 {4}바이트여야 하므로 잘못된 상황입니다. {5} 대신 사용할 데이터 형식을 결정하려면 MSDN Platform SDK 문서를 참조하세요. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - 코드에 선언된 것처럼 P/Invoke {0}의 반환 형식은 {2} 플랫폼에서 {1}바이트가 됩니다. 이 API의 실제 네이티브 선언에 따르면 {2} 플랫폼에서 {3}바이트여야 하므로 잘못된 상황입니다. {4} 대신 사용할 데이터 형식을 결정하려면 MSDN Platform SDK 문서를 참조하세요. - - - - PInvoke declarations should be portable - PInvoke 선언은 이식 가능해야 합니다. - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. public 형식의 public 또는 protected 메서드에 System.Runtime.InteropServices.DllImportAttribute 특성(Visual Basic의 선언 키워드에서 구현함)이 있습니다. 이러한 메서드는 노출할 수 없습니다. @@ -2287,21 +2192,6 @@ 문자열 리터럴을 char 리터럴로 바꾸기 - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - 예외가 다시 throw되었으며 throw 문에서 해당 예외가 명시적으로 지정되었습니다. throw 문에서 예외를 지정하여 다시 throw한 경우 해당 예외를 throw한 원래 메서드와 현재 메서드 사이의 메서드 호출 목록이 손실됩니다. - - - - Rethrow to preserve stack details - 다시 throw하여 스택 정보를 유지하세요. - - - - Rethrow to preserve stack details - 다시 throw하여 스택 정보를 유지하세요. - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. '{1}' 메서드의 '{0}'이(가) '{3}' 메서드의 '{2}'에서 사용자 제어 데이터에 의해 감염될 수 있는 잠재적인 DLL 삽입 취약성이 발견되었습니다. @@ -2562,26 +2452,6 @@ 플랫폼 호출 멤버는 부분적으로 신뢰하는 호출자를 허용하고, 문자열 매개 변수를 보유하며, 문자열을 명시적으로 마샬링하지 않습니다. 이로 인해 잠재적인 보안 취약성이 발생할 수 있습니다. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - 보안 위험을 줄이려면 {1}의 StructLayout.CharSet을 CharSet.Unicode로 설정하거나 {0} 필드를 명시적으로 UnmanagedType.LPWStr로 마샬링하여 필드를 유니코드로 마샬링하세요. 이 문자열을 ANSI 또는 시스템 설정으로 마샬링해야 하는 경우 BestFitMapping 특성을 사용하여 최적 문자 매핑을 해제하세요. 또한 ThrowOnUnmappableChar이 설정되어 있는지 확인하여 보안을 강화하세요. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - 보안 위험을 줄이려면 {1}의 StructLayout.CharSet을 CharSet.Unicode로 설정하거나 {0} 필드를 명시적으로 UnmanagedType.LPWStr로 마샬링하여 필드를 유니코드로 마샬링하세요. 이 문자열을 ANSI 또는 시스템 설정으로 마샬링해야 하는 경우 MarshalAs를 명시적으로 지정하고, BestFitMapping 특성을 사용하여 최적 문자 매핑을 해제하세요. 또한 ThrowOnUnmappableChar이 설정되어 있는지 확인하여 보안을 강화하세요. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - 보안 위험을 줄이려면 DllImport.CharSet을 CharSet.Unicode로 설정하거나 {0} 매개 변수를 명시적으로 UnmanagedType.LPWStr로 마샬링하여 매개 변수를 유니코드로 마샬링하세요. 이 문자열을 ANSI 또는 시스템 설정으로 마샬링해야 하는 경우 BestFitMapping=false를 설정하세요. 또한 ThrowOnUnmappableChar=true를 설정하여 보안을 강화하세요. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - 보안 위험을 줄이려면 DllImport.CharSet을 CharSet.Unicode로 설정하거나 {0} 매개 변수를 명시적으로 UnmanagedType.LPWStr로 마샬링하여 매개 변수를 유니코드로 마샬링하세요. 이 문자열을 ANSI 또는 시스템 설정으로 마샬링해야 하는 경우 MarshalAs를 명시적으로 지정하고, BestFitMapping=false를 설정하세요. 또한 ThrowOnUnmappableChar=true를 설정하여 보안을 강화하세요. - - Specify marshaling for P/Invoke string arguments P/Invoke 문자열 인수에 대해 마샬링을 지정하세요. @@ -2922,16 +2792,6 @@ 비언어적 문자열 비교 작업에서는 StringComparison 매개 변수를 서수 또는 OrdinalIgnoreCase로 설정하지 않습니다. 매개 변수를 명시적으로 StringComparison.Ordinal 또는 StringComparison.OrdinalIgnoreCase로 설정하면 코드의 속도가 빨라지고, 정확도와 신뢰도가 더 높아집니다. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0}에서는 '{1}'을(를) 'StringComparer' 매개 변수로 {2}에 전달합니다. 비언어적 비교 작업을 수행하려면 'StringComparer.Ordinal' 또는 'StringComparer.OrdinalIgnoreCase'를 지정하세요. - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0}에서는 '{1}'을(를) 'StringComparison' 매개 변수로 {2}에 전달합니다. 비언어적 비교 작업을 수행하려면 'StringComparison.Ordinal' 또는 'StringComparison.OrdinalIgnoreCase'를 지정하세요. - - Use ordinal string comparison 서수 문자열 비교 사용 diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.pl.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.pl.xlf index 63f409a9a3..12be1a7404 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.pl.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.pl.xlf @@ -7,11 +7,6 @@ Dodaj atrybut „NonSerialized” do tego pola. - - Add a public constructor that takes zero parameters - Dodaj konstruktora publicznego, który przyjmuje zero parametrów - - Add Serializable attribute Dodaj atrybut Serializable @@ -172,11 +167,6 @@ Metoda Dispose powinna wywoływać metodę SuppressFinalize - - Reliability - Niezawodność - - , , @@ -562,21 +552,6 @@ Podczas deserializacji wystąpienia klasy {0} metoda {1} może wywołać niebezpieczną metodę {2}. Potencjalne wywołania metod to: {3}. - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - Gdy konstruktor wywołuje metodę wirtualną, konstruktor wystąpienia wywołującego metodę może nie zostać wykonany. - - - - Do not call overridable methods in constructors - Nie wywołuj w konstruktorach metod, które można przesłaniać - - - - Do not call overridable methods in constructors - Nie wywołuj w konstruktorach metod, które można przesłaniać - - Do not call {0} on an {1} value Nie wywołuj elementu {0} dla wartości {1} @@ -587,21 +562,6 @@ Nie wywołuj elementu ToImmutableCollection dla wartości ImmutableCollection - - Do not author general catch handlers in code that receives corrupted state exceptions. - Nie twórz ogólnych procedur obsługi przechwytywania w kodzie, który odbiera wyjątki stanu uszkodzenia. - - - - Do not catch corrupted state exceptions in general handlers. - Nie przechwytuj wyjątków stanu uszkodzenia w ogólnych procedurach obsługi. - - - - Do not catch corrupted state exceptions in general handlers. - Nie przechwytuj wyjątków stanu uszkodzenia w ogólnych procedurach obsługi. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. Element TaskCompletionSource ma konstruktory przyjmujące opcje TaskCreationOptions, które kontrolują podstawowe zadanie, oraz konstruktory, które przyjmują stan obiektu przechowywany w zadaniu. Przypadkowe przekazanie opcji TaskContinuationOptions zamiast opcji TaskCreationOptions spowoduje, że wywołanie potraktuje opcje jako stan. @@ -982,16 +942,6 @@ {0} to niezabezpieczony generator liczb losowych. Użyj kryptograficznie zabezpieczonego generatora liczb losowych, gdy losowość jest wymagana ze względów bezpieczeństwa. - - Do not use insecure cryptographic algorithm MD5. - Nie używaj niezabezpieczonego algorytmu kryptograficznego MD5. - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Ten typ implementuje niezabezpieczoną kryptograficznie funkcję skrótu MD5. Istnieje możliwość wystąpienia kolizji skrótów w przypadku algorytmów MD5 i HMACMD5. Zastąp to użycie algorytmem wartości skrótu z rodziny SHA-2 (SHA512, SHA384, SHA256). - - Do not use obsolete key derivation function Nie używaj przestarzałej funkcji wyprowadzenia klucza @@ -1042,16 +992,6 @@ Nie używaj metody ReferenceEquals z typami wartości - - Do not use insecure cryptographic algorithm SHA1. - Nie używaj niezabezpieczonego algorytmu kryptograficznego SHA1. - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Ten typ implementuje niezabezpieczoną kryptograficznie funkcję skrótu SHA1. Istnieje możliwość wystąpienia kolizji skrótów w przypadku algorytmów SHA-1 i SHA-0. Zastąp to użycie algorytmem wartości skrótu z rodziny SHA-2 (SHA512, SHA384, SHA256). - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. Miejsce na stosie przydzielone przy użyciu słowa kluczowego stackalloc jest zwalniane jedynie na końcu wywołania bieżącej metody. Użycie go w pętli może spowodować nieograniczone powiększanie stosu i, ostatecznie, warunki przepełnienia stosu. @@ -1247,21 +1187,6 @@ {3} „{0}” — typ tego elementu zawiera typ w wersji zapoznawczej „{1}” i wymaga wyrażenia zgody na korzystanie z funkcji w wersji zapoznawczej. Aby uzyskać więcej informacji, zobacz {2}. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - Finalizacja musi być propagowana w hierarchii dziedziczenia. Aby to zagwarantować, typy muszą wywoływać metodę Finalize ich klasy podstawowej we własnej metodzie Finalize. - - - - Finalizers should call base class finalizer - Finalizatory powinny wywoływać finalizator klasy podstawowej - - - - Finalizers should call base class finalizer - Finalizatory powinny wywoływać finalizator klasy podstawowej - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. Prześlij dalej parametr „CancellationToken” do metod, aby upewnić się, że powiadomienia o anulowaniu operacji zostaną prawidłowo rozpropagowane, lub przekaż element „CancellationToken.None” jawnie, aby wskazać celowe niepropagowanie tokenu. @@ -1872,26 +1797,6 @@ {3} „{0}” przesłania metodę w wersji zapoznawczej „{1}” i dlatego wymaga wyrażenia zgody na korzystanie z funkcji w wersji zapoznawczej. Aby uzyskać więcej informacji, zobacz {2}. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - Ta reguła wylicza rozmiar poszczególnych parametrów i zwraca wartość metody P/Invoke oraz sprawdza, czy rozmiar parametru jest prawidłowy, gdy jest kierowany do kodu niezarządzanego w 32- i 64-bitowych systemach operacyjnych. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - Zgodnie z deklaracją w kodzie, parametr {0} metody P/Invoke {1} będzie mieć szerokość {2} bajtów na platformach: {3}. Ta wartość jest niepoprawna, ponieważ rzeczywista natywna deklaracja tego interfejsu API wskazuje, że powinien on mieć szerokość {4} bajtów na platformach {3}. Pomoc dotyczącą określania typu danych, którego należy użyć zamiast {5}, zawiera dokumentacja zestawu SDK platformy MSDN. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Zgodnie z deklaracją w kodzie typ zwracany metody P/Invoke {0} będzie mieć szerokość {1} bajtów na platformach {2}. Ta wartość jest niepoprawna, ponieważ rzeczywista natywna deklaracja tego interfejsu API wskazuje, że powinien on mieć szerokość {3} bajtów na platformach {2}. Pomoc dotyczącą określania typu danych, którego należy użyć zamiast {4}, zawiera dokumentacja zestawu SDK platformy MSDN. - - - - PInvoke declarations should be portable - Deklaracje metody PInvoke powinny być przenośne - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. Metoda publiczna lub chroniona w typie publicznym ma atrybut System.Runtime.InteropServices.DllImportAttribute (implementowany również przez słowo kluczowe Declare w języku Visual Basic). Takie metody nie powinny być ujawniane. @@ -2287,21 +2192,6 @@ Zamień literał ciągu na literał char - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - Wyjątek jest zgłaszany ponownie i jest jawnie określony w instrukcji throw. Jeśli wyjątek zostanie zgłoszony ponownie przez określenie wyjątku w instrukcji throw, lista wywołań metod między oryginalną metodą zgłaszającą wyjątek a bieżącą metodą zostanie utracona. - - - - Rethrow to preserve stack details - Zgłoś ponownie wyjątek, aby zachować szczegóły stosu - - - - Rethrow to preserve stack details - Zgłoś ponownie wyjątek, aby zachować szczegóły stosu - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. Znaleziono potencjalną lukę umożliwiającą wstrzyknięcie biblioteki DLL, gdzie element „{0}” w metodzie „{1}” może zostać zanieczyszczony danymi kontrolowanymi przez użytkownika z elementu „{2}” w metodzie „{3}”. @@ -2562,26 +2452,6 @@ Element członkowski wywołania platformy zezwala na częściowo zaufany kod wywołujący, ma parametr ciągu i nie kieruje jawnie łańcuchem. Może to być przyczyną potencjalnej luki w zabezpieczeniach. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - Aby ograniczyć ryzyko związane z zabezpieczeniami, kieruj pole {0} w kodowaniu Unicode przez ustawienie właściwości StructLayout.CharSet w elemencie {1} na wartość CharSet.Unicode lub przez jawne kierowanie pola jako typu UnmanagedType.LPWStr. Jeśli musisz kierować ten ciąg w kodowaniu ANSI lub zależnym od systemu, użyj atrybutu BestFitMapping, aby wyłączyć mapowanie najlepszego dopasowania. Aby zwiększyć bezpieczeństwo, upewnij się również, że właściwość ThrowOnUnmappableChar jest włączona. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Aby ograniczyć ryzyko związane z zabezpieczeniami, kieruj pole {0} w kodowaniu Unicode przez ustawienie właściwości StructLayout.CharSet w elemencie {1} na wartość CharSet.Unicode lub przez jawne kierowanie pola jako typu UnmanagedType.LPWStr. Jeśli musisz kierować ten ciąg w kodowaniu ANSI lub zależnym od systemu, określ jawnie atrybut MarshalAs i użyj atrybutu BestFitMapping, aby wyłączyć mapowanie najlepszego dopasowania. Aby zwiększyć bezpieczeństwo, upewnij się również, że właściwość ThrowOnUnmappableChar jest włączona. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Aby ograniczyć ryzyko związane z zabezpieczeniami, kieruj parametr {0} w kodowaniu Unicode przez ustawienie właściwości DllImport.CharSet na wartość CharSet.Unicode lub przez jawne kierowanie parametru jako typu UnmanagedType.LPWStr. Jeśli musisz kierować ten ciąg w kodowaniu ANSI lub zależnym od systemu, ustaw wartość BestFitMapping=false. Aby zwiększyć bezpieczeństwo, ustaw również wartość ThrowOnUnmappableChar=true. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Aby ograniczyć ryzyko związane z zabezpieczeniami, kieruj parametr {0} w kodowaniu Unicode przez ustawienie właściwości DllImport.CharSet na wartość CharSet.Unicode lub przez jawne kierowanie parametru jako typu UnmanagedType.LPWStr. Jeśli musisz kierować ten ciąg w kodowaniu ANSI lub zależnym od systemu, określ jawnie atrybut MarshalAs i ustaw wartość BestFitMapping=false. Aby zwiększyć bezpieczeństwo, ustaw również wartość ThrowOnUnmappableChar=true. - - Specify marshaling for P/Invoke string arguments Określ kierowanie dla argumentów ciągu P/Invoke @@ -2922,16 +2792,6 @@ Operacja porównywania ciągów nieuwzględniająca zasad języka nie ustawia parametru StringComparison na wartość Ordinal ani OrdinalIgnoreCase. Jawne ustawienie parametru na wartość StringComparison.Ordinal lub StringComparison.OrdinalIgnoreCase umożliwia często przyspieszenie kodu oraz zwiększenie jego poprawności i niezawodności. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - Element {0} przekazuje wartość „{1}” jako parametr „StringComparer” do metody {2}. Aby wykonać porównanie nieuwzględniające zasad języka, określ zamiast niej wartość „StringComparer.Ordinal” lub „StringComparer.OrdinalIgnoreCase”. - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - Element {0} przekazuje wartość „{1}” jako parametr „StringComparison” do metody {2}. Aby wykonać porównanie nieuwzględniające zasad języka, określ zamiast niej wartość „StringComparison.Ordinal” lub „StringComparison.OrdinalIgnoreCase”. - - Use ordinal string comparison Użyj porównywania ciągów porządkowych diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.pt-BR.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.pt-BR.xlf index e5b6ac382e..3d086963ed 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.pt-BR.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.pt-BR.xlf @@ -7,11 +7,6 @@ Adicione o atributo 'NonSerialized' a esse campo. - - Add a public constructor that takes zero parameters - Adicionar um construtor público que usa zero parâmetros - - Add Serializable attribute Adicionar o atributo Serializable @@ -172,11 +167,6 @@ Os métodos Dispose devem chamar SuppressFinalize - - Reliability - Confiabilidade - - , , @@ -562,21 +552,6 @@ Ao desserializar uma instância da classe {0}, o método {1} pode chamar o método perigoso {2}. As possíveis invocações de método são: {3}. - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - Quando um construtor chama um método virtual, o construtor para a instância que invoca o método pode não ter sido executado. - - - - Do not call overridable methods in constructors - Não chamar métodos substituíveis em construtores - - - - Do not call overridable methods in constructors - Não chamar métodos substituíveis em construtores - - Do not call {0} on an {1} value Não chamar {0} em um valor {1} @@ -587,21 +562,6 @@ Não chamar ToImmutableCollection em um valor ImmutableCollection - - Do not author general catch handlers in code that receives corrupted state exceptions. - Não crie manipuladores catch gerais no código que recebe exceções de estado corrompido. - - - - Do not catch corrupted state exceptions in general handlers. - Não capture exceções de estado corrompido em manipuladores gerais. - - - - Do not catch corrupted state exceptions in general handlers. - Não capture exceções de estado corrompido em manipuladores gerais. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource tem construtores que assumem o TaskCreationOptions que controla a Tarefa subjacente e construtores que assumem o estado do objeto armazenado na tarefa. Passar acidentalmente um TaskContinuationOptions em vez de um TaskCreationOptions fará com que a chamada trate as opções como estado. @@ -982,16 +942,6 @@ {0} é um gerador de números aleatórios não seguro. Use geradores de números aleatórios criptograficamente seguros quando a aleatoriedade for necessária para segurança. - - Do not use insecure cryptographic algorithm MD5. - Não use o algoritmo de criptografia não seguro MD5. - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Esse tipo implementa MD5, uma função de hash criptograficamente não segura. As colisões de hash são computacionalmente viáveis para os algoritmos MD5 e HMACMD5. Substitua esse uso por um algoritmo hash da família SHA-2 (SHA512, SHA384, SHA256). - - Do not use obsolete key derivation function Não use a função de derivação de chave obsoleta @@ -1042,16 +992,6 @@ Não use ReferenceEquals com tipos de valor - - Do not use insecure cryptographic algorithm SHA1. - Não use o algoritmo de criptografia não seguro SHA1. - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Esse tipo implementa SHA1, uma função de hash criptograficamente não segura. As colisões de hash são computacionalmente viáveis para os algoritmos SHA-1 e SHA-0. Substitua esse uso por um algoritmo hash da família SHA-2 (SHA512, SHA384, SHA256). - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. O espaço de pilha alocado por um stackalloc é liberado somente no final da invocação do método atual. O uso de um stackalloc em um loop pode resultar em um aumento ilimitado da pilha e em condições eventuais de excedente de pilha. @@ -1247,21 +1187,6 @@ {3}O tipo de “{0}” contém o tipo de visualização “{1}” e requer a aceitação dos recursos de visualização. Consulte {2} para obter mais informações. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - A finalização deve ser propagada por meio da hierarquia de herança. Para garantir isso, os tipos devem chamar seu método Finalize de classe base em seu próprio método Finalize. - - - - Finalizers should call base class finalizer - Os finalizadores devem chamar o finalizador da classe base - - - - Finalizers should call base class finalizer - Os finalizadores devem chamar o finalizador da classe base - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. Encaminhe o parâmetro 'CancellationToken' para os métodos para garantir que as notificações de cancelamento da operação sejam propagadas corretamente ou passe o 'CancellationToken.None' explicitamente para indicar que ele está intencionalmente não propagando o token. @@ -1872,26 +1797,6 @@ {3}“{0}” substitui o método de visualização “{1}” e, portanto, precisa aceitar os recursos de visualização. Consulte {2}para obter mais informações. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - Essa regra avalia o tamanho de cada parâmetro e o valor retornado de um P/Invoke e verifica se o tamanho do parâmetro está correto quando o marshaling foi realizado no código não gerenciado em sistemas operacionais de 32 bits e 64 bits. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - Conforme declarado em seu código, o parâmetro {0} de P/Invoke {1} terá {2} bytes nas plataformas {3}. Isso não está correto, já que a declaração nativa real desta API indica que ele deve ter {4} bytes nas plataformas {3}. Consulte a documentação do SDK da Plataforma MSDN para obter ajuda para determinar que tipo de dados deve ser usado em vez de {5}. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Conforme declarado em seu código, o tipo de retorno de P/Invoke {0} terá {1} bytes nas plataformas {2}. Isso não está correto, já que a declaração nativa real desta API indica que ele deve ter {3} bytes nas plataformas {2}. Consulte a documentação do SDK da Plataforma MSDN para obter ajuda para determinar que tipo de dados deve ser usado em vez de {4}. - - - - PInvoke declarations should be portable - Declarações PInvoke devem ser portáteis - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. Um método público ou protegido em um tipo público tem o atributo System.Runtime.InteropServices.DllImportAttribute (implementado também pela palavra-chave Declare no Visual Basic). Esses métodos não devem ser expostos. @@ -2287,21 +2192,6 @@ Substituir literal de cadeia de caracteres por literal char - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - Uma exceção é gerada novamente e a exceção é especificada explicitamente na instrução throw. Se uma exceção for gerada novamente especificando a exceção na instrução throw, a lista de métodos será chamada entre o método original que gerou a exceção e o método atual será perdido. - - - - Rethrow to preserve stack details - Gerar novamente para preservar detalhes da pilha - - - - Rethrow to preserve stack details - Gerar novamente para preservar detalhes da pilha - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. Foi encontrada uma possível vulnerabilidade de injeção de DLL, em que o '{0}' no método '{1}' pode ter sido afetado pelos dados controlados pelo usuário de '{2}' no método '{3}'. @@ -2562,26 +2452,6 @@ Um membro de invocação de plataforma permite chamadores parcialmente confiáveis, tem um parâmetro de cadeia de caracteres e não realiza marshaling da cadeia de caracteres explicitamente. Isso pode causar uma potencial vulnerabilidade de segurança. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - Para reduzir o risco de segurança, realize marshaling do campo {0} como Unicode, definindo StructLayout.CharSet em {1} como CharSet.Unicode ou realizando marshaling do campo explicitamente como UnmanagedType.LPWStr. Se você precisar realizar marshaling dessa cadeia de caracteres como ANSI ou dependente do sistema, use o atributo BestFitMapping para desativar o mapeamento de melhor ajuste e para maior segurança, ative ThrowOnUnmappableChar. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Para reduzir o risco de segurança, realize marshaling do campo {0} como Unicode, definindo StructLayout.CharSet em {1} como CharSet.Unicode ou realizando marshaling do campo explicitamente como UnmanagedType.LPWStr. Se você precisar realizar marshaling dessa cadeia de caracteres como ANSI ou dependente do sistema, especifique MarshalAs explicitamente, use o atributo BestFitMapping para desativar o mapeamento de melhor ajuste e para maior segurança, ative ThrowOnUnmappableChar. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Para reduzir o risco de segurança, realize marshaling do parâmetro {0} como Unicode, definindo DllImport.CharSet como CharSet.Unicode ou realizando marshaling do parâmetro explicitamente como UnmanagedType.LPWStr. Se você precisar realizar marshaling dessa cadeia de caracteres como ANSI ou dependente do sistema, defina BestFitMapping=false; para maior segurança, também defina ThrowOnUnmappableChar=true. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Para reduzir o risco de segurança, realize marshaling do parâmetro {0} como Unicode, definindo DllImport.CharSet como CharSet.Unicode ou realizando marshaling do parâmetro explicitamente como UnmanagedType.LPWStr. Se você precisar realizar marshaling dessa cadeia de caracteres como ANSI ou dependente do sistema, especifique MarshalAs explicitamente e defina BestFitMapping=false; para maior segurança, também defina ThrowOnUnmappableChar=true. - - Specify marshaling for P/Invoke string arguments Especificar marshaling para argumentos de cadeias de caracteres P/Invoke @@ -2922,16 +2792,6 @@ Uma comparação de cadeia de caracteres não linguística não define o parâmetro StringComparison como Ordinal ou OrdinalIgnoreCase. Ao definir explicitamente o parâmetro como StringComparison.Ordinal ou StringComparison.OrdinalIgnoreCase, seu código geralmente ganha velocidade, torna-se mais correto e mais confiável. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0} passa '{1}' como o parâmetro 'StringComparer' para {2}. Em vez disso, para realizar uma comparação não linguística, especifique 'StringComparer.Ordinal' ou 'StringComparer.OrdinalIgnoreCase'. - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0} passa '{1}' como o parâmetro 'StringComparison' para {2}. Em vez disso, para realizar uma comparação não linguística, especifique 'StringComparison.Ordinal' ou 'StringComparison.OrdinalIgnoreCase'. - - Use ordinal string comparison Usar a comparação de cadeia de caracteres ordinal diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ru.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ru.xlf index 0b273728fc..9696475f8d 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ru.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.ru.xlf @@ -7,11 +7,6 @@ Добавьте атрибут "NonSerialized" в это поле. - - Add a public constructor that takes zero parameters - Добавить общедоступный конструктор, принимающий нулевые параметры - - Add Serializable attribute Добавить атрибут Serializable @@ -172,11 +167,6 @@ Методы Dispose должны вызывать SuppressFinalize - - Reliability - Надежность - - , , @@ -562,21 +552,6 @@ При десериализации экземпляра класса {0} метод {1} может вызывать опасный метод {2}. Потенциальные вызовы методов: {3}. - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - Когда конструктор вызывает виртуальный метод, конструктор может не выполняться для экземпляра, вызывающего этот метод. - - - - Do not call overridable methods in constructors - Не вызывайте переопределяемые методы в конструкторах - - - - Do not call overridable methods in constructors - Не вызывайте переопределяемые методы в конструкторах - - Do not call {0} on an {1} value Не вызывайте {0} для значения {1} @@ -587,21 +562,6 @@ Не вызывайте ToImmutableCollection для значения ImmutableCollection - - Do not author general catch handlers in code that receives corrupted state exceptions. - Не создавайте общие обработчики catch в коде, получающем исключения поврежденного состояния. - - - - Do not catch corrupted state exceptions in general handlers. - Не перехватывайте исключения поврежденного состояния в общих обработчиках. - - - - Do not catch corrupted state exceptions in general handlers. - Не перехватывайте исключения поврежденного состояния в общих обработчиках. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource содержит конструкторы, которые принимают TaskCreationOptions, управляющие базовой задачей, и конструкторы, принимающие состояние объекта, которое хранится в задаче. Случайная передача TaskContinuationOptions вместо TaskCreationOptions приведет к вызову, обрабатывающему параметры как состояние. @@ -982,16 +942,6 @@ {0} является небезопасным генератором случайных чисел. Если случайные числа требуются для обеспечения безопасности, используйте криптографически безопасные генераторы случайных чисел. - - Do not use insecure cryptographic algorithm MD5. - Не используйте небезопасный алгоритм шифрования MD5. - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Этот тип реализует криптографически небезопасную хэш-функцию MD5. С точки зрения вычислений для алгоритмов MD5 и HMACMD5 возможны хэш-конфликты. Замените на хэш-алгоритм из семейства SHA-2 (SHA512, SHA384, SHA256). - - Do not use obsolete key derivation function Не используйте устаревшую функцию формирования ключа. @@ -1042,16 +992,6 @@ Не используйте ReferenceEquals с типами значений - - Do not use insecure cryptographic algorithm SHA1. - Не используйте небезопасный алгоритм шифрования SHA1. - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Этот тип реализует криптографически небезопасную хэш-функцию SHA1. С точки зрения вычислений для алгоритмов SHA-1 и SHA-0 возможны хэш-конфликты. Замените на хэш-алгоритм из семейства SHA-2 (SHA512, SHA384, SHA256). - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. Место в стеке, выделенное stackalloc, освобождается только в конце вызова текущего метода. Использование его в цикле может привести к неограниченному увеличению стека и в конечном итоге к переполнению стека. @@ -1247,21 +1187,6 @@ Тип "{0}" {3} содержит предварительную версию типа "{1}", поэтому требуется согласие на использование предварительных версий функций. Дополнительные сведения см. в разделе {2}. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - Завершение должно распространяться через иерархию наследования. Для этого типы должны вызывать метод Finalize своего базового класса в своем собственном методе Finalize. - - - - Finalizers should call base class finalizer - Методы завершения должны вызывать метод завершения базового класса - - - - Finalizers should call base class finalizer - Методы завершения должны вызывать метод завершения базового класса - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. Перенаправьте параметр "CancellationToken" в методы, чтобы обеспечить правильное распространение уведомлений об отмене операции, или передайте "CancellationToken.None" явным образом, чтобы намеренно указать запрет на распространение маркера. @@ -1872,26 +1797,6 @@ "{0}" {3} переопределяет предварительную версию метода "{1}", поэтому требуется согласие на использование предварительных версий функций. Дополнительные сведения см. в разделе {2}. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - Это правило оценивает каждый параметр и возвращает значение P/Invoke, а затем проверяет правильность размера параметра при маршалировании в неуправляемый код на 32- и 64-разрядных операционных системах. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - Как объявлено в вашем коде, параметр {0} для P/Invoke {1} будет иметь размер {2} байт для платформ {3}. Это неправильно, так как текущее объявление в машинном коде для данного API указывает, что его размер должен быть {4} байт для платформ {3}. Обратитесь к документации по пакету SDK для платформы MSDN и выясните, какой тип данных следует использовать вместо {5}. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Как объявлено в вашем коде, тип возвращаемого значения для P/Invoke {0} будет иметь размер {1} байт для платформ {2}. Это неправильно, так как текущее объявление в машинном коде для данного API указывает, что его размер должен быть {3} байт для платформ {2}. Обратитесь к документации по пакету SDK для платформы MSDN и выясните, какой тип данных следует использовать вместо {4}. - - - - PInvoke declarations should be portable - Объявления PInvoke должны быть переносимыми - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. Общий или защищенный метод в общем типе имеет атрибут System.Runtime.InteropServices.DllImportAttribute (также реализуемый ключевым словом Declare в Visual Basic). Предоставлять такие методы не следует. @@ -2287,21 +2192,6 @@ Заменить строковый литерал на знаковый литерал - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - Исключение выдается повторно и явно указывается в операторе throw. Если исключение порождается повторно путем его указания в операторе throw, список вызовов метода между исходным методом, породившим исключение, и текущим методом теряется. - - - - Rethrow to preserve stack details - Повторно порождайте исключения для сохранения сведений стека - - - - Rethrow to preserve stack details - Повторно порождайте исключения для сохранения сведений стека - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. Обнаружена потенциальная уязвимость к внедрению DLL, где "{0}" в методе "{1}" может быть испорчен пользовательскими данными из "{2}" в методе "{3}". @@ -2562,26 +2452,6 @@ Член вызова неуправляемого кода разрешает вызовы с неполным доверием, имеет строковый параметр и не маршалирует строку явным образом. Это может привести к уязвимости системы безопасности. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - Чтобы уменьшить угрозу безопасности, маршалируйте поле {0} как Юникод, установив значение StructLayout.CharSet для StructLayout.CharSet в {1} либо явно маршалировав поле как UnmanagedType.LPWStr. Если необходимо маршалировать эту строку как ANSI или зависящую от системы, используйте атрибут BestFitMapping для отключения сопоставления путем автоматического подбора, а также включите параметр ThrowOnUnmappableChar. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Чтобы уменьшить угрозу безопасности, маршалируйте поле {0} как Юникод, установив значение StructLayout.CharSet для StructLayout.CharSet в {1} либо явно маршалировав поле как UnmanagedType.LPWStr. Если необходимо маршалировать эту строку как ANSI или зависящую от системы, явно укажите MarshalAs, используйте атрибут BestFitMapping для отключения сопоставления путем автоматического подбора, а также включите параметр ThrowOnUnmappableChar для обеспечения дополнительной безопасности. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Чтобы уменьшить угрозу безопасности, маршалируйте параметр {0} как Юникод, установив значение CharSet.Unicode для DllImport.CharSet либо явно маршалировав параметр как UnmanagedType.LPWStr. Если необходимо маршалировать эту строку как ANSI или зависящую от системы, установите BestFitMapping=false; для обеспечения дополнительной безопасности также установите ThrowOnUnmappableChar=true. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Чтобы уменьшить угрозу безопасности, маршалируйте параметр {0} как Юникод, установив значение CharSet.Unicode для DllImport.CharSet либо явно маршалировав параметр как UnmanagedType.LPWStr. Если необходимо маршалировать эту строку как ANSI или зависящую от системы, явно укажите MarshalAs и установите BestFitMapping=false; для обеспечения дополнительной безопасности также установите ThrowOnUnmappableChar=true. - - Specify marshaling for P/Invoke string arguments Укажите маршалинг для строковых аргументов P/Invoke @@ -2922,16 +2792,6 @@ Нелингвистическая операция сравнения строк не задает для параметра StringComparison значение Ordinal или OrdinalIgnoreCase. Задав явным образом значение StringComparison.Ordinal или StringComparison.OrdinalIgnoreCase для параметра, можно сделать код более быстродействующим, корректным и надежным. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0} передает "{1}" в {2} в качестве параметра "StringComparer". Чтобы выполнить нелингвистическое сравнение, укажите "StringComparer.Ordinal" или "StringComparer.OrdinalIgnoreCase". - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0} передает "{1}" в {2} в качестве параметра "StringComparison". Чтобы выполнить нелингвистическое сравнение, укажите "StringComparison.Ordinal" или "StringComparison.OrdinalIgnoreCase". - - Use ordinal string comparison Использование порядкового сравнения строк diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.tr.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.tr.xlf index b3892dc09d..b8b66d6d12 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.tr.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.tr.xlf @@ -7,11 +7,6 @@ Bu alana 'NonSerialized' özniteliğini ekleyin. - - Add a public constructor that takes zero parameters - Sıfır parametrelerini alan ortak bir oluşturucu ekleyin - - Add Serializable attribute Serileştirilebilir öznitelik ekle @@ -172,11 +167,6 @@ Dispose yöntemleri tarafından SuppressFinalize çağrılmalıdır - - Reliability - Güvenilirlik - - , , @@ -562,21 +552,6 @@ {0} sınıfının bir örneği seri durumdan çıkarılırken, {1} metodu tehlikeli {2} metodunu çağırabilir. Olası metot çağırmaları: {3}. - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - Bir oluşturucu tarafından sanal bir yöntem çağrıldığında, yöntemi tetikleyen örneğin oluşturucusu yürütülmemiş olabilir. - - - - Do not call overridable methods in constructors - Oluşturucularda geçersiz kılınabilen yöntemleri çağırmayın - - - - Do not call overridable methods in constructors - Oluşturucularda geçersiz kılınabilen yöntemleri çağırmayın - - Do not call {0} on an {1} value Bir {1} değeri üzerinde {0} çağırmayın @@ -587,21 +562,6 @@ Bir ImmutableCollection değeri üzerinde ToImmutableCollection çağırmayın - - Do not author general catch handlers in code that receives corrupted state exceptions. - Kodda bozuk durum özel durumlarını alan genel yakalama işleyicileri yazmayın. - - - - Do not catch corrupted state exceptions in general handlers. - Genel işleyicilerde bozuk durum özel durumlarını yakalamayın. - - - - Do not catch corrupted state exceptions in general handlers. - Genel işleyicilerde bozuk durum özel durumlarını yakalamayın. - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource, temel alınan görevi denetleyen TaskCreationOptions öğesini ve görevde depolanan nesne durumunu alan oluşturucuları alan oluşturucuları içerir. TaskCreationOptions yerine yanlışlıkla TaskContinuationOptions geçirilmesi, çağrının seçenekleri durum olarak değerlendirmesine neden olur. @@ -982,16 +942,6 @@ {0}, güvenli olmayan bir rastgele sayı üreticidir. Güvenlik için rastgelelik gerekli olduğunda şifreli olarak güvenli rastgele sayı üreticileri kullanın. - - Do not use insecure cryptographic algorithm MD5. - Güvenli olmayan MD5 kriptografik algoritmasını kullanmayın. - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Bu tür, kriptografik olarak güvenli olmayan bir karma işlevi olan MD5 uygular. MD5 ve HMACMD5 algoritmaları için karma çakışmaları işlemsel olarak uygundur. Bu kullanımı bir SHA-2 aile karma algoritmasıyla (SHA512, SHA384, SHA256) değiştirin. - - Do not use obsolete key derivation function Artık kullanılmayan anahtar türetme işlevini kullanma @@ -1042,16 +992,6 @@ ReferenceEquals metodunu değer türleriyle birlikte kullanmayın - - Do not use insecure cryptographic algorithm SHA1. - Güvenli olmayan SHA1 kriptografik algoritmasını kullanmayın. - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - Bu tür, kriptografik olarak güvenli olmayan bir karma işlevi olan SHA1 uygular. SHA-1 ve SHA-0 algoritmaları için karma çakışmaları işlemsel olarak uygundur. Bu kullanımı bir SHA-2 aile karma algoritmasıyla (SHA512, SHA384, SHA256) değiştirin. - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. Stackalloc tarafından ayrılan yığın alanı yalnızca geçerli metot çağrısının sonunda bırakılır. Bunu bir döngüde kullanmak, sınırsız yığın büyümesi ve sonunda yığın taşması durumlarına neden olabilir. @@ -1247,21 +1187,6 @@ {3} '{0}' türü, '{1}' önizleme türünü içerdiğinden önizleme özelliklerini kabul etmesi gerekir. Daha fazla bilgi için bkz. {2}. - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - Sonlandırma, devralma hiyerarşisine yayılmalıdır. Bunun sağlanması için, türler kendi Finalize yönteminde temel sınıfının Finalize yöntemini çağırmalıdır. - - - - Finalizers should call base class finalizer - Sonlandırıcılar temel sınıf sonlandırıcısını çağırmalıdır - - - - Finalizers should call base class finalizer - Sonlandırıcılar temel sınıf sonlandırıcısını çağırmalıdır - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. İşlem iptali bildirimlerinin doğru yayılmasını sağlamak için 'CancellationToken' parametresini metotlara iletin veya belirtecin kasıtlı olarak yayılmayacağını belirtmek için 'CancellationToken.None' ifadesini açıkça geçirin. @@ -1872,26 +1797,6 @@ {3} '{0}', '{1}' önizleme yöntemini geçersiz kıldığından önizleme özelliklerini kabul etmesi gerekir. Daha fazla bilgi için bkz. {2}. - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - Bu kural her bir parametrenin boyutunu ve bir P/Invoke’un dönüş değerini değerlendirir ve parametre boyutunun 32 bit ve 64 bit işletim sistemlerinde yönetilmeyen kodda sıralandığında doğru olduğunu doğrular. - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - Kodunuzda bildirildiği gibi, P/Invoke {1} öğesinin {0} parametresi {3} platformlarında {2} bayt genişliğinde olacaktır. Bu API’nin gerçek yerel bildirimi {3} platformlarında {4} genişliğinde olması gerektiğini bildirdiğinden, bu doğru değildir. {5} yerine hangi veri türünün kullanılması gerektiğini belirleme hakkında yardım için MSDN Platform SDK’sı belgelerine başvurun. - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - Kodunuzda bildirildiği gibi, P/Invoke {0} öğesinin dönüş türü {2} platformlarında {1} bayt genişliğinde olacaktır. Bu API’nin gerçek yerel bildirimi {2} platformlarında {3} genişliğinde olması gerektiğini bildirdiğinden, bu doğru değildir. {4} yerine hangi veri türünün kullanılması gerektiğini belirleme hakkında yardım için MSDN Platform SDK’sı belgelerine başvurun. - - - - PInvoke declarations should be portable - PInvoke bildirimleri taşınabilir olmalıdır - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. Ortak bir türdeki ortak veya korumalı bir yöntem System.Runtime.InteropServices.DllImportAttribute özniteliğine sahip (ayrıca Visual Basic içinde Declare anahtar sözcüğü tarafından uygulanır). Bu tür yöntemler açığa çıkarılmamalıdır. @@ -2287,21 +2192,6 @@ Sabit değerli dizeyi sabit değerli karakter ile değiştirin - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - Bir özel durum yeniden oluşturulur ve oluşturma bildiriminde özel durum açıkça belirtilir. Bir özel durum oluşturma bildiriminde belirtilerek yeniden oluşturulursa, özel durumu oluşturan özgün yöntem ile geçerli yöntem arasındaki yöntem çağrıları listesi kaybolur. - - - - Rethrow to preserve stack details - Yığın ayrıntılarını korumak için yeniden oluşturun - - - - Rethrow to preserve stack details - Yığın ayrıntılarını korumak için yeniden oluşturun - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. '{1}' metodundaki '{0}' öğesinin '{3}' metodundaki '{2}' öğesinde bulunan kullanıcı denetimindeki veriler nedeniyle zarar görmüş olabileceği bir olası DLL ekleme güvenlik açığı bulundu. @@ -2562,26 +2452,6 @@ Platform çağırma üyeleri kısmen güvenilen çağıranlara izin verir, bir dize parametresine sahiptir ve dizeyi açıkça sıralamaz. Bu olası bir güvenlik açığına neden olabilir. - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - Güvenlik riskini azaltmak için, {1} üzerinde StructLayout.CharSet değerini CharSet.Unicode olarak ayarlayarak ya da alanı belirgin bir şekilde UnmanagedType.LPWStr olarak hazırlayarak {0} alanını Unicode olarak hazırlayın. Bu dizeyi ANSI veya sistem bağımlı olarak sıralamanız gerekirse, en iyi uyan eşlemeyi kapatmak için BestFitMapping özniteliğini kullanın, ve ek güvenlik için ThrowOnUnmappableChar’ın açık olduğundan emin olun. - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - Güvenlik riskini azaltmak için, {1} üzerinde StructLayout.CharSet değerini CharSet.Unicode olarak ayarlayarak ya da alanı belirgin bir şekilde UnmanagedType.LPWStr olarak hazırlayarak {0} alanını Unicode olarak hazırlayın. Bu dizeyi ANSI veya sistem bağımlı olarak sıralamanız gerekirse, MarshalAs’i açıkça belirtin, en iyi uyan eşlemeyi kapatmak için BestFitMapping özniteliğini kullanın, ve ek güvenlik için ThrowOnUnmappableChar’ı açın. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Güvenlik riskini azaltmak için {0} parametresini Unicode olarak sıralamak için DllImport.CharSet'i CharSet.Unicode olarak ayarlayın ya da parametreyi belirgin bir şekilde UnmanagedType.LPWStr olarak sıralayın. Bu dizeyi ANSI ya da sistem bağımlı olarak sıralamanız gerekirse, BestFitMapping=false olarak ayarlayın; ek güvenlik için de ThrowOnUnmappableChar=true olarak ayarlayın. - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - Güvenlik riskini azaltmak için {0} parametresini Unicode olarak sıralamak için DllImport.CharSet'i CharSet.Unicode olarak ayarlayın ya da parametreyi belirgin bir şekilde UnmanagedType.LPWStr olarak sıralayın. Bu dizeyi ANSI ya da sistem bağımlı olarak sıralamanız gerekirse, MarshalAs’i açıkça belirtin, BestFitMapping=false olarak ayarlayın; ek güvenlik için de ThrowOnUnmappableChar=true olarak ayarlayın. - - Specify marshaling for P/Invoke string arguments P/Invoke dize bağımsız değişkenleri için sıralamayı belirtme @@ -2922,16 +2792,6 @@ Dille ilgili olmayan bir dize karşılaştırma işlemi, StringComparison parametresini Ordinal veya OrdinalIgnoreCase olarak ayarlamaz. Parametreyi açıkça StringComparison.Ordinal veya StringComparison.OrdinalIgnoreCase olarak ayarladığınızda kodunuz genellikle hızlanır, daha doğru ve daha güvenilir hale gelir. - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0}, {2} öğesine 'StringComparer' parametresi olarak '{1}' değerini geçiriyor. Dille ilgili olmayan bir karşılaştırma gerçekleştirmek için bunun yerine 'StringComparer.Ordinal' veya 'StringComparer.OrdinalIgnoreCase' değerini belirtin. - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0}, {2} öğesine 'StringComparison' parametresi olarak '{1}' değerini geçiriyor. Dille ilgili olmayan bir karşılaştırma gerçekleştirmek için bunun yerine 'StringComparison.Ordinal' veya 'StringComparison.OrdinalIgnoreCase' değerini belirtin. - - Use ordinal string comparison Sıralı dize karşılaştırması kullanın diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.zh-Hans.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.zh-Hans.xlf index 2fdd5a89ac..a182b8a770 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.zh-Hans.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.zh-Hans.xlf @@ -7,11 +7,6 @@ 将 "NonSerialized" 特性添加到此字段。 - - Add a public constructor that takes zero parameters - 添加采用零参数的公共构造函数 - - Add Serializable attribute 添加 Serializable 特性 @@ -172,11 +167,6 @@ Dispose 方法应调用 SuppressFinalize - - Reliability - 可靠性 - - , , @@ -562,21 +552,6 @@ 反序列化类 {0} 的实例时，方法 {1} 可调用危险方法 {2}。潜在的方法调用为: {3}。 - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - 构造函数调用虚方法时，可能尚未执行调用该方法的实例的构造函数。 - - - - Do not call overridable methods in constructors - 不要在构造函数中调用可重写的方法 - - - - Do not call overridable methods in constructors - 不要在构造函数中调用可重写的方法 - - Do not call {0} on an {1} value 请勿对 {1} 值调用 {0} @@ -587,21 +562,6 @@ 请勿对 ImmutableCollection 值调用 ToImmutableCollection - - Do not author general catch handlers in code that receives corrupted state exceptions. - 不要在接收到损坏状态异常的代码中编写常规捕获处理程序。 - - - - Do not catch corrupted state exceptions in general handlers. - 不要在常规处理程序中捕获损坏状态异常。 - - - - Do not catch corrupted state exceptions in general handlers. - 不要在常规处理程序中捕获损坏状态异常。 - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource 具有采用 TaskCreationOptions 的控制基础任务的构造函数，以及采用任务中存储的对象状态的构造函数。如果意外地传递 TaskContinuationOptions 而不是 TaskCreationOptions，会导致调用将选项视为状态。 @@ -982,16 +942,6 @@ {0} 是不安全的随机数生成器。当需要随机性以确保安全性时，请使用加密的安全随机数生成器。 - - Do not use insecure cryptographic algorithm MD5. - 不要使用不安全的加密算法 MD5。 - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - 此类型实现 MD5，它是一种不安全的加密哈希函数。在计算方面，MD5 和 HMACMD5 算法可能出现哈希冲突。请将此使用项替换为 SHA-2 系列哈希算法(SHA512、SHA384、SHA256)。 - - Do not use obsolete key derivation function 请勿使用已过时的密钥派生功能 @@ -1042,16 +992,6 @@ 不要使用具有值类型的 ReferenceEquals - - Do not use insecure cryptographic algorithm SHA1. - 不要使用不安全的加密算法 SHA1。 - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - 此类型实现 SHA1，它是一种不安全的加密哈希函数。在计算方面，SHA-1 和 SHA-0 算法可能出现哈希冲突。请将此使用项替换为 SHA-2 系列哈希算法(SHA512、SHA384、SHA256)。 - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. Stackalloc 分配的堆栈空间仅在当前方法的调用结束时释放。 在循环中使用它可能会导致无限堆栈增长和最终堆栈溢出条件。 @@ -1247,21 +1187,6 @@ {3}.“{0}”类型包含预览类型“{1}”，因此需要选择加入预览功能。有关详细信息，请参阅 {2}。 - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - 终止必须通过继承层次结构传播。要确保这一点，类型必须从其自身的 Finalize 方法调用它们的基类 Finalize 方法。 - - - - Finalizers should call base class finalizer - 终结器应调用基类的终结器 - - - - Finalizers should call base class finalizer - 终结器应调用基类的终结器 - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. 将 "CancellationToken" 参数转发给方法来确保操作取消通知得到正确传播，或者在 "CancellationToken.None" 中显式传递，以指示有意不传播令牌。 @@ -1872,26 +1797,6 @@ {3}.“{0}”覆盖预览方法“{1}”，因此需要选择加入预览功能。有关详细信息，请参阅 {2}。 - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - 此规则计算每个参数的大小和 P/Invoke 的返回值，并在封送处理为 32 位和 64 位操作系统上的非托管代码时验证参数大小是否正确。 - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - 如代码中所声明的，P/Invoke {1} 的参数 {0} 在 {3} 平台上的字节宽度将为 {2}。这是不正确的，因为此 API 的实际本机声明表明该参数在 {3} 平台上的字节宽度应为 {4}。请参考 MSDN Platform SDK 文档来获取帮助，确定应使用哪种数据类型来代替 {5}。 - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - 如代码中所声明的，P/Invoke {0} 的返回类型在 {2} 平台上的字节宽度将为 {1}。这是不正确的，因为此 API 的实际本机声明表明该返回类型在 {2} 平台上的字节宽度应为 {3}。请参考 MSDN Platform SDK 文档来获取帮助，确定应使用哪种数据类型来代替 {4}。 - - - - PInvoke declarations should be portable - PInvoke 声明应为可移植声明 - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. 公共类型中的公共方法或受保护的方法具有 System.Runtime.InteropServices.DllImportAttribute 属性(在 Visual Basic 中也由 Declare 关键字实现)。不应公开此类方法。 @@ -2287,21 +2192,6 @@ 将字符串字面量替换为字符型文本 - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - 异常被再次引发并在 throw 语句中显式指定。如果通过在 throw 语句中指定异常来重新引发异常，则引发该异常的原始方法与当前方法之间的方法调用列表将丢失。 - - - - Rethrow to preserve stack details - 再次引发以保留堆栈详细信息 - - - - Rethrow to preserve stack details - 再次引发以保留堆栈详细信息 - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. 找到了潜在的 DLL 注入漏洞，其中方法“{1}”中的“{0}”可能会受到方法“{3}”中“{2}”的用户控制数据的污染。 @@ -2562,26 +2452,6 @@ 平台调用成员允许部分受信任的调用方，具有字符串参数，且不显式封送字符串。这可能导致潜在的安全漏洞。 - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - 为了降低安全风险，请将字段 {0} 封送为 Unicode，方法是将 {1} 上的 StructLayout.CharSet 设置为 CharSet.Unicode，或者将该字段显式封送为 UnmanagedType.LPWStr。如果需要将该字符串封送为 ANSI 或者与系统相关的编码，请使用 BestFitMapping 属性来禁用最佳匹配映射。另外，为了提高安全性，请确保启用 ThrowOnUnmappableChar。 - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - 为了降低安全风险，请将字段 {0} 封送为 Unicode，方法是将 {1} 上的 StructLayout.CharSet 设置为 CharSet.Unicode，或者将该字段显式封送为 UnmanagedType.LPWStr。如果需要将该字符串封送为 ANSI 或者与系统相关的编码，请显式指定 MarshalAs，并使用 BestFitMapping 属性来禁用最佳匹配映射；为了提高安全性，启用 ThrowOnUnmappableChar。 - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - 为了降低安全风险，请将参数 {0} 封送为 Unicode，方法是将 DllImport.CharSet 设置为 CharSet.Unicode 或者将该参数显式封送为 UnmanagedType.LPWStr。如果你需要将该字符串封送为 ANSI 或与系统相关的编码，请设置 BestFitMapping=false；为了提高安全性，还可以设置 ThrowOnUnmappableChar=true。 - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - 为了降低安全风险，请将参数 {0} 封送为 Unicode，方法是将 DllImport.CharSet 设置为 CharSet.Unicode 或者将该参数显式封送为 UnmanagedType.LPWStr。如果需要将该字符串封送为 ANSI 或者与系统相关的编码，请显式指定 MarshalAs，并设置 BestFitMapping=false；为了提高安全性，还应设置 ThrowOnUnmappableChar=true。 - - Specify marshaling for P/Invoke string arguments 指定对 P/Invoke 字符串参数进行封送处理 @@ -2922,16 +2792,6 @@ 非语义的字符串比较运算没有将 StringComparison 参数设置为 Ordinal 或 OrdinalIgnoreCase。通过将参数显式设置为 StringComparison.Ordinal 或 StringComparison.OrdinalIgnoreCase，通常可提高代码的速度、准确率和可靠性。 - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0} 将“{1}”作为 "StringComparer" 参数传递给 {2}。若要执行非语义比较，请改为指定 "StringComparer.Ordinal" 或 "StringComparer.OrdinalIgnoreCase"。 - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0} 将“{1}”作为 "StringComparison" 参数传递给 {2}。若要执行非语义比较，请改为指定 "StringComparison.Ordinal" 或 "StringComparison.OrdinalIgnoreCase"。 - - Use ordinal string comparison 使用序数字符串比较 diff --git a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.zh-Hant.xlf b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.zh-Hant.xlf index c780e85b4b..57b194f305 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.zh-Hant.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.zh-Hant.xlf @@ -7,11 +7,6 @@ 將 'NonSerialized' 屬性新增至此欄位。 - - Add a public constructor that takes zero parameters - 新增接受零個參數的公用建構函式 - - Add Serializable attribute 新增可序列化屬性 @@ -172,11 +167,6 @@ Dispose 方法應該呼叫 SuppressFinalize - - Reliability - 可靠性 - - , , @@ -562,21 +552,6 @@ 將類別 {0} 的執行個體還原序列化時，方法 {1} 可以呼叫危險的方法 {2}。潛在的方法引動過程為: {3}。 - - When a constructor calls a virtual method, the constructor for the instance that invokes the method may not have executed. - 當建構函式呼叫虛擬方法時，可能尚未執行叫用方法之執行個體的建構函式。 - - - - Do not call overridable methods in constructors - 請勿呼叫建構函式中的可覆寫方法 - - - - Do not call overridable methods in constructors - 請勿呼叫建構函式中的可覆寫方法 - - Do not call {0} on an {1} value 請勿對 {1} 值呼叫 {0} @@ -587,21 +562,6 @@ 請勿對 ImmutableCollection 值呼叫 TolmmutableCollection - - Do not author general catch handlers in code that receives corrupted state exceptions. - 請勿在接收損毀狀態例外狀況的程式碼中，撰寫一般的 catch 處理常式。 - - - - Do not catch corrupted state exceptions in general handlers. - 請勿在一般處理常式中擷取損毀狀態例外狀況。 - - - - Do not catch corrupted state exceptions in general handlers. - 請勿在一般處理常式中擷取損毀狀態例外狀況。 - - TaskCompletionSource has constructors that take TaskCreationOptions that control the underlying Task, and constructors that take object state that's stored in the task. Accidentally passing a TaskContinuationOptions instead of a TaskCreationOptions will result in the call treating the options as state. TaskCompletionSource 有建構函式會採用控制基礎工作的 TaskCreationOptions，也有會採用儲存在工作內物件狀態的建構函式。不小心傳遞了 TaskContinuationOptions 而非 TaskCreationOptions 時，會導致呼叫將選項視為狀態。 @@ -982,16 +942,6 @@ {0} 是不安全的亂數產生器。當安全性需要隨機性時，請使用密碼編譯安全性亂數產生器。 - - Do not use insecure cryptographic algorithm MD5. - 請勿使用不安全的密碼編譯演算法 MD5。 - - - - This type implements MD5, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the MD5 and HMACMD5 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - 此類型會實作 MD5，此雜湊函數在密碼編譯方面有安全性疑慮。MD5 與 HMACMD5 演算法在運算方面可能會發生雜湊衝突。請以 SHA-2 系列雜湊演算法 (SHA512、SHA384、SHA256) 取代此用法。 - - Do not use obsolete key derivation function 請勿使用已淘汰的金鑰衍生函數 @@ -1042,16 +992,6 @@ 請勿使用有實值型別的 ReferenceEquals - - Do not use insecure cryptographic algorithm SHA1. - 請勿使用不安全的密碼編譯演算法 SHA1。 - - - - This type implements SHA1, a cryptographically insecure hashing function. Hash collisions are computationally feasible for the SHA-1 and SHA-0 algorithms. Replace this usage with a SHA-2 family hash algorithm (SHA512, SHA384, SHA256). - 此類型會實作 SHA1，此雜湊函數在密碼編譯方面有安全性疑慮。SHA-1 與 SHA-0 演算法在運算方面可能會發生雜湊衝突。請以 SHA-2 系列雜湊演算法 (SHA512、SHA384、SHA256) 取代此用法。 - - Stack space allocated by a stackalloc is only released at the end of the current method's invocation. Using it in a loop can result in unbounded stack growth and eventual stack overflow conditions. stackalloc 配置的堆疊空間只會在目前方法的引動過程結束時釋出。在迴圈中使用該空間可能會造成堆疊無限增長，最終導致堆疊溢位。 @@ -1247,21 +1187,6 @@ {3} '{0}' 的類型包含預覽類型 '{1}'，因此必須加入預覽功能。如需詳細資訊，請參閱 {2}。 - - Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method. - 完成項必須傳播到整個繼承階層。為確保上述作業，類型必須呼叫其本身 Finalize 方法中的基底類別 Finalize 方法。 - - - - Finalizers should call base class finalizer - 完成項應呼叫基底類別完成項 - - - - Finalizers should call base class finalizer - 完成項應呼叫基底類別完成項 - - Forward the 'CancellationToken' parameter to methods to ensure the operation cancellation notifications gets properly propagated, or pass in 'CancellationToken.None' explicitly to indicate intentionally not propagating the token. 將 'CancellationToken' 參數轉送給方法，以確保作業取消通知能正確地散佈，或明確地傳入 'CancellationToken.None'，以表示刻意不散佈權杖。 @@ -1872,26 +1797,6 @@ {3} '{0}' 會覆寫預覽方法 '{1}'，因此必須加入預覽功能。如需詳細資訊，請參閱 {2}。 - - This rule evaluates the size of each parameter and the return value of a P/Invoke, and verifies that the size of the parameter is correct when marshaled to unmanaged code on 32-bit and 64-bit operating systems. - 此規則會評估 P/Invoke 每個參數的大小以及傳回值，並會在參數於 32 位元和 64 位元作業系統上封送處理成非受控程式碼時，驗證其大小是否正確。 - - - - As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, as the actual native declaration of this API indicates it should be {4} bytes wide on {3} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {5}. - 因為其宣告於您的程式碼中，所以 P/Invoke {1} 的參數 {0} 在 {3} 平台上將會是 {2} 個位元組寬。但這是錯誤的，因為此 API 的實際原生宣告指出，其在 {3} 平台上應為 {4} 個位元組寬。請參閱 MSDN Platform SDK 文件中的說明，決定應使用何種資料類型來取代 {5}。 - - - - As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, as the actual native declaration of this API indicates it should be {3} bytes wide on {2} platforms. Consult the MSDN Platform SDK documentation for help determining what data type should be used instead of {4}. - 因為其宣告於您的程式碼中，因此 P/Invoke {0} 的傳回型別在 {2} 平台上將會是 {1} 個位元組寬。但這是錯誤的，因為此 API 的實際原生宣告指出，其在 {2} 平台上應為 {3} 個位元組寬。請參閱 MSDN Platform SDK 文件中的說明，決定應使用何種資料類型來取代 {4}。 - - - - PInvoke declarations should be portable - PInvoke 宣告應可攜 - - A public or protected method in a public type has the System.Runtime.InteropServices.DllImportAttribute attribute (also implemented by the Declare keyword in Visual Basic). Such methods should not be exposed. 公用類型中的公用方法或受保護方法，具有 System.Runtime.InteropServices.DllImportAttribute 屬性 (也由 Visual Basic 中的 Declare 關鍵字實作)。這類方法不應公開。 @@ -2287,21 +2192,6 @@ 以字元常值取代字串常值 - - An exception is rethrown and the exception is explicitly specified in the throw statement. If an exception is rethrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost. - 會再次擲回例外狀況，並在 throw 陳述式中明確指定該例外狀況。如果在 throw 陳述式中指定例外狀況，而再次擲回了例外狀況，則方法清單會呼叫之前擲回例外狀況的原始方法，而目前的方法則會遺失。 - - - - Rethrow to preserve stack details - 重新擲回以保存堆疊詳細資料 - - - - Rethrow to preserve stack details - 重新擲回以保存堆疊詳細資料 - - Potential DLL injection vulnerability was found where '{0}' in method '{1}' may be tainted by user-controlled data from '{2}' in method '{3}'. 發現潛在的插入 DLL 弱點，方法 '{1}' 中的 '{0}' 可能被來自方法 '{3}' 中 '{2}' 由使用者控制的資料所感染。 @@ -2562,26 +2452,6 @@ 平台叫用成員允許部分信任的呼叫端、具有字串參數，且不會明確地封送處理字串。如此可能會造成資訊安全漏洞。 - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, ensure ThrowOnUnmappableChar is on. - 為降低安全性風險，請將欄位 {0} 封送處理為 Unicode，方法是將 {1} 上的 StructLayout.CharSet 設為 CharSet.Unicode，或將該欄位明確封送處理為 UnmanagedType.LPWStr。如果需要將此字串封送處理為 ANSI 或與系統相依，請使用 BestFitMapping 屬性關閉自動調整對應，此外為增加安全性，請確認已開啟 ThrowOnUnmappableChar。 - - - - To reduce security risk, marshal field {0} as Unicode, by setting StructLayout.CharSet on {1} to CharSet.Unicode, or by explicitly marshaling the field as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, use the BestFitMapping attribute to turn best-fit mapping off, and for added security, to turn ThrowOnUnmappableChar on. - 為降低安全性風險，請將欄位 {0} 封送處理為 Unicode，方法是將 {1} 上的 StructLayout.CharSet 設為 CharSet.Unicode，或將該欄位明確封送處理為 UnmanagedType.LPWStr。如果需要將此字串封送處理為 ANSI 或與系統相依，可明確地指定 MarshalAs 並使用 BestFitMapping 屬性關閉自動調整對應，此外為增加安全性，請將 ThrowOnUnmappableChar 開啟。 - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - 為降低安全性風險，請將參數 {0} 封送處理為 Unicode，方法是將 DllImport.CharSet 設為 CharSet.Unicode，或將該參數明確封送處理為 UnmanagedType.LPWStr。如果需要將此字串封送處理為 ANSI 或與系統相依，可以設定 BestFitMapping=false; 此外為增加安全性，也可設定 ThrowOnUnmappableChar=true。 - - - - To reduce security risk, marshal parameter {0} as Unicode, by setting DllImport.CharSet to CharSet.Unicode, or by explicitly marshaling the parameter as UnmanagedType.LPWStr. If you need to marshal this string as ANSI or system-dependent, specify MarshalAs explicitly, and set BestFitMapping=false; for added security, also set ThrowOnUnmappableChar=true. - 為降低安全性風險，請將參數 {0} 封送處理為 Unicode，方法是將 DllImport.CharSet 設為 CharSet.Unicode，或將該參數明確封送處理為 UnmanagedType.LPWStr。如果需要將此字串封送處理為 ANSI 或與系統相依，可明確地指定 MarshalAs 並設定 BestFitMapping=false; 此外為增加安全性，也可設定 ThrowOnUnmappableChar=true。 - - Specify marshaling for P/Invoke string arguments 指定 P/Invoke 字串引數的封送處理 @@ -2922,16 +2792,6 @@ 非語言的字串比較作業不會將 StringComparison 參數設為 Ordinal 或 OrdinalIgnoreCase。將參數明確設定為 StringComparison.Ordinal 或 StringComparison.OrdinalIgnoreCase 時，程式碼通常會更快速、精確且更可靠。 - - {0} passes '{1}' as the 'StringComparer' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparer.Ordinal' or 'StringComparer.OrdinalIgnoreCase' instead. - {0} 會以 'StringComparison' 參數形式將 '{1}' 傳遞給 {2}。若要執行非語言比較，請改為指定 'StringComparer.Ordinal' 或 'StringComparer.OrdinalIgnoreCase'。 - - - - {0} passes '{1}' as the 'StringComparison' parameter to {2}. To perform a non-linguistic comparison, specify 'StringComparison.Ordinal' or 'StringComparison.OrdinalIgnoreCase' instead. - {0} 會以 'StringComparison' 參數形式將 '{1}' 傳遞給 {2}。若要執行非語言比較，請改為指定 'StringComparison.Ordinal' 或 'StringComparison.OrdinalIgnoreCase'。 - - Use ordinal string comparison 使用序數字串比較 diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/MicrosoftNetFrameworkAnalyzersResources.resx b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/MicrosoftNetFrameworkAnalyzersResources.resx index 88c939c932..76a736dbb2 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/MicrosoftNetFrameworkAnalyzersResources.resx +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/MicrosoftNetFrameworkAnalyzersResources.resx @@ -153,51 +153,6 @@ Call base class methods on ISerializable types - - Use XmlReader for DataSet ReadXml - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - - - Use XmlReader for DataSet ReadXml - - - Use XmlReader for DataSet ReadXmlSchema - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - - - Use XmlReader for DataSet ReadXmlSchema - - - Review DataView CollectionString - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - - - Review DataView CollectionString - - - Use XmlReader for DataTable ReadXml - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - - - Use XmlReader for DataTable ReadXml - - - Use XmlReader for DataTable ReadXmlSchema - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - - - Use XmlReader for DataTable ReadXmlSchema - Do Not Catch Corrupted State Exceptions @@ -245,10 +200,6 @@ Unsafe overload of '{0}' method CA3075 - - Insecure DTD Processing - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. CA3075 diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.cs.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.cs.xlf index 07dbfad1ec..2f0a1bb655 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.cs.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.cs.xlf @@ -62,81 +62,6 @@ Zavolejte metody základních tříd pro typy ISerializable - - Use XmlReader for DataSet ReadXml - Pro DataSet ReadXml použijte XmlReader - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Nepoužívejte nebezpečná přetížení metody System.Data.DataSet.ReadXml. Toto rozhraní API umožňuje zpracovávat DTD v instanci používané čtečky XML a pomocí UrlResolveru překládá externí entity XML. Výsledkem je odhalení informací. Obsah systému souborů nebo sdílených síťových složek počítače, který zpracovává kód XML, může zjistit útočník. Kromě toho může toto útočník využít jako místo pro útok DoS. - - - - Use XmlReader for DataSet ReadXml - Pro DataSet ReadXml použijte XmlReader - - - - Use XmlReader for DataSet ReadXmlSchema - Pro DataSet ReadXmlSchema použijte XmlReader - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Nepoužívejte nebezpečná přetížení metody System.Data.DataSet.ReadXmlSchema. Toto rozhraní API umožňuje zpracovávat DTD v instanci používané čtečky XML a pomocí UrlResolveru překládá externí entity XML. Výsledkem je odhalení informací. Obsah systému souborů nebo sdílených síťových složek počítače, který zpracovává kód XML, může zjistit útočník. Kromě toho může toto útočník využít jako místo pro útok DoS. - - - - Use XmlReader for DataSet ReadXmlSchema - Pro DataSet ReadXmlSchema použijte XmlReader - - - - Review DataView CollectionString - Zkontrolujte DataView CollectionString - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Zkontrolujte kód a ujistěte se, že vstup System.Data.DataViewManager.DataViewSettingCollectionString se upravil tak, aby neobsahoval DTD. Když se ve čtečce XML povolí zpracování DTD a k překladu externích entit XML se použije UrlResolver, může dojít k odhalení informací. Obsah systému souborů nebo sdílených síťových složek počítače, který zpracovává kód XML, může zjistit útočník. Kromě toho může toto útočník využít jako místo pro útok DoS. - - - - Review DataView CollectionString - Zkontrolujte DataView CollectionString - - - - Use XmlReader for DataTable ReadXml - Pro DataTable ReadXml použijte XmlReader - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Nepoužívejte nebezpečná přetížení metody System.Data.DataTable.ReadXml. Toto rozhraní API umožňuje zpracovávat DTD v instanci používané čtečky XML a pomocí UrlResolveru překládá externí entity XML. Výsledkem je odhalení informací. Obsah systému souborů nebo sdílených síťových složek počítače, který zpracovává kód XML, může zjistit útočník. Kromě toho může toto útočník využít jako místo pro útok DoS. - - - - Use XmlReader for DataTable ReadXml - Pro DataTable ReadXml použijte XmlReader - - - - Use XmlReader for DataTable ReadXmlSchema - Pro DataTable ReadXmlSchema použijte XmlReader - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Zkontroluje, jestli se nepoužilo nebezpečné přetížení metody System.Data.DataTable.ReadXmlSchema. Toto rozhraní API umožňuje zpracovávat DTD v instanci používané čtečky XML a pomocí UrlResolveru překládá externí entity XML. Výsledkem je odhalení informací. Obsah systému souborů nebo sdílených síťových složek počítače, který zpracovává kód XML, může zjistit útočník. Kromě toho může toto útočník využít jako místo pro útok DoS. - - - - Use XmlReader for DataTable ReadXmlSchema - Pro DataTable ReadXmlSchema použijte XmlReader - - Do Not Catch Corrupted State Exceptions Nezachytávejte výjimky poškozující stav procesu @@ -212,11 +137,6 @@ Nebezpečné přetížení metody {0} CA3075 - - Insecure DTD Processing - Nezabezpečené zpracování DTD - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. Používá nebezpečnou metodu setter vlastnosti InnerXml třídy System.Xml.XmlDocument. diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.de.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.de.xlf index d4e0d4e0d7..977cddcc25 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.de.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.de.xlf @@ -62,81 +62,6 @@ Basisklassenmethoden bei ISerializable-Typen aufrufen - - Use XmlReader for DataSet ReadXml - XmlReader für DataSet ReadXml verwenden - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Verwenden Sie keine unsicheren Überladungen von "System.Data.DataSet.ReadXml". Diese API aktiviert intern die DTD-Verarbeitung für die verwendete XML-Readerinstanz und verwendet den UrlResolver zum Auflösen externer XML-Entitäten. Das Ergebnis ist die Veröffentlichung von Informationen. Inhalte aus dem Dateisystem oder aus Netzwerkfreigaben für den Computer, auf dem das XML verarbeitet wird, können einem Angreifer verfügbar gemacht werden. Außerdem kann ein Angreifer dies als DoS-Vektor verwenden. - - - - Use XmlReader for DataSet ReadXml - XmlReader für DataSet ReadXml verwenden - - - - Use XmlReader for DataSet ReadXmlSchema - XmlReader für DataSet ReadXmlSchema verwenden - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Verwenden Sie keine unsicheren Überladungen von "System.Data.DataSet.ReadXmlSchema". Diese API aktiviert intern die DTD-Verarbeitung für die verwendete XML-Readerinstanz und verwendet den UrlResolver zum Auflösen externer XML-Entitäten. Das Ergebnis ist die Veröffentlichung von Informationen. Inhalte aus dem Dateisystem oder aus Netzwerkfreigaben für den Computer, auf dem das XML verarbeitet wird, können einem Angreifer verfügbar gemacht werden. Außerdem kann ein Angreifer dies als DoS-Vektor verwenden. - - - - Use XmlReader for DataSet ReadXmlSchema - XmlReader für DataSet ReadXmlSchema verwenden - - - - Review DataView CollectionString - DataView CollectionString prüfen - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Prüfen Sie den Code, um sicherzustellen, dass die Syntax der Eingabe für "System.Data.DataViewManager.DataViewSettingCollectionString" so bereinigt wurde, dass keine DTD enthalten ist. Das Aktivieren der DTD´-Verarbeitung im XML-Reader und die Verwendung von UrlResolver zum Auflösen externer XML-Entitäten können zur Veröffentlichung von Informationen führen. Inhalte aus dem Dateisystem oder aus Netzwerkfreigaben für den Computer, auf dem das XML verarbeitet wird, können einem Angreifer verfügbar gemacht werden. Außerdem kann ein Angreifer dies als DoS-Vektor verwenden. - - - - Review DataView CollectionString - DataView CollectionString prüfen - - - - Use XmlReader for DataTable ReadXml - XmlReader für DataTable ReadXml verwenden - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Verwenden Sie keine unsicheren Überladungen von "System.Data.DataTable.ReadXml". Diese API aktiviert intern die DTD-Verarbeitung für die verwendete XML-Readerinstanz und verwendet den UrlResolver zum Auflösen externer XML-Entitäten. Das Ergebnis ist die Veröffentlichung von Informationen. Inhalte aus dem Dateisystem oder aus Netzwerkfreigaben für den Computer, auf dem das XML verarbeitet wird, können einem Angreifer verfügbar gemacht werden. Außerdem kann ein Angreifer dies als DoS-Vektor verwenden. - - - - Use XmlReader for DataTable ReadXml - XmlReader für DataTable ReadXml verwenden - - - - Use XmlReader for DataTable ReadXmlSchema - XmlReader für DataTable ReadXmlSchema verwenden - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Prüft auf die Nutzung einer unsicheren Überladung von "System.Data.DataTable.ReadXmlSchema". Diese API aktiviert intern die DTD-Verarbeitung für die verwendete XML-Readerinstanz und verwendet den UrlResolver zum Auflösen externer XML-Entitäten. Das Ergebnis ist die Veröffentlichung von Informationen. Inhalte aus dem Dateisystem oder aus Netzwerkfreigaben für den Computer, auf dem das XML verarbeitet wird, können einem Angreifer verfügbar gemacht werden. Außerdem kann ein Angreifer dies als DoS-Vektor verwenden. - - - - Use XmlReader for DataTable ReadXmlSchema - XmlReader für DataTable ReadXmlSchema verwenden - - Do Not Catch Corrupted State Exceptions Keine Corrupted State Exceptions abfangen @@ -212,11 +137,6 @@ Unsichere Überladung der Methode "{0}" CA3075 - - Insecure DTD Processing - Unsichere DTD-Verarbeitung - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. Verwendet den unsicheren Setter der InnerXml-Eigenschaft von "System.Xml.XmlDocument". diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.es.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.es.xlf index 1de91b3c17..6a4a97c9c5 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.es.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.es.xlf @@ -62,81 +62,6 @@ Llamar a métodos de clase base en tipos ISerializable - - Use XmlReader for DataSet ReadXml - Usar XmlReader para DataSet ReadXml - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - No utilice sobrecargas no seguras de System.Data.DataSet.ReadXml. Esta API habilita internamente el procesado de DTD en la instancia utilizada del lector XML, y utiliza UrlResolver para resolver entidades XML externas. El resultado es la revelación de información. El contenido del sistema de archivos o los recursos compartidos de red de la máquina que procesa el XML pueden resultar expuestos al atacante. Además, un atacante puede usar esto como vector de denegación de servicio. - - - - Use XmlReader for DataSet ReadXml - Usar XmlReader para DataSet ReadXml - - - - Use XmlReader for DataSet ReadXmlSchema - Usar XmlReader para DataSet ReadXmlSchema - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - No utilice sobrecargas no seguras de System.Data.DataSet.ReadXmlSchema. Esta API habilita internamente el procesado de DTD en la instancia utilizada del lector XML, y utiliza UrlResolver para resolver entidades XML externas. El resultado es la revelación de información. El contenido del sistema de archivos o los recursos compartidos de red de la máquina que procesa el XML pueden resultar expuestos al atacante. Además, un atacante puede usar esto como vector de denegación de servicio. - - - - Use XmlReader for DataSet ReadXmlSchema - Usar XmlReader para DataSet ReadXmlSchema - - - - Review DataView CollectionString - Revisar DataView CollectionString - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Revise el código para asegurarse de que el uso de la entrada de System.Data.DataViewManager.DataViewSettingCollectionString está saneada para no contener DTD. La habilitación del procesamiento de DTD en el lector XML y el uso de UrlResolver para resolver las entidades XML externas puede provocar una revelación de información. El contenido del sistema de archivos o los recursos compartidos de red de la máquina que procesa el XML pueden resultar expuestos al atacante. Además, un atacante puede usar esto como vector de denegación de servicio. - - - - Review DataView CollectionString - Revisar DataView CollectionString - - - - Use XmlReader for DataTable ReadXml - Usar XmlReader para DataTable ReadXml - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - No utilice sobrecargas no seguras de System.Data.DataTable.ReadXml. Esta API habilita internamente el procesado de DTD en la instancia utilizada del lector XML, y utiliza UrlResolver para resolver entidades XML externas. El resultado es la revelación de información. El contenido del sistema de archivos o los recursos compartidos de red de la máquina que procesa el XML pueden resultar expuestos al atacante. Además, un atacante puede usar esto como vector de denegación de servicio. - - - - Use XmlReader for DataTable ReadXml - Usar XmlReader para DataTable ReadXml - - - - Use XmlReader for DataTable ReadXmlSchema - Usar XmlReader para DataTable ReadXmlSchema - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Comprobaciones para el uso de una sobrecarga no segura de System.Data.DataTable.ReadXmlSchema. Esta API habilita internamente el procesado de DTD en la instancia utilizada del lector XML, y utiliza UrlResolver para resolver entidades XML externas. El resultado es la revelación de información. El contenido del sistema de archivos o los recursos compartidos de red de la máquina que procesa el XML pueden resultar expuestos al atacante. Además, un atacante puede usar esto como vector de denegación de servicio. - - - - Use XmlReader for DataTable ReadXmlSchema - Usar XmlReader para DataTable ReadXmlSchema - - Do Not Catch Corrupted State Exceptions No tomar excepciones de estado dañado @@ -212,11 +137,6 @@ Sobrecarga no segura del método "{0}" CA3075 - - Insecure DTD Processing - Procesamiento de DTD no seguro - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. Usa el establecedor no seguro de la propiedad InnerXml de System.Xml.XmlDocument. diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.fr.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.fr.xlf index 614a0c5730..a676b4de11 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.fr.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.fr.xlf @@ -62,81 +62,6 @@ Appeler les méthodes de classe de base sur les types ISerializable - - Use XmlReader for DataSet ReadXml - Utiliser XmlReader pour le ReadXml de DataSet - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Ne pas utiliser de surcharges unsafe de System.Data.DataSet.ReadXml. Cette API active de manière interne le traitement DTD sur l'instance de lecteur XML utilisée, puis utilise UrlResolver pour résoudre les entités XML externes. Il en résulte une divulgation d'informations. Le contenu du système de fichiers ou des partages réseau de la machine qui traite le code XML peut être exposé à des attaques de pirates. En outre, un pirate peut l'utiliser comme vecteur d'attaque DoS. - - - - Use XmlReader for DataSet ReadXml - Utiliser XmlReader pour le ReadXml de DataSet - - - - Use XmlReader for DataSet ReadXmlSchema - Utiliser XmlReader pour le ReadXmlSchema de DataSet - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Ne pas utiliser de surcharges unsafe de System.Data.DataSet.ReadXmlSchema. Cette API active de manière interne le traitement DTD sur l'instance de lecteur XML utilisée, puis utilise UrlResolver pour résoudre les entités XML externes. Il en résulte une divulgation d'informations. Le contenu du système de fichiers ou des partages réseau de la machine qui traite le code XML peut être exposé à des attaques de pirates. En outre, un pirate peut l'utiliser comme vecteur d'attaque DoS. - - - - Use XmlReader for DataSet ReadXmlSchema - Utiliser XmlReader pour le ReadXmlSchema de DataSet - - - - Review DataView CollectionString - Passer en revue le CollectionString de DataView - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Passer en revue le code pour vérifier que l'utilisation de l'entrée de System.Data.DataViewManager.DataViewSettingCollectionString ne contient aucun DTD. L'activation du traitement DTD sur le lecteur XML et l'utilisation de UrlResolver pour résoudre les entités XML externes peuvent entraîner une divulgation d'informations. Le contenu du système de fichiers ou des partages réseau de la machine qui traite le code XML peut être exposé à des attaques de pirates. En outre, un pirate peut l'utiliser comme vecteur d'attaque DoS. - - - - Review DataView CollectionString - Passer en revue le CollectionString de DataView - - - - Use XmlReader for DataTable ReadXml - Utiliser XmlReader pour le ReadXml de DataTable - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Ne pas utiliser de surcharges unsafe de System.Data.DataTable.ReadXml. Cette API active de manière interne le traitement DTD sur l'instance de lecteur XML utilisée, puis utilise UrlResolver pour résoudre les entités XML externes. Il en résulte une divulgation d'informations. Le contenu du système de fichiers ou des partages réseau de la machine qui traite le code XML peut être exposé à des attaques de pirates. En outre, un pirate peut l'utiliser comme vecteur d'attaque DoS. - - - - Use XmlReader for DataTable ReadXml - Utiliser XmlReader pour le ReadXml de DataTable - - - - Use XmlReader for DataTable ReadXmlSchema - Utiliser XmlReader pour le ReadXmlSchema de DataTable - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Vérifie si une surcharge unsafe de System.Data.DataTable.ReadXmlSchema est utilisée. Cette API active de manière interne le traitement DTD sur l'instance de lecteur XML utilisée, puis utilise UrlResolver pour résoudre les entités XML externes. Il en résulte une divulgation d'informations. Le contenu du système de fichiers ou des partages réseau de la machine qui traite le code XML peut être exposé à des attaques de pirates. En outre, un pirate peut l'utiliser comme vecteur d'attaque DoS. - - - - Use XmlReader for DataTable ReadXmlSchema - Utiliser XmlReader pour le ReadXmlSchema de DataTable - - Do Not Catch Corrupted State Exceptions Ne pas intercepter les exceptions état altéré @@ -212,11 +137,6 @@ Surcharge unsafe de la méthode '{0}' CA3075 - - Insecure DTD Processing - Traitement DTD non sécurisé - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. Utilise la méthode setter unsafe de la propriété InnerXml de System.Xml.XmlDocument. diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.it.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.it.xlf index 2d0d473963..45e23c8ae3 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.it.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.it.xlf @@ -62,81 +62,6 @@ Chiamare metodi della classe di base su tipi ISerializable - - Use XmlReader for DataSet ReadXml - Usare XmlReader per ReadXml di DataSet - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Non usare overload non sicuri di System.Data.DataSet.ReadXml. Questa API abilita internamente l'elaborazione della DTD sull'istanza usata del lettore XML e usa UrlResolver per risolvere le entità XML esterne. Il risultato implica la diffusione di informazioni. Il contenuto di file system o condivisioni di rete per il computer che elabora il codice XML può essere esposto a utenti malintenzionati. Un utente malintenzionato può inoltre usarlo come vettore DoS. - - - - Use XmlReader for DataSet ReadXml - Usare XmlReader per ReadXml di DataSet - - - - Use XmlReader for DataSet ReadXmlSchema - Usare XmlReader per ReadXmlSchema di DataSet - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Non usare overload non sicuri di System.Data.DataSet.ReadXmlSchema. Questa API abilita internamente l'elaborazione della DTD sull'istanza usata del lettore XML e usa UrlResolver per risolvere le entità XML esterne. Il risultato implica la diffusione di informazioni. Il contenuto di file system o condivisioni di rete per il computer che elabora il codice XML può essere esposto a utenti malintenzionati. Un utente malintenzionato può inoltre usarlo come vettore DoS. - - - - Use XmlReader for DataSet ReadXmlSchema - Usare XmlReader per ReadXmlSchema di DataSet - - - - Review DataView CollectionString - Esaminare DataView CollectionString - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Esaminare il codice per assicurarsi che l'utilizzo dell'input di System.Data.DataViewManager.DataViewSettingCollectionString sia stato bonificato in modo da non contenere DTD. L'abilitazione dell'elaborazione DTD sul lettore XML e l'uso di UrlResolver per risolvere entità XML esterne potrebbero causare la diffusione di informazioni. Il contenuto di file system o condivisioni di rete per il computer che elabora il codice XML può essere esposto a utenti malintenzionati. Un utente malintenzionato può inoltre usarlo come vettore DoS. - - - - Review DataView CollectionString - Esaminare DataView CollectionString - - - - Use XmlReader for DataTable ReadXml - Usare XmlReader per ReadXml di DataTable - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Non usare overload non sicuri di System.Data.DataTable.ReadXml. Questa API abilita internamente l'elaborazione della DTD sull'istanza usata del lettore XML e usa UrlResolver per risolvere le entità XML esterne. Il risultato implica la diffusione di informazioni. Il contenuto di file system o condivisioni di rete per il computer che elabora il codice XML può essere esposto a utenti malintenzionati. Un utente malintenzionato può inoltre usarlo come vettore DoS. - - - - Use XmlReader for DataTable ReadXml - Usare XmlReader per ReadXml di DataTable - - - - Use XmlReader for DataTable ReadXmlSchema - Usare XmlReader per ReadXmlSchema di DataTable - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Verifica se è stato usato un overload non sicuro di System.Data.DataTable.ReadXmlSchema. Questa API abilita internamente l'elaborazione della DTD sull'istanza usata del lettore XML e usa UrlResolver per risolvere le entità XML esterne. Il risultato implica la diffusione di informazioni. Il contenuto di file system o condivisioni di rete per il computer che elabora il codice XML può essere esposto a utenti malintenzionati. Un utente malintenzionato può inoltre usarlo come vettore DoS. - - - - Use XmlReader for DataTable ReadXmlSchema - Usare XmlReader per ReadXmlSchema di DataTable - - Do Not Catch Corrupted State Exceptions Non rilevare eccezioni di stato danneggiato @@ -212,11 +137,6 @@ Overload non sicuro del metodo '{0}' CA3075 - - Insecure DTD Processing - Elaborazione DTD non sicura - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. Usa il setter non sicuro della proprietà InnerXml di System.Xml.XmlDocument. diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ja.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ja.xlf index c7dc27b60c..83e3c65e19 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ja.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ja.xlf @@ -62,81 +62,6 @@ ISerializable 型で基底クラス メソッドを呼び出します - - Use XmlReader for DataSet ReadXml - DataSet ReadXml に XmlReader を使用します - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - System.Data.DataSet.ReadXml の安全でないオーバーロードを使用しないでください。この API により、使用されている XML リーダー インスタンスでの DTD 処理が内部で有効になり、外部 XML エンティティの解決に UrlResolver が使用されます。その結果は情報漏えいです。XML を処理しているコンピューターのファイル システムまたはネットワーク共有のコンテンツは、攻撃者にさらされる可能性があります。また、攻撃者はこれを DoS ベクトルとして使用する可能性があります。 - - - - Use XmlReader for DataSet ReadXml - DataSet ReadXml に XmlReader を使用します - - - - Use XmlReader for DataSet ReadXmlSchema - DataSet ReadXmlSchema に XmlReader を使用します - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - System.Data.DataSet.ReadXmlSchema の安全でないオーバーロードを使用しないでください。この API により、使用されている XML リーダー インスタンスでの DTD 処理が内部で有効になり、外部 XML エンティティの解決に UrlResolver が使用されます。その結果は情報漏えいです。XML を処理しているコンピューターのファイル システムまたはネットワーク共有のコンテンツは、攻撃者にさらされる可能性があります。また、攻撃者はこれを DoS ベクトルとして使用する可能性があります。 - - - - Use XmlReader for DataSet ReadXmlSchema - DataSet ReadXmlSchema に XmlReader を使用します - - - - Review DataView CollectionString - DataView CollectionString を確認します - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - コードをレビューして、System.Data.DataViewManager.DataViewSettingCollectionString 入力の使用が DTD を含まないように校正されていることを確認してください。XML リーダーで DTD 処理を有効にし、外部 XML エンティティの解決に UrlResolver を使用すると、情報漏えいにつながる可能性があります。XML を処理しているコンピューターのファイル システムまたはネットワーク共有のコンテンツは、攻撃者にさらされる可能性があります。また、攻撃者はこれを DoS ベクトルとして使用する可能性があります。 - - - - Review DataView CollectionString - DataView CollectionString を確認します - - - - Use XmlReader for DataTable ReadXml - DataTable ReadXml に XmlReader を使用します - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - System.Data.DataTable.ReadXml の安全でないオーバーロードを使用しないでください。この API により、使用されている XML リーダー インスタンスでの DTD 処理が内部で有効になり、外部 XML エンティティの解決に UrlResolver が使用されます。その結果は情報漏えいです。XML を処理しているコンピューターのファイル システムまたはネットワーク共有のコンテンツは、攻撃者にさらされる可能性があります。また、攻撃者はこれを DoS ベクトルとして使用する可能性があります。 - - - - Use XmlReader for DataTable ReadXml - DataTable ReadXml に XmlReader を使用します - - - - Use XmlReader for DataTable ReadXmlSchema - DataTable ReadXmlSchema に XmlReader を使用します - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - System.Data.DataTable.ReadXmlSchema の安全でないオーバーロードの使用状況を確認します。この API により、使用されている XML リーダー インスタンスでの DTD 処理が内部で有効になり、外部 XML エンティティの解決に UrlResolver が使用されます。その結果は情報漏えいです。XML を処理しているコンピューターのファイル システムまたはネットワーク共有のコンテンツは、攻撃者にさらされる可能性があります。また、攻撃者はこれを DoS ベクトルとして使用する可能性があります。 - - - - Use XmlReader for DataTable ReadXmlSchema - DataTable ReadXmlSchema に XmlReader を使用します - - Do Not Catch Corrupted State Exceptions 破損状態例外をキャッチしません @@ -212,11 +137,6 @@ '{0}' メソッドの安全でないオーバーロード CA3075 - - Insecure DTD Processing - DTD 処理が安全ではありません - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. System.Xml.XmlDocument の InnerXml プロパティの安全でないセッターを使用します。 diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ko.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ko.xlf index bdba3d39bb..a213911cbe 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ko.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ko.xlf @@ -62,81 +62,6 @@ ISerializable 형식에서 기본 클래스 메서드를 호출하세요. - - Use XmlReader for DataSet ReadXml - DataSet ReadXml에 대해 XmlReader를 사용하세요. - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - System.Data.DataSet.ReadXml의 안전하지 않은 오버로드를 사용하지 마세요. 이 API는 사용하는 XML 판독기 인스턴스에서 DTD 처리를 내부적으로 활성화하고, UrlResolver를 사용하여 외부 XML 엔터티를 확인합니다. 이에 따른 결과는 정보 공개입니다. XML을 처리하는 머신의 파일 시스템 또는 네트워크 공유 콘텐츠는 공격자에게 노출될 수 있습니다. 또한, 공격자는 이러한 콘텐츠를 DoS 벡터로 사용할 수 있습니다. - - - - Use XmlReader for DataSet ReadXml - DataSet ReadXml에 대해 XmlReader를 사용하세요. - - - - Use XmlReader for DataSet ReadXmlSchema - DataSet ReadXmlSchema에 대해 XmlReader를 사용하세요. - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - System.Data.DataSet.ReadXmlSchema의 안전하지 않은 오버로드를 사용하지 마세요. 이 API는 사용하는 XML 판독기 인스턴스에서 DTD 처리를 내부적으로 활성화하고, UrlResolver를 사용하여 외부 XML 엔터티를 확인합니다. 이에 따른 결과는 정보 공개입니다. XML을 처리하는 머신의 파일 시스템 또는 네트워크 공유 콘텐츠는 공격자에게 노출될 수 있습니다. 또한, 공격자는 이러한 콘텐츠를 DoS 벡터로 사용할 수 있습니다. - - - - Use XmlReader for DataSet ReadXmlSchema - DataSet ReadXmlSchema에 대해 XmlReader를 사용하세요. - - - - Review DataView CollectionString - DataView CollectionString을 검토하세요. - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - DTD를 포함하지 않도록 System.Data.DataViewManager.DataViewSettingCollectionString 입력의 사용이 삭제되었는지 코드를 검토하세요. XML 판독기에서 DTD 처리를 사용하고 외부 XML 엔터티를 확인하기 위해 UrlResolver를 사용하면 정보가 공개될 수 있습니다. 파일 시스템의 콘텐츠 또는 XML을 처리하는 컴퓨터의 네트워크 공유가 공격자에 노출될 수 있습니다. 또한 공격자는 이를 DoS 벡터로 사용할 수 있습니다. - - - - Review DataView CollectionString - DataView CollectionString을 검토하세요. - - - - Use XmlReader for DataTable ReadXml - DataTable ReadXml에 대해 XmlReader를 사용하세요. - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - System.Data.DataTable.ReadXml의 안전하지 않은 오버로드를 사용하지 마세요. 이 API는 인스턴스가 사용된 XML 판독기에서 내부적으로 DTD 처리를 사용하며 외부 XML 엔터티를 확인하기 위해 UrlResolver를 사용합니다. 그 결과, 정보가 공개됩니다. 파일 시스템의 콘텐츠 또는 XML을 처리하는 컴퓨터의 네트워크 공유가 공격자에 노출될 수 있습니다. 또한 공격자는 이를 DoS 벡터로 사용할 수 있습니다. - - - - Use XmlReader for DataTable ReadXml - DataTable ReadXml에 대해 XmlReader를 사용하세요. - - - - Use XmlReader for DataTable ReadXmlSchema - DataTable ReadXmlSchema에 대해 XmlReader를 사용하세요. - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - System.Data.DataTable.ReadXmlSchema의 안전하지 않은 오버로드 사용을 확인합니다. 이 API는 인스턴스가 사용된 XML 판독기에서 내부적으로 DTD 처리를 사용하며 외부 XML 엔터티를 확인하기 위해 UrlResolver를 사용합니다. 그 결과, 정보가 공개됩니다. 파일 시스템의 콘텐츠 또는 XML을 처리하는 컴퓨터의 네트워크 공유가 공격자에 노출될 수 있습니다. 또한 공격자는 이를 DoS 벡터로 사용할 수 있습니다. - - - - Use XmlReader for DataTable ReadXmlSchema - DataTable ReadXmlSchema에 대해 XmlReader를 사용하세요. - - Do Not Catch Corrupted State Exceptions 손상된 상태 예외를 catch하지 마세요. @@ -212,11 +137,6 @@ '{0}' 메서드의 안전하지 않은 오버로드 CA3075 - - Insecure DTD Processing - 안전하지 않은 DTD 처리 - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. System.Xml.XmlDocument의 InnerXml 속성에 대한 안전하지 않은 setter를 사용합니다. diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.pl.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.pl.xlf index c6d46e4e97..6a19504c0d 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.pl.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.pl.xlf @@ -62,81 +62,6 @@ Wywołuj metody klasy podstawowej dla typów ISerializable - - Use XmlReader for DataSet ReadXml - Użyj elementu XmlReader dla elementu DataSet ReadXml - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Nie używaj niebezpiecznych przeciążeń elementu System.Data.DataSet.ReadXml. Ten interfejs API wewnętrznie umożliwia przetwarzanie elementu DTD w używanym wystąpieniu obiektu odczytującego XML i używa elementu UrlResolver do rozpoznawania zewnętrznych jednostek XML. Wynikiem jest ujawnienie informacji. Zawartość systemu plików lub udziałów sieciowych w przypadku maszynowego przetwarzania elementu XML może być narażona na atak. Ponadto atakujący może użyć tego jako wektora ataku DoS. - - - - Use XmlReader for DataSet ReadXml - Użyj elementu XmlReader dla elementu DataSet ReadXml - - - - Use XmlReader for DataSet ReadXmlSchema - Użyj elementu XmlReader dla elementu DataSet ReadXmlSchema - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Nie używaj niebezpiecznych przeciążeń elementu System.Data.DataSet.ReadXmlSchema. Ten interfejs API wewnętrznie umożliwia przetwarzanie elementu DTD w używanym wystąpieniu obiektu odczytującego XML i używa elementu UrlResolver do rozpoznawania zewnętrznych jednostek XML. Wynikiem jest ujawnienie informacji. Zawartość systemu plików lub udziałów sieciowych w przypadku maszynowego przetwarzania elementu XML może być narażona na atak. Ponadto atakujący może użyć tego jako wektora ataku DoS. - - - - Use XmlReader for DataSet ReadXmlSchema - Użyj elementu XmlReader dla elementu DataSet ReadXmlSchema - - - - Review DataView CollectionString - Przejrzyj element DataView CollectionString - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Przejrzyj kod, aby upewnić się, że użycie danych wejściowych System.Data.DataViewManager.DataViewSettingCollectionString zostało oczyszczone i nie zawiera elementu DTD. Włączenie przetwarzania elementu DTD w obiekcie odczytującym XML i używanie elementu UrlResolver do rozpoznawania zewnętrznych jednostek XML może prowadzić do ujawnienia informacji. Zawartość systemu plików lub udziałów sieciowych w przypadku maszynowego przetwarzania elementu XML może być narażona na atak. Ponadto atakujący może użyć tego jako wektora ataku DoS. - - - - Review DataView CollectionString - Przejrzyj element DataView CollectionString - - - - Use XmlReader for DataTable ReadXml - Użyj elementu XmlReader dla elementu DataTable ReadXml - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Nie używaj niebezpiecznych przeciążeń elementu System.Data.DataTable.ReadXml. Ten interfejs API wewnętrznie umożliwia przetwarzanie elementu DTD w używanym wystąpieniu obiektu odczytującego XML i używa elementu UrlResolver do rozpoznawania zewnętrznych jednostek XML. Wynikiem jest ujawnienie informacji. Zawartość systemu plików lub udziałów sieciowych w przypadku maszynowego przetwarzania elementu XML może być narażona na atak. Ponadto atakujący może użyć tego jako wektora ataku DoS. - - - - Use XmlReader for DataTable ReadXml - Użyj elementu XmlReader dla elementu DataTable ReadXml - - - - Use XmlReader for DataTable ReadXmlSchema - Użyj elementu XmlReader dla elementu DataTable ReadXmlSchema - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Sprawdza, czy używane jest niebezpieczne przeciążenie elementu System.Data.DataTable.ReadXmlSchema. Ten interfejs API wewnętrznie umożliwia przetwarzanie elementu DTD w używanym wystąpieniu obiektu odczytującego XML i używa elementu UrlResolver do rozpoznawania zewnętrznych jednostek XML. Wynikiem jest ujawnienie informacji. Zawartość systemu plików lub udziałów sieciowych w przypadku maszynowego przetwarzania elementu XML może być narażona na atak. Ponadto atakujący może użyć tego jako wektora ataku DoS. - - - - Use XmlReader for DataTable ReadXmlSchema - Użyj elementu XmlReader dla elementu DataTable ReadXmlSchema - - Do Not Catch Corrupted State Exceptions Nie przechwytuj wyjątków stanu uszkodzenia @@ -212,11 +137,6 @@ Niebezpieczne przeciążenie metody {0} CA3075 - - Insecure DTD Processing - Niezabezpieczone przetwarzanie elementu DTD - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. Używa niebezpiecznej metody ustawiającej właściwości InnerXml elementu System.Xml.XmlDocument. diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.pt-BR.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.pt-BR.xlf index e759eb8cd8..0adef15165 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.pt-BR.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.pt-BR.xlf @@ -62,81 +62,6 @@ Chamar métodos da classe base em tipos ISerializable - - Use XmlReader for DataSet ReadXml - Usar XmlReader para DataSet ReadXml - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Não use sobrecargas não seguras de System.Data.DataSet.ReadXml. Esta API habilita internamente o processamento DTD na instância do leitor de XML usada e usa o UrlResolver para resolver entidades XML externas. O resultado é a divulgação de informações. O conteúdo do sistema de arquivos ou dos compartilhamentos de rede para o computador que está processando o XML pode ser exposto ao invasor. Além disso, um invasor pode usar isso como um vetor DoS. - - - - Use XmlReader for DataSet ReadXml - Usar XmlReader para DataSet ReadXml - - - - Use XmlReader for DataSet ReadXmlSchema - Usar o XmlReader para DataSet ReadXmlSchema - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Não use sobrecargas não seguras de System.Data.DataSet.ReadXmlSchema. Esta API habilita internamente o processamento DTD na instância do leitor de XML usada e usa o UrlResolver para resolver entidades XML externas. O resultado é a divulgação de informações. O conteúdo do sistema de arquivos ou dos compartilhamentos de rede para o computador que está processando o XML pode ser exposto ao invasor. Além disso, um invasor pode usar isso como um vetor DoS. - - - - Use XmlReader for DataSet ReadXmlSchema - Usar o XmlReader para DataSet ReadXmlSchema - - - - Review DataView CollectionString - Examinar DataView CollectionString - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Examine o código para garantir que o uso da entrada System.Data.DataViewManager.DataViewSettingCollectionString seja corrigido para não conter DTD. Habilitar o processamento DTD no leitor XML e usar UrlResolver para resolver entidades XML externas pode levar à divulgação de informações. O conteúdo do sistema de arquivos ou dos compartilhamentos de rede para o computador que está processando o XML pode ser exposto ao invasor. Além disso, um invasor pode usar isso como um vetor DoS. - - - - Review DataView CollectionString - Examinar DataView CollectionString - - - - Use XmlReader for DataTable ReadXml - Usar XmlReader para DataTable ReadXml - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Não use sobrecargas não seguras de System.Data.DataTable.ReadXml. Esta API habilita internamente o processamento DTD na instância do leitor de XML usada e usa o UrlResolver para resolver entidades XML externas. O resultado é a divulgação de informações. O conteúdo do sistema de arquivos ou dos compartilhamentos de rede para o computador que está processando o XML pode ser exposto ao invasor. Além disso, um invasor pode usar isso como um vetor DoS. - - - - Use XmlReader for DataTable ReadXml - Usar XmlReader para DataTable ReadXml - - - - Use XmlReader for DataTable ReadXmlSchema - Usar XmlReader para DataTable ReadXmlSchema - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Verifique se há uso de uma sobrecarga não segura de System.Data.DataTable.ReadXmlSchema. Esta API habilita internamente o processamento DTD na instância do leitor de XML usada e usa o UrlResolver para resolver entidades XML externas. O resultado é a divulgação de informações. O conteúdo do sistema de arquivos ou dos compartilhamentos de rede para o computador que está processando o XML pode ser exposto ao invasor. Além disso, um invasor pode usar isso como um vetor DoS. - - - - Use XmlReader for DataTable ReadXmlSchema - Usar XmlReader para DataTable ReadXmlSchema - - Do Not Catch Corrupted State Exceptions Não capturar exceções de estado corrompido @@ -212,11 +137,6 @@ Sobrecarga não segura do método '{0}' CA3075 - - Insecure DTD Processing - Processamento DTD não seguro - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. Usa o setter não seguro da propriedade InnerXml de System.Xml.XmlDocument. diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ru.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ru.xlf index 7c82b8a721..81394c7521 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ru.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.ru.xlf @@ -62,81 +62,6 @@ Вызывайте методы базового класса для типов ISerializable - - Use XmlReader for DataSet ReadXml - Используйте XmlReader для DataSet ReadXml - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Не используйте небезопасные перегрузки System.Data.DataSet.ReadXml. Этот API допускает внутреннюю обработку DTD в используемом экземпляре модуля чтения XML, а также использует UrlResolver для разрешения внешних XML-сущностей. Результатом является раскрытие информации. Содержимое из файловой системы или сетевых папок для компьютера, обрабатывающего XML, может попасть к злоумышленнику. Кроме того, злоумышленник может использовать это в качестве вектора для атаки типа "отказ в обслуживании". - - - - Use XmlReader for DataSet ReadXml - Используйте XmlReader для DataSet ReadXml - - - - Use XmlReader for DataSet ReadXmlSchema - Используйте XmlReader для DataSet ReadXmlSchema - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Не используйте небезопасные перегрузки System.Data.DataSet.ReadXmlSchema. Этот API допускает внутреннюю обработку DTD в используемом экземпляре модуля чтения XML, а также использует UrlResolver для разрешения внешних XML-сущностей. Результатом является раскрытие информации. Содержимое из файловой системы или сетевых папок для компьютера, обрабатывающего XML, может попасть к злоумышленнику. Кроме того, злоумышленник может использовать это в качестве вектора для атаки типа "отказ в обслуживании". - - - - Use XmlReader for DataSet ReadXmlSchema - Используйте XmlReader для DataSet ReadXmlSchema - - - - Review DataView CollectionString - Проверьте DataView CollectionString - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Проверьте, что используемые входные данные System.Data.DataViewManager.DataViewSettingCollectionString очищены от DTD. Разрешение обработки DTD в модуле чтения XML и использование UrlResolver для разрешения внешних XML-сущностей может привести к раскрытию информации. Содержимое из файловой системы или сетевых папок для компьютера, обрабатывающего XML, может попасть к злоумышленнику. Кроме того, злоумышленник может использовать это в качестве вектора для атаки типа "отказ в обслуживании". - - - - Review DataView CollectionString - Проверьте DataView CollectionString - - - - Use XmlReader for DataTable ReadXml - Используйте XmlReader для DataTable ReadXml - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Не используйте небезопасные перегрузки System.Data.DataTable.ReadXml. Этот API допускает внутреннюю обработку DTD в используемом экземпляре модуля чтения XML, а также использует UrlResolver для разрешения внешних XML-сущностей. Результатом является раскрытие информации. Содержимое из файловой системы или сетевых папок для компьютера, обрабатывающего XML, может попасть к злоумышленнику. Кроме того, злоумышленник может использовать это в качестве вектора для атаки типа "отказ в обслуживании". - - - - Use XmlReader for DataTable ReadXml - Используйте XmlReader для DataTable ReadXml - - - - Use XmlReader for DataTable ReadXmlSchema - Используйте XmlReader для DataTable ReadXmlSchema - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Проверки использования небезопасной перегрузки System.Data.DataTable.ReadXmlSchema. Этот API допускает внутреннюю обработку DTD в используемом экземпляре модуля чтения XML, а также использует UrlResolver для разрешения внешних XML-сущностей. Результатом является раскрытие информации. Содержимое из файловой системы или сетевых папок для компьютера, обрабатывающего XML, может попасть к злоумышленнику. Кроме того, злоумышленник может использовать это в качестве вектора для атаки типа "отказ в обслуживании". - - - - Use XmlReader for DataTable ReadXmlSchema - Используйте XmlReader для DataTable ReadXmlSchema - - Do Not Catch Corrupted State Exceptions Не перехватывайте исключения поврежденного состояния @@ -212,11 +137,6 @@ Небезопасная перегрузка метода "{0}" CA3075 - - Insecure DTD Processing - Небезопасная обработка DTD - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. Использует небезопасный метод задания свойства InnerXml для System.Xml.XmlDocument. diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.tr.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.tr.xlf index 33b0e57268..9918632c17 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.tr.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.tr.xlf @@ -62,81 +62,6 @@ ISerializable türleri üzerinde temel sınıf yöntemlerini çağırın - - Use XmlReader for DataSet ReadXml - DataSet ReadXml için XmlReader kullanın - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Güvenli olmayan System.Data.DataSet.ReadXml aşırı yükleri kullanmayın. Bu API kullanılan XML okuyucusu örneği üzerinde iç DTD işlemeyi etkinleştirir ve dış XML varlıkları için UrlResolver kullanır. Sonuç, bilgilerin açığa çıkmasıdır. XML’i işleyen makine için dosya sistemi veya ağ paylaşımlarından içerikler saldırgan için açığa çıkarılabilir. Ayrıca, bir saldırgan bunu bir DoS vektörü olarak kullanabilir. - - - - Use XmlReader for DataSet ReadXml - DataSet ReadXml için XmlReader kullanın - - - - Use XmlReader for DataSet ReadXmlSchema - DataSet ReadXmlSchema için XmlReader kullanın - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Güvenli olmayan System.Data.DataSet.ReadXmlSchema aşırı yükleri kullanmayın. Bu API kullanılan XML okuyucusu örneği üzerinde iç DTD işlemeyi etkinleştirir ve dış XML varlıkları için UrlResolver kullanır. Sonuç, bilgilerin açığa çıkmasıdır. XML’i işleyen makine için dosya sistemi veya ağ paylaşımlarından içerikler saldırgan için açığa çıkarılabilir. Ayrıca, bir saldırgan bunu bir DoS vektörü olarak kullanabilir. - - - - Use XmlReader for DataSet ReadXmlSchema - DataSet ReadXmlSchema için XmlReader kullanın - - - - Review DataView CollectionString - DataView CollectionString’i gözden geçirin - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - System.Data.DataViewManager.DataViewSettingCollectionString girişi kullanımının DTD içermeyecek şekilde temizlendiğinden emin olmak için kodu gözden geçirin. XML okuyucusu üzerinde DTD’yi etkinleştirmek ve dış XML varlıklarını çözümlemek için UrlResolver kullanmak bilgilerin açığa çıkarılmasına neden olabilir. XML’i işleyen makine için dosya sistemi veya ağ paylaşımlarından içerikler saldırgan için açığa çıkarılabilir. Ayrıca, bir saldırgan bunu bir DoS vektörü olarak kullanabilir. - - - - Review DataView CollectionString - DataView CollectionString’i gözden geçirin - - - - Use XmlReader for DataTable ReadXml - DataTable ReadXml için XmlReader kullanın - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Güvenli olmayan System.Data.DataTable.ReadXml aşırı yükleri kullanmayın. Bu API kullanılan XML okuyucusu örneği üzerinde iç DTD işlemeyi etkinleştirir ve dış XML varlıkları için UrlResolver kullanır. Sonuç, bilgilerin açığa çıkmasıdır. XML’i işleyen makine için dosya sistemi veya ağ paylaşımlarından içerikler saldırgan için açığa çıkarılabilir. Ayrıca, bir saldırgan bunu bir DoS vektörü olarak kullanabilir. - - - - Use XmlReader for DataTable ReadXml - DataTable ReadXml için XmlReader kullanın - - - - Use XmlReader for DataTable ReadXmlSchema - DataTable ReadXmlSchema için XmlReader kullanın - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - Güvenli olmayan System.Data.DataTable.ReadXmlSchema aşırı yüklerinin kullanımını denetler. Bu API kullanılan XML okuyucusu örneği üzerinde iç DTD işlemeyi etkinleştirir ve dış XML varlıkları için UrlResolver kullanır. Sonuç, bilgilerin açığa çıkmasıdır. XML’i işleyen makine için dosya sistemi veya ağ paylaşımlarından içerikler saldırgan için açığa çıkarılabilir. Ayrıca, bir saldırgan bunu bir DoS vektörü olarak kullanabilir. - - - - Use XmlReader for DataTable ReadXmlSchema - DataTable ReadXmlSchema için XmlReader kullanın - - Do Not Catch Corrupted State Exceptions Bozuk Durum Özel Durumlarını Yakalama @@ -212,11 +137,6 @@ '{0}' yönteminin güvenli olmayan aşırı yükü CA3075 - - Insecure DTD Processing - Güvenli Olmayan DTD İşleme - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. System.Xml.XmlDocument’in güvenli olmayan InnerXml özellik ayarlayıcısını kullanır. diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.zh-Hans.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.zh-Hans.xlf index 285cbf11e5..2d95200dd8 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.zh-Hans.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.zh-Hans.xlf @@ -62,81 +62,6 @@ 对 ISerializable 类型调用基类方法 - - Use XmlReader for DataSet ReadXml - 使用 DataSet ReadXml 的 XmlReader - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 不要使用 System.Data.DataSet.ReadXml 的不安全重载。此 API 在内部对所用的 XML 读取器实例启用了 DTD 处理，并使用 UrlResolver 解析外部 XML 实体。这导致了信息泄漏。供计算机处理 XML 的文件系统或网络共享内容可能会暴露给攻击者。另外，攻击者可能会将其用作 DoS 矢量。 - - - - Use XmlReader for DataSet ReadXml - 使用 DataSet ReadXml 的 XmlReader - - - - Use XmlReader for DataSet ReadXmlSchema - 使用 DataSet ReadXmlSchema 的 XmlReader - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 不要使用 System.Data.DataSet.ReadXmlSchema 的不安全重载。此 API 在内部对所用的 XML 读取器实例启用了 DTD 处理，并使用 UrlResolver 解析外部 XML 实体。这导致了信息泄漏。供计算机处理 XML 的文件系统或网络共享内容可能会暴露给攻击者。另外，攻击者可能会将其用作 DoS 矢量。 - - - - Use XmlReader for DataSet ReadXmlSchema - 使用 DataSet ReadXmlSchema 的 XmlReader - - - - Review DataView CollectionString - 评审 DataView CollectionString - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 请评审代码，确保已清理 System.Data.DataViewManager.DataViewSettingCollectionString 输入的使用情况，使其不含 DTD。如果在 XML 读取器中启用 DTD 处理并使用 UrlResolver 解析外部 XML 实体，这可能会导致信息泄露。供计算机处理 XML 的文件系统或网络共享内容可能会暴露给攻击者。另外，攻击者可能会将其用作 DoS 矢量。 - - - - Review DataView CollectionString - 评审 DataView CollectionString - - - - Use XmlReader for DataTable ReadXml - 使用 DataTable ReadXml 的 XmlReader - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 不要使用 System.Data.DataTable.ReadXml 的不安全重载。此 API 在内部对所用的 XML 读取器实例启用了 DTD 处理，并使用 UrlResolver 解析外部 XML 实体。这导致了信息泄漏。供计算机处理 XML 的文件系统或网络共享内容可能会暴露给攻击者。另外，攻击者可能会将其用作 DoS 矢量。 - - - - Use XmlReader for DataTable ReadXml - 使用 DataTable ReadXml 的 XmlReader - - - - Use XmlReader for DataTable ReadXmlSchema - 使用 DataTable ReadXmlSchema 的 XmlReader - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 检查 System.Data.DataTable.ReadXmlSchema 的不安全重载的使用情况。此 API 在内部对所用的 XML 读取器实例启用了 DTD 处理，并使用 UrlResolver 解析外部 XML 实体。这导致了信息泄漏。供计算机处理 XML 的文件系统或网络共享内容可能会暴露给攻击者。另外，攻击者可能会将其用作 DoS 矢量。 - - - - Use XmlReader for DataTable ReadXmlSchema - 使用 DataTable ReadXmlSchema 的 XmlReader - - Do Not Catch Corrupted State Exceptions 不要捕获损坏状态异常 @@ -212,11 +137,6 @@ “{0}”方法的不安全重载 CA3075 - - Insecure DTD Processing - 不安全的 DTD 处理 - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. 使用 System.Xml.XmlDocument 的 InnerXml 属性的不安全资源库。 diff --git a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.zh-Hant.xlf b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.zh-Hant.xlf index 3a0b8dd0cd..3138deb731 100644 --- a/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.zh-Hant.xlf +++ b/src/NetAnalyzers/Core/Microsoft.NetFramework.Analyzers/xlf/MicrosoftNetFrameworkAnalyzersResources.zh-Hant.xlf @@ -62,81 +62,6 @@ 呼叫 ISerializable 類型上的基底類別方法 - - Use XmlReader for DataSet ReadXml - 為 DataSet ReadXml 使用 XmlReader - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 請勿使用 System.Data.DataSet.ReadXml 的不安全多載。此 API 會在執行個體使用的 XML 讀取器上，於內部啟用 DTD 處理，並使用 UrlResolver 解析外部 XML 實體。結果會造成資訊外洩。攻擊者有可能會看到為處理 XML 的電腦所提供之檔案系統或網路共用內容。此外，攻擊者還可以使用它作為 DoS 向量。 - - - - Use XmlReader for DataSet ReadXml - 為 DataSet ReadXml 使用 XmlReader - - - - Use XmlReader for DataSet ReadXmlSchema - 為 DataSet ReadXmlSchema 使用 XmlReader - - - - Do not use unsafe overloads of System.Data.DataSet.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 請勿使用 System.Data.DataSet.ReadXmlSchema 的不安全多載。此 API 會在執行個體使用的 XML 讀取器上，於內部啟用 DTD 處理，並使用 UrlResolver 解析外部 XML 實體。結果會造成資訊外洩。攻擊者有可能會看到為處理 XML 的電腦所提供之檔案系統或網路共用內容。此外，攻擊者還可以使用它作為 DoS 向量。 - - - - Use XmlReader for DataSet ReadXmlSchema - 為 DataSet ReadXmlSchema 使用 XmlReader - - - - Review DataView CollectionString - 檢閱 DataView CollectionString - - - - Review code to insure that usage of System.Data.DataViewManager.DataViewSettingCollectionString input is sanitized to not contain DTD. Enabling DTD processing on the XML reader and using UrlResolver for resolving external XML entities may lead to information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 檢閱程式碼以確保 System.Data.DataViewManager.DataViewSettingCollectionString 輸入的使用經過處理，以排除 DTD。在 XML 讀取器上啟用 DTD 處理，並使用 UrlResolver 解析外部 XML 實體，可能會造成資訊外洩。攻擊者有可能會看到為處理 XML 的電腦所提供之檔案系統或網路共用內容。此外，攻擊者還可以使用它作為 DoS 向量。 - - - - Review DataView CollectionString - 檢閱 DataView CollectionString - - - - Use XmlReader for DataTable ReadXml - 為 DataTable ReadXml 使用 XmlReader - - - - Do not use unsafe overloads of System.Data.DataTable.ReadXml. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 請勿使用 System.Data.DataTable.ReadXml 的不安全多載。此 API 會在執行個體使用的 XML 讀取器上，於內部啟用 DTD 處理，並使用 UrlResolver 解析外部 XML 實體。結果會造成資訊外洩。攻擊者有可能會看到為處理 XML 的電腦所提供之檔案系統或網路共用內容。此外，攻擊者還可以使用它作為 DoS 向量。 - - - - Use XmlReader for DataTable ReadXml - 為 DataTable ReadXml 使用 XmlReader - - - - Use XmlReader for DataTable ReadXmlSchema - 為 DataTable ReadXmlSchema 使用 XmlReader - - - - Checks for usage of an unsafe overload of System.Data.DataTable.ReadXmlSchema. This API internally enables DTD processing on the XML reader instance used, and uses UrlResolver for resolving external XML entities. The outcome is information disclosure. Content from file system or network shares for the machine processing the XML can be exposed to attacker. In addition, an attacker can use this as a DoS vector. - 檢查 System.Data.DataTable.ReadXmlSchema 不安全多載的使用方式。此 API 會在執行個體使用的 XML 讀取器上，於內部啟用 DTD 處理，並使用 UrlResolver 解析外部 XML 實體。結果會造成資訊外洩。攻擊者有可能會看到為處理 XML 的電腦所提供之檔案系統或網路共用內容。此外，攻擊者還可以使用它作為 DoS 向量。 - - - - Use XmlReader for DataTable ReadXmlSchema - 為 DataTable ReadXmlSchema 使用 XmlReader - - Do Not Catch Corrupted State Exceptions 請勿擷取損毀狀態例外狀況 @@ -212,11 +137,6 @@ '{0}' 方法的不安全多載 CA3075 - - Insecure DTD Processing - 不安全的 DTD 處理 - CA3075 - Uses the unsafe setter of InnerXml property of System.Xml.XmlDocument. 使用 System.Xml.XmlDocument 的 InnerXml 屬性之不安全 setter。 diff --git a/src/PublicApiAnalyzers/Core/Analyzers/PublicApiAnalyzerResources.resx b/src/PublicApiAnalyzers/Core/Analyzers/PublicApiAnalyzerResources.resx index 531042fefa..a763f9f5ba 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/PublicApiAnalyzerResources.resx +++ b/src/PublicApiAnalyzers/Core/Analyzers/PublicApiAnalyzerResources.resx @@ -208,12 +208,6 @@ implicit set-accessor for '{0}' - - One or both of the public API files are missing - - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Add all items in document '{0}' to the API @@ -223,15 +217,6 @@ Add all items in the solution to the API - - Annotate all items in document '{0}' in the API - - - Annotate all items in project '{0}' in the API - - - Annotate all items in the solution in the API - Enable nullability annotations in the API for project '{0}' @@ -308,10 +293,4 @@ The symbol '{0}' appears more than once in the internal API files - - One or both of the internal API files are missing - - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.cs.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.cs.xlf index d40c8bf2da..ccb1321157 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.cs.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.cs.xlf @@ -17,21 +17,6 @@ Přidat všechny položky v řešení do rozhraní API - - Annotate all items in document '{0}' in the API - Přidat anotaci ke všem položkám v dokumentu {0} v rozhraní API - - - - Annotate all items in project '{0}' in the API - Přidat anotaci ke všem položkám v projektu {0} rozhraní API - - - - Annotate all items in the solution in the API - Přidat anotaci ke všem položkám v řešení v rozhraní API - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. Všechny interní typy a členy by se měly deklarovat s anotacemi o možnosti použití hodnoty null v souboru InternalAPI.txt. To přitáhne pozornost ke změnám možnosti použití hodnoty null u rozhraní API při revizích a v historii správy zdrojového kódu a pomůže předejít změnám způsobujícím chybu. @@ -177,16 +162,6 @@ Obsah souborů interních rozhraní API není platný - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Řešení musí obsahovat dva soubory typu AdditionalFiles: InternalAPI.Unshipped.txt a InternalAPI.Shipped.txt. Nejméně jeden z těchto souborů chybí nebo nemá správný typ. - - - - One or both of the internal API files are missing - Chybí nejméně jeden soubor interního rozhraní API - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. Všechny interní členové by měly používat odkazové typy s možnou hodnotou null, nebo bez ní, ale ne odkazové typy bez určení možnosti použití hodnoty null. @@ -247,16 +222,6 @@ Obsah souborů veřejných rozhraní API není platný - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Řešení musí obsahovat dva soubory typu AdditionalFiles: PublicAPI.Unshipped.txt a PublicAPI.Shipped.txt. Nejméně jeden z těchto souborů chybí nebo nemá správný typ. - - - - One or both of the public API files are missing - Chybí nejméně jeden soubor veřejného rozhraní API - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. Když se odebírá interní typ nebo člen, vložte tuto položku do souboru InternalAPI.Unshipped.txt s předponou *REMOVED*. To upozorňuje na změny rozhraní API v revizích kódu a historii správy zdrojového kódu a pomáhá předcházet změnám způsobujícím chybu. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.de.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.de.xlf index 7bd484ba77..65ff7eaac3 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.de.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.de.xlf @@ -17,21 +17,6 @@ Alle Elemente in der Lösung der API hinzufügen - - Annotate all items in document '{0}' in the API - Alle Elemente im Dokument „{0}“ in der API anmerken - - - - Annotate all items in project '{0}' in the API - Alle Elemente im Projekt „{0}“ in der API anmerken - - - - Annotate all items in the solution in the API - Alle Elemente in der Lösung in der API anmerken - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. Alle internen Typen und Member müssen in InternalAPI.txt mit Anmerkungen zur NULL-Zulässigkeit deklariert werden. Dadurch wird die Aufmerksamkeit auf Änderungen an der NULL-Zulässigkeit der API in den Code Reviews und im Quellcodeverwaltungsverlauf gelenkt, und Breaking Changes werden verhindert. @@ -177,16 +162,6 @@ Die Inhalte der internen API-Dateien sind ungültig - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Die Lösung muss zwei Dateien mit dem Typ „AdditionalFiles“ enthalten: InternalAPI.Unshipped.txt und InternalAPI.Shipped.txt. Mindestens eine dieser Dateien fehlt oder weist den falschen Typ auf. - - - - One or both of the internal API files are missing - Mindestens eine der beiden internen API-Dateien fehlt - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. Alle internen Member sollten Verweistypen verwenden, die Nullwerte zulassen oder nicht zulassen, aber keine nicht bewussten Verweistypen. @@ -247,16 +222,6 @@ Inhalte der öffentlichen API-Dateien sind ungültig - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Die Projektmappe muss zwei Dateien mit dem Typ "AdditionalFiles" enthalten: "PublicAPI.Unshipped.txt" und "PublicAPI.Shipped.txt". txt. Mindestens eine dieser Dateien fehlt oder weist den falschen Typ auf. - - - - One or both of the public API files are missing - Mindestens eine der öffentlichen API-Dateien fehlt. - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. Wenn Sie einen internen Typ oder ein internes Member entfernen, fügen Sie diesen Eintrag in InternalAPI.Unshipped.txt mit dem Präfix „*REMOVED*“ ein. Dadurch wird die Aufmerksamkeit auf API-Änderungen in den Code Reviews und dem Quellcodeverwaltungsverlauf gelenkt,und Breaking Changes werden verhindert. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.es.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.es.xlf index ec9e890f38..396e5f991e 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.es.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.es.xlf @@ -17,21 +17,6 @@ Agregar todos los elementos de la solución a la API pública - - Annotate all items in document '{0}' in the API - Anote todos los elementos del documento "{0}" en la API - - - - Annotate all items in project '{0}' in the API - Anotar todos los elementos del proyecto "{0}" en la API - - - - Annotate all items in the solution in the API - Anote todos los elementos de la solución en la API - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. Todos los tipos y miembros internos deben declararse con anotaciones de nulabilidad en InternalAPI.txt. Esto atrae la atención a los cambios de nulabilidad de la API en las revisiones de código y el historial de control de código fuente; además, ayuda a evitar cambios importantes. @@ -177,16 +162,6 @@ El contenido de los archivos internos de la API no es válido - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - La solución debe contener dos archivos con el tipo "AdditionalFiles": InternalAPI.Unshipped.txt y InternalAPI.Shipped.txt. Al menos uno de estos archivos falta o tiene un tipo incorrecto. - - - - One or both of the internal API files are missing - Faltan uno o los dos archivos internos de la API - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. Todos los miembros públicos deben usar tipos de referencia que se puedan o no anular, pero no tipos de referencia inconscientes. @@ -247,16 +222,6 @@ El contenido de los archivos de la API pública no es válido - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - La solución debe contener dos archivos con el tipo "AdditionalFiles": PublicAPI.Unshipped.txt y PublicAPI.Shipped.txt. Al menos uno de estos archivos falta o tiene un tipo incorrecto. - - - - One or both of the public API files are missing - Faltan los dos archivos de la API pública o uno de ellos - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. Al quitar un tipo o miembro público, coloque esa entrada en InternalAPI.Unshipped.txt con el prefijo "*REMOVED*". Esto atrae la atención a los cambios de la API en las revisiones de código y el historial de control de código fuente; además, ayuda a evitar cambios importantes. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.fr.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.fr.xlf index 9eb6ad52bb..8565484183 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.fr.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.fr.xlf @@ -17,21 +17,6 @@ Ajouter tous les éléments de la solution à l’API - - Annotate all items in document '{0}' in the API - Annoter tous les éléments du document «{0}» dans l’API - - - - Annotate all items in project '{0}' in the API - Annoter tous les éléments du projet '{0}' dans l’API - - - - Annotate all items in the solution in the API - Annoter tous les éléments de la solution dans l’API - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. Tous les types et membres internes doivent être déclarés avec des annotations de nullabilité dans InternalAPI.txt. Cela attire l’attention sur les modifications de nullabilité de l’API dans les révisions de code et l’historique du contrôle de code source, et permet d’éviter les changements cassants. @@ -177,16 +162,6 @@ Le contenu des fichiers d’API internes n’est pas valide - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - La solution doit contenir deux fichiers de type « AdditionalFiles » : InternalAPI.Unshipped.txt et internalAPI.Shipped.txt. Au moins un de ces fichiers est manquant ou a un type incorrect. - - - - One or both of the internal API files are missing - Un ou les deux fichiers d’API internes sont manquants - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. Tous les membres internes doivent utiliser des types référence nullables ou non nullables, mais aucun type référence inconscient. @@ -247,16 +222,6 @@ Le contenu des fichiers de l'API publique est non valide - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - La solution doit contenir deux fichiers ayant le type "AdditionalFiles" : PublicAPI.Unshipped.txt et PublicAPI.Shipped.txt. L'un de ces fichiers est manquant, ou son type est incorrect. - - - - One or both of the public API files are missing - Il manque l'un des deux fichiers d'API publiques, ou les deux - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. Lors de la suppression d’un type ou d’un membre interne, placez cette entrée dans InternalAPI.Unshipped.txt avec le préfixe '*REMOVED*'. Cela attire l’attention sur les modifications d’API dans les révisions de code et l’historique du contrôle de code source, et permet d’éviter les changements cassants. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.it.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.it.xlf index 687bfd7de6..c48bac46d8 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.it.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.it.xlf @@ -17,21 +17,6 @@ Aggiungi tutti gli elementi della soluzione all'API - - Annotate all items in document '{0}' in the API - Annota tutti gli elementi del documento '{0}' nell'API - - - - Annotate all items in project '{0}' in the API - Annota tutti gli elementi del progetto '{0}' nell'API - - - - Annotate all items in the solution in the API - Annota tutti gli elementi della soluzione nell'API - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. Tutti i tipi e i membri interni devono essere dichiarati con annotazioni di supporto dei valori Null in InternalAPI.txt. In questo modo si richiama l'attenzione sulle modifiche del supporto dei valori Null all'API nelle revisioni del codice e nella cronologia del controllo del codice sorgente e si contribuisce a evitare modifiche che causano un'interruzione. @@ -177,16 +162,6 @@ Il contenuto dei file dell'API interna non è valido: - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - La soluzione deve contenere due file con il tipo "AdditionalFiles": InternalAPI.unshipped.txt e InternalAPI.shipped.txt. Almeno uno di questi file manca o è di tipo errato. - - - - One or both of the internal API files are missing - Uno o entrambi i file dell'API interna sono mancanti - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. Tutti i membri interni devono usare tipi riferimento nullable o non nullable, ma non tipi riferimento oblivious. @@ -247,16 +222,6 @@ Il contenuto dei file dell'API pubblica non è valido - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - La soluzione deve contenere due file con il tipo "AdditionalFiles": PublicAPI.unshipped.txt e PublicAPI.shipped.txt. Almeno uno di questi file manca o è di tipo errato. - - - - One or both of the public API files are missing - Uno o entrambi i file dell'API pubblica sono mancanti - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. Quando si rimuove un tipo o un membro interno, è necessario inserire questa voce in InternalAPI.Unshipped.txt con prefisso '*REMOVED*’. In questo modo si richiama l'attenzione sulle modifiche all'API nelle revisioni del codice e nella cronologia dei controlli del codice sorgente, e si contribuisce a evitare modifiche che causano un'interruzione. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ja.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ja.xlf index 2ce75ecf79..cd4054f86d 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ja.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ja.xlf @@ -17,21 +17,6 @@ ソリューション内のすべての項目を API へ追加 - - Annotate all items in document '{0}' in the API - API のドキュメント '{0}' 内のすべての項目に注釈を付ける - - - - Annotate all items in project '{0}' in the API - API のプロジェクト '{0}' 内のすべての項目に注釈を付ける - - - - Annotate all items in the solution in the API - API のソリューション内のすべての項目に注釈を付ける - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. すべての内部の型とメンバーは、NULL 値許容の注釈を付けて、InternalAPI.txt で宣言する必要があります。これにより、コード レビューとソース管理履歴で API の NULL 値の許容の変更に注意を引くことができ、破壊的変更を防ぐことができます。 @@ -177,16 +162,6 @@ 内部 API ファイルのコンテンツが無効 - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - ソリューションには、種類が "AdditionalFiles" の 2 つのファイル (InternalAPI.Unshipped.txt と InternalAPI.Unshipped.txt) が含まれている必要があります。これらのファイルのうち少なくとも 1 つが見つからないか、種類が正しくありません。 - - - - One or both of the internal API files are missing - 内部 API ファイルの 1 つまたは両方が見つからない - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. すべての内部メンバーは、Null 許容参照型と null 非許容参照型のいずれかを使用する必要がありますが、oblivious 参照型は使用しません。 @@ -247,16 +222,6 @@ パブリック API ファイルのコンテンツが無効です - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - ソリューションには、種類が "AdditionalFiles" の 2 つのファイル (PublicAPI.Unshipped.txt と PublicAPI.Shipped.txt) が含まれている必要があります。これらのファイルのうち少なくとも 1 つが見つからないか、種類が正しくありません。 - - - - One or both of the public API files are missing - パブリック API ファイルの 1 つまたは両方が見つからない - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. 内部の型またはメンバーを削除する際、その項目を InternalAPI.Unshipped.txt に '*REMOVED*' プレフィックスを付けて記入する必要があります。これにより、コード レビューとソース管理履歴で API の変更に注意を引くことができ、破壊的変更を防ぐことができます。 diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ko.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ko.xlf index 1a4d8bfee6..dac3176758 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ko.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ko.xlf @@ -17,21 +17,6 @@ API에 솔루션의 모든 항목 추가 - - Annotate all items in document '{0}' in the API - API에서 문서 '{0}'의 모든 항목에 주석 달기 - - - - Annotate all items in project '{0}' in the API - API에서 프로젝트 '{0}'의 모든 항목에 주석 추가 - - - - Annotate all items in the solution in the API - API에서 솔루션의 모든 항목에 주석 달기 - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. 모든 내부 형식 및 구성원은 InternalAPI.txt에서 Null 허용 여부 주석을 포함하여 선언되어야 합니다. 그러면 코드 검토 및 소스 제어 기록에서 API Null 허용 여부 변경 내용을 쉽게 확인할 수 있고 호환성이 손상되는 변경을 방지할 수 있습니다. @@ -177,16 +162,6 @@ 내부 API 파일의 내용이 잘못되었습니다. - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - 솔루션에는 "AdditionalFiles" 형식의 두 파일(InternalAPI.Unshipped.txt 및 internalAPI.Shipped.txt)이 포함되어야 합니다. 이러한 파일 중 하나 이상이 없거나 형식이 잘못되었습니다. - - - - One or both of the internal API files are missing - 내부 API 파일 중 하나 또는 둘 다 없습니다. - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. 모든 내부 구성원은 null을 허용하거나 null을 허용하지 않는 참조 형식을 사용해야 하지만, 인식 불가능한 참조 형식은 사용하면 안 됩니다. @@ -247,16 +222,6 @@ 공용 API 파일의 콘텐츠가 유효하지 않습니다. - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - 솔루션에 "AdditionalFiles": PublicAPI.Unshipped.txt 및 PublicAPI.Shipped.txt 형식의 파일이 두 개 포함되어야 합니다. 이러한 파일 중 하나 이상이 없거나 형식이 잘못되었습니다. - - - - One or both of the public API files are missing - 공용 API 파일 중 하나 또는 둘 다 없습니다. - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. 내부 형식 또는 구성원을 제거할 때 해당 항목을 InternalAPI.Unshipped.txt에 '*REMOVED*' 접두어를 추가합니다. 이는 코드 검토 및 소스 제어 기록의 API 변경 내용에 주의를 기울이고 주요 변경 내용을 방지하는 데 도움이 됩니다. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.pl.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.pl.xlf index 6fd3e14f13..ecc2859dd5 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.pl.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.pl.xlf @@ -17,21 +17,6 @@ Dodaj wszystkie elementy w rozwiązaniu interfejsu API - - Annotate all items in document '{0}' in the API - Dodawanie adnotacji do wszystkich elementów w dokumencie „{0}” w interfejsie API - - - - Annotate all items in project '{0}' in the API - Dodawanie adnotacji do wszystkich elementów w projekcie „{0}” w interfejsie API - - - - Annotate all items in the solution in the API - Dodawanie adnotacji do wszystkich elementów w rozwiązaniu w interfejsie API - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. Wszystkie wewnętrzne typy i składowe powinny być zadeklarowane w pliku PublicAPI.txt z adnotacjami opcji dopuszczania wartości null. To zwraca uwagę na zmiany opcji dopuszczania wartości null interfejsu API w przeglądach kodu i historii kontroli źródła oraz pomaga zapobiegać zmianom powodującym nieprawidłowe działanie. @@ -177,16 +162,6 @@ Zawartość plików wewnętrznego interfejsu API jest nieprawidłowa - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Rozwiązanie musi zawierać dwa pliki typu „AdditionalFiles”: PublicAPI.Unshipped.txt i PublicAPI.Shipped.txt. Brakuje co najmniej jednego z tych plików lub ma on nieprawidłowy typ. - - - - One or both of the internal API files are missing - Brak jednego lub obu plików wewnętrznego interfejsu API - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. Wszystkie publiczne składowe powinny używać typów referencyjnych dopuszczających wartość null lub nie dopuszczających jej, ale nie nieświadomych typów referencyjnych. @@ -247,16 +222,6 @@ Zawartość plików publicznego interfejsu API jest nieprawidłowa - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Rozwiązanie musi zawierać dwa pliki typu „AdditionalFiles”: PublicAPI.Unshipped.txt i PublicAPI.Shipped.txt. Brakuje co najmniej jednego z tych plików lub ma on nieprawidłowy typ. - - - - One or both of the public API files are missing - Brakuje co najmniej jednego pliku publicznego interfejsu API - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. W przypadku usunięcia typu wewnętrznego lub składowej należy usunąć także powiązany wpis w pliku PublicAPI.Unshipped.txt. z prefiksem ’*REMOVED*’. To przyciąga uwagę do zmian interfejsu API w przeglądach kodu i historii kontroli źródła oraz pomaga zapobiegać zmianom powodującym nieprawidłowe działanie. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.pt-BR.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.pt-BR.xlf index 2af67d4956..891b40eb41 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.pt-BR.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.pt-BR.xlf @@ -17,21 +17,6 @@ Adicione todos os itens da solução à API - - Annotate all items in document '{0}' in the API - Anote todos os itens no documento '{0}' na API - - - - Annotate all items in project '{0}' in the API - Anotar todos os itens no projeto '{0}' na API - - - - Annotate all items in the solution in the API - Anote todos os itens da solução na API - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. Todos os tipos e membros internos devem ser declarados com anotações de nulidade em InternalAPI.txt. Isso chama a atenção para as alterações de nulidade da API nas revisões de código e no histórico de controle do código-fonte e ajuda a evitar alterações significativas. @@ -177,16 +162,6 @@ O conteúdo dos arquivos internos da API é inválido - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - A solução deve conter dois arquivos do tipo "AdditionalFiles": InternalAPI.Unshipped.txt e internalAPI.Shipped.txt. Pelo menos um desses arquivos está ausente ou tem o tipo errado. - - - - One or both of the internal API files are missing - Um ou ambos os arquivos internos da API estão ausentes - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. Todos os membros internos devem usar tipos de referência anuláveis ​​ou não anuláveis, mas nenhum tipo de referência inconsciente. @@ -247,16 +222,6 @@ O conteúdo dos arquivos da API pública é inválido - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - A solução precisa conter dois arquivos com o tipo "AdditionalFiles": PublicAPI.Unshipped.txt e PublicAPI.Shipped.txt. Pelo menos um desses arquivos está ausente ou tem o tipo errado. - - - - One or both of the public API files are missing - Um ou ambos os arquivos de API pública estão ausentes - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. Ao remover um tipo ou membro interno, coloque essa entrada em InternalAPI.Unshipped.txt com o prefixo '*REMOVED*'. Isso chama a atenção para as alterações da API nas revisões de código e no histórico de controle do código-fonte e ajuda a evitar alterações significativas. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ru.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ru.xlf index 18c842a84f..8c9cea2735 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ru.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.ru.xlf @@ -17,21 +17,6 @@ Добавить все элементы решения в API - - Annotate all items in document '{0}' in the API - Добавлять заметки для всех элементов в документе "{0}" в API - - - - Annotate all items in project '{0}' in the API - Добавлять заметки для всех элементов в проекте "{0}" в API - - - - Annotate all items in the solution in the API - Добавлять заметки ко всем элементам решения в API - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. Все внутренние типы и элементы должны быть объявлены в InternalAPI.txt. с заметками допустимости значений NULL. Это привлекает внимание к изменениям допустимости значений NULL в API при проверках кода и в журнале системы управления версиями и помогает предотвратить критические изменения. @@ -177,16 +162,6 @@ Недопустимое содержимое внутренних файлов API - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Решение должно содержать два файла с типом "AdditionalFiles": InternalAPI.Unshipped.txt и internalAPI.Shipped.txt. По меньшей мере один из этих файлов отсутствует или относится к неправильному типу. - - - - One or both of the internal API files are missing - Отсутствует один или оба файла внутреннего API - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. Все внутренние элементы должны использовать ссылочные типы, допускающие или не допускающие значение NULL, но не игнорируемые ссылочные типы. @@ -247,16 +222,6 @@ Недопустимое содержимое файлов открытого API - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Решение должно содержать два файла с типом "AdditionalFiles": PublicAPI.Unshipped.txt и PublicAPI.Shipped.txt. По меньшей мере один из этих файлов отсутствует или имеет неправильный тип. - - - - One or both of the public API files are missing - Отсутствует один или оба файла открытого API - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. При удалении внутреннего типа или элемента поместите эту запись в файл InternalAPI.Unshipped.txt с префиксом "*REMOVED*". Это привлекает внимание к изменениям API в проверках кода и журнала управления версиями и помогает предотвратить критические изменения. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.tr.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.tr.xlf index 4adbcea967..468345d678 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.tr.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.tr.xlf @@ -17,21 +17,6 @@ Çözümdeki tüm öğeleri API'ye ekleyin - - Annotate all items in document '{0}' in the API - API'de yer alan '{0}' belgesindeki tüm öğelere not ekleyin - - - - Annotate all items in project '{0}' in the API - API'de yer alan '{0}' projesindeki tüm öğelere not ekleyin - - - - Annotate all items in the solution in the API - API'de yer alan çözümdeki tüm öğelere not ekleyin - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. Tüm genel türler ve üyeler PublicAPI.txt içinde null atanabilirlik ek açıklamalarıyla tanımlanmalıdır. Bu işlem, kod incelemeleri ve kaynak denetimi geçmişindeki API null atanabilirlik değişikliklerine dikkat çeker ve hataya neden olan değişikliklerin önlenmesine yardımcı olur. @@ -177,16 +162,6 @@ Dahili API dosyalarının içeriği geçersiz - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Çözüm, "AdditionalFiles" türünde iki dosya içermelidir: InternalAPI.Unshipped.txt ve internalAPI.Shipped.txt. Bu dosyalardan en az biri eksik veya yanlış türde. - - - - One or both of the internal API files are missing - Dahili API dosyalarından biri veya ikisi eksik - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. Tüm dahili üyeler, null atanabilir veya null atanamaz başvuru türleri kullanmalı, ancak habersiz başvuru türleri kullanmamalıdır. @@ -247,16 +222,6 @@ Genel API dosyalarının içerikleri geçersiz - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - Çözüm, "AdditionalFiles" türüne sahip iki dosya içermelidir: PublicAPI.Unshipped.txt ve PublicAPI.Shipped.txt. Bu dosyalardan en az biri eksik veya yanlış türe sahip. - - - - One or both of the public API files are missing - Ortak API dosyalarından biri veya her ikisi de eksik - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. Bir dahili türü veya üyeyi kaldırırken, o girişi '*REMOVED*' önekiyle InternalAPI.Unshipped.txt dosyasına koyun. Bu, kod incelemelerindeki ve kaynak denetimi geçmişindeki API değişikliklerine dikkat çeker ve değişikliklerin bozulmasını önlemeye yardımcı olur. diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.zh-Hans.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.zh-Hans.xlf index 39595c7789..2780621110 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.zh-Hans.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.zh-Hans.xlf @@ -17,21 +17,6 @@ 将解决方案中的所有项添加到 API - - Annotate all items in document '{0}' in the API - 在 API 中对文档“{0}”中的所有项进行批注 - - - - Annotate all items in project '{0}' in the API - 在 API 中对项目“{0}”中的所有项进行批注 - - - - Annotate all items in the solution in the API - 在 API 中对解决方案中的所有项进行批注 - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. 应在 InternalAPI.txt 中使用为 Null 性注释声明所有内部类型和成员。这将关注代码评审和源代码管理历史记录中的 API 为 Null 性更改，并有助于防止中断性变更。 @@ -177,16 +162,6 @@ 内部 API 文件的内容无效 - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - 解决方案必须包含两个具有类型 "AdditionalFiles" 的文件(InternalAPI.Unshipped.txt 和 InternalAPI.Shipped.txt)。其中至少有一个文件缺失或类型错误。 - - - - One or both of the internal API files are missing - 缺少一个或两个内部 API 文件 - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. 所有内部成员都应使用可以为 null 或不可为 null 的引用类型，但不能使用未知引用类型。 @@ -247,16 +222,6 @@ 公共 API 文件的内容无效 - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - 解决方案必须包含两个具有类型 "AdditionalFiles" 的文件(PublicAPI.Unshipped.txt 和 PublicAPI.Shipped.txt)。其中至少有一个文件缺失或类型错误。 - - - - One or both of the public API files are missing - 缺少一个或两个公共 API 文件 - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. 删除内部类型或成员时，将其项输入 InternalAPI.Unshipped.txt 中，并附上前缀 "*REMOVED*"。这样能够在代码评审和源代码管理历史记录中引起对 API 更改的注意，有助于防止中断性更改。 diff --git a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.zh-Hant.xlf b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.zh-Hant.xlf index fc3c34eec1..8690ef0236 100644 --- a/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.zh-Hant.xlf +++ b/src/PublicApiAnalyzers/Core/Analyzers/xlf/PublicApiAnalyzerResources.zh-Hant.xlf @@ -17,21 +17,6 @@ 將解決方案中的所有項目新增至 API - - Annotate all items in document '{0}' in the API - 標註 API 中文件 '{0}' 的所有項目 - - - - Annotate all items in project '{0}' in the API - 標註 API 中專案 '{0}' 的所有項目 - - - - Annotate all items in the solution in the API - 標註 API 中解決方案的所有項目 - - All internal types and members should be declared with nullability annotations in InternalAPI.txt. This draws attention to API nullability changes in the code reviews and source control history, and helps prevent breaking changes. 應在 InternalAPI.txt 中宣告所有內部類型與成員並加上可 NULL 性註釋。這麼做會讓您注意到程式碼檢閱與原始檔控制歷程記錄中的 API 可 NULL 性變更，同時有助於避免重大變更。 @@ -177,16 +162,6 @@ 內部 API 檔案的內容無效 - - The solution must contain two files with the type "AdditionalFiles": InternalAPI.Unshipped.txt and internalAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - 解決方案必須包含兩個類型為 "AdditionalFiles" 的檔案: InternalAPI.Unshipped.txt 與 internalAPI.Shipped.txt。這些檔案中至少遺失一個或具有錯誤的類型。 - - - - One or both of the internal API files are missing - 遺失兩個內部 API 檔案的其中一個或兩者 - - All internal members should use either nullable or non-nullable reference types, but no oblivious reference types. 所有內部成員都應使用可為 Null 或不可為 Null 的參考類型，但不可使用無警示的參考類型。 @@ -247,16 +222,6 @@ 公用 API 檔案的內容無效 - - The solution must contain two files with the type "AdditionalFiles": PublicAPI.Unshipped.txt and PublicAPI.Shipped.txt. At least one of these files is missing or has the wrong type. - 解決方案必須包含兩個類型為 "AdditionalFiles" 的檔案: PublicAPI.Unshipped.txt 與 PublicAPI.Shipped.txt。其中至少缺少一個檔案或檔案類型錯誤。 - - - - One or both of the public API files are missing - 缺少兩個公用 API 檔案的其中一個或兩者 - - When removing a internal type or member, put that entry in InternalAPI.Unshipped.txt with '*REMOVED*' prefix. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes. 移除內部類型或成員時，請將該項目放在 InternalAPI.Unshipped.txt 中並包含 '*REMOVED*' 前置詞。這麼做會讓您注意到程式碼檢閱與原始檔控制歷程記錄中的 API 變更，同時有助於避免重大變更。