Skip to content

Commit c498fc5

Browse files
mavasanimavasani
authored
Merge pull request #4680 from mateoatr/remove-sf-analyzer
Remove single-file analyzer
2 parents bb764b5 + 89f58a2 commit c498fc5

22 files changed

+3
-604
lines changed

‎src/NetAnalyzers/Core/AnalyzerReleases.Unshipped.md

+2
Original file line numberDiff line numberDiff line change
@@ -5,3 +5,5 @@
55
Rule ID | Category | Severity | Notes
66
--------|----------|----------|-------
77
CA1801 | Usage | Disabled | ReviewUnusedParametersAnalyzer, [Documentation](https://docs.microsoft.com/visualstudio/code-quality/ca1801)
8+
IL3000 | Publish | Disabled | Moved analyzer to mono/linker
9+
IL3001 | Publish | Disabled | Moved analyzer to mono/linker

‎src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/MicrosoftNetCoreAnalyzersResources.resx

-9
Original file line numberDiff line numberDiff line change
@@ -1463,15 +1463,6 @@
14631463
<data name="AvoidStringBuilderPInvokeParametersTitle" xml:space="preserve">
14641464
<value>Avoid 'StringBuilder' parameters for P/Invokes</value>
14651465
</data>
1466-
<data name="AvoidAssemblyLocationInSingleFileTitle" xml:space="preserve">
1467-
<value>Avoid using accessing Assembly file path when publishing as a single-file</value>
1468-
</data>
1469-
<data name="AvoidAssemblyLocationInSingleFileMessage" xml:space="preserve">
1470-
<value>'{0}' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.</value>
1471-
</data>
1472-
<data name="AvoidAssemblyGetFilesInSingleFileMessage" xml:space="preserve">
1473-
<value>'{0}' will throw for assemblies embedded in a single-file app</value>
1474-
</data>
14751466
<data name="PlatformCompatibilityOnlySupportedCsReachableMessage" xml:space="preserve">
14761467
<value>This call site is reachable on: {2}. '{0}' is only supported on: {1}.</value>
14771468
<comment>This call site is reachable on: 'windows' all versions.'SupportedOnWindowsUnsupportedFromWindows2004()' is only supported on: 'windows' 10.0.2004 and before</comment>

‎src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/Publish/AvoidAssemblyLocationInSingleFile.cs

-161
This file was deleted.

‎src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.cs.xlf

-15
Original file line numberDiff line numberDiff line change
@@ -47,21 +47,6 @@
4747
<target state="translated">Literály řetězců atributů by se měly správně parsovat</target>
4848
<note />
4949
</trans-unit>
50-
<trans-unit id="AvoidAssemblyGetFilesInSingleFileMessage">
51-
<source>'{0}' will throw for assemblies embedded in a single-file app</source>
52-
<target state="translated">Pro sestavení vložená do aplikace s jedním souborem {0} vyvolá výjimku.</target>
53-
<note />
54-
</trans-unit>
55-
<trans-unit id="AvoidAssemblyLocationInSingleFileMessage">
56-
<source>'{0}' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.</source>
57-
<target state="translated">Pro sestavení vložená do aplikace s jedním souborem {0} vždy vrátí prázdný řetězec. Pokud se cesta k adresáři aplikace vyžaduje, zvažte možnost zavolat System.AppContext.BaseDirectory.</target>
58-
<note />
59-
</trans-unit>
60-
<trans-unit id="AvoidAssemblyLocationInSingleFileTitle">
61-
<source>Avoid using accessing Assembly file path when publishing as a single-file</source>
62-
<target state="translated">Při publikování jednoho souboru nepoužívat přístup k cestě souboru sestavení</target>
63-
<note />
64-
</trans-unit>
6550
<trans-unit id="AvoidStringBuilderPInvokeParametersDescription">
6651
<source>Marshalling of 'StringBuilder' always creates a native buffer copy, resulting in multiple allocations for one marshalling operation.</source>
6752
<target state="translated">Zařazením parametru StringBuilder se vždy vytvoří kopie nativní vyrovnávací paměti, která bude mít za následek vícenásobné přidělení pro jednu operaci zařazování.</target>

‎src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.de.xlf

-15
Original file line numberDiff line numberDiff line change
@@ -47,21 +47,6 @@
4747
<target state="translated">Attributzeichenfolgenliterale müssen richtig analysiert werden</target>
4848
<note />
4949
</trans-unit>
50-
<trans-unit id="AvoidAssemblyGetFilesInSingleFileMessage">
51-
<source>'{0}' will throw for assemblies embedded in a single-file app</source>
52-
<target state="translated">"{0}" wird für Assemblys ausgelöst, die in einer Einzeldatei-App eingebettet sind.</target>
53-
<note />
54-
</trans-unit>
55-
<trans-unit id="AvoidAssemblyLocationInSingleFileMessage">
56-
<source>'{0}' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.</source>
57-
<target state="translated">"{0}" gibt immer eine leere Zeichenfolge für Assemblys zurück, die in einer Einzeldatei-App eingebettet sind. Wenn der Pfad zum App-Verzeichnis erforderlich ist, sollten Sie "System.AppContext.BaseDirectory" aufrufen.</target>
58-
<note />
59-
</trans-unit>
60-
<trans-unit id="AvoidAssemblyLocationInSingleFileTitle">
61-
<source>Avoid using accessing Assembly file path when publishing as a single-file</source>
62-
<target state="translated">Zugriff auf den Assemblydateipfad beim Veröffentlichen als Einzeldatei vermeiden</target>
63-
<note />
64-
</trans-unit>
6550
<trans-unit id="AvoidStringBuilderPInvokeParametersDescription">
6651
<source>Marshalling of 'StringBuilder' always creates a native buffer copy, resulting in multiple allocations for one marshalling operation.</source>
6752
<target state="translated">Beim Marshalling von "StringBuilder" wird immer eine native Pufferkopie erstellt, sodass mehrere Zuordnungen für einen Marshallingvorgang vorhanden sind.</target>

‎src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.es.xlf

-15
Original file line numberDiff line numberDiff line change
@@ -47,21 +47,6 @@
4747
<target state="translated">Los literales de cadena de atributo se deben analizar correctamente</target>
4848
<note />
4949
</trans-unit>
50-
<trans-unit id="AvoidAssemblyGetFilesInSingleFileMessage">
51-
<source>'{0}' will throw for assemblies embedded in a single-file app</source>
52-
<target state="translated">Se iniciará "{0}" para los ensamblados insertados en una aplicación de un solo archivo.</target>
53-
<note />
54-
</trans-unit>
55-
<trans-unit id="AvoidAssemblyLocationInSingleFileMessage">
56-
<source>'{0}' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.</source>
57-
<target state="translated">"{0}" devuelve siempre una cadena vacía para los ensamblados insertados en una aplicación de un solo archivo. Si se necesita la ruta de acceso al directorio de la aplicación, considere la posibilidad de llamar a "System.AppContext.BaseDirectory".</target>
58-
<note />
59-
</trans-unit>
60-
<trans-unit id="AvoidAssemblyLocationInSingleFileTitle">
61-
<source>Avoid using accessing Assembly file path when publishing as a single-file</source>
62-
<target state="translated">Evite usar la ruta de acceso al archivo de ensamblado al publicar como único archivo</target>
63-
<note />
64-
</trans-unit>
6550
<trans-unit id="AvoidStringBuilderPInvokeParametersDescription">
6651
<source>Marshalling of 'StringBuilder' always creates a native buffer copy, resulting in multiple allocations for one marshalling operation.</source>
6752
<target state="translated">Al serializar "StringBuilder" siempre se crea una copia del búfer nativo, lo que da lugar a varias asignaciones para una operación de serialización.</target>

‎src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.fr.xlf

-15
Original file line numberDiff line numberDiff line change
@@ -47,21 +47,6 @@
4747
<target state="translated">Les littéraux de chaîne d'attribut doivent être analysés correctement</target>
4848
<note />
4949
</trans-unit>
50-
<trans-unit id="AvoidAssemblyGetFilesInSingleFileMessage">
51-
<source>'{0}' will throw for assemblies embedded in a single-file app</source>
52-
<target state="translated">'{0}' lèvera une exception pour les assemblys incorporés dans une application monofichier</target>
53-
<note />
54-
</trans-unit>
55-
<trans-unit id="AvoidAssemblyLocationInSingleFileMessage">
56-
<source>'{0}' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.</source>
57-
<target state="translated">'{0}' retourne toujours une chaîne vide pour les assemblys incorporés dans une application monofichier. Si le chemin du répertoire d'application est nécessaire, appelez 'System.AppContext.BaseDirectory'.</target>
58-
<note />
59-
</trans-unit>
60-
<trans-unit id="AvoidAssemblyLocationInSingleFileTitle">
61-
<source>Avoid using accessing Assembly file path when publishing as a single-file</source>
62-
<target state="translated">Évitez d'utiliser l'accès du chemin du fichier d'assembly lors de la publication en tant qu'application monofichier</target>
63-
<note />
64-
</trans-unit>
6550
<trans-unit id="AvoidStringBuilderPInvokeParametersDescription">
6651
<source>Marshalling of 'StringBuilder' always creates a native buffer copy, resulting in multiple allocations for one marshalling operation.</source>
6752
<target state="translated">Le marshaling de 'StringBuilder' crée toujours une copie de la mémoire tampon native, ce qui entraîne plusieurs allocations pour une seule opération de marshaling.</target>

‎src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/xlf/MicrosoftNetCoreAnalyzersResources.it.xlf

-15
Original file line numberDiff line numberDiff line change
@@ -47,21 +47,6 @@
4747
<target state="translated">I valori letterali stringa dell'attributo devono essere analizzati correttamente</target>
4848
<note />
4949
</trans-unit>
50-
<trans-unit id="AvoidAssemblyGetFilesInSingleFileMessage">
51-
<source>'{0}' will throw for assemblies embedded in a single-file app</source>
52-
<target state="translated">'{0}' verrà generato per gli assembly incorporati in un'app a file singolo</target>
53-
<note />
54-
</trans-unit>
55-
<trans-unit id="AvoidAssemblyLocationInSingleFileMessage">
56-
<source>'{0}' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.</source>
57-
<target state="translated">'{0}' restituisce sempre una stringa vuota per gli assembly incorporati in un'app a file singolo. Se il percorso della directory app è necessario, provare a chiamare 'System.AppContext.BaseDirectory'.</target>
58-
<note />
59-
</trans-unit>
60-
<trans-unit id="AvoidAssemblyLocationInSingleFileTitle">
61-
<source>Avoid using accessing Assembly file path when publishing as a single-file</source>
62-
<target state="translated">Evitare l'accesso al percorso del file di assembly quando si esegue la pubblicazione come file singolo</target>
63-
<note />
64-
</trans-unit>
6550
<trans-unit id="AvoidStringBuilderPInvokeParametersDescription">
6651
<source>Marshalling of 'StringBuilder' always creates a native buffer copy, resulting in multiple allocations for one marshalling operation.</source>
6752
<target state="translated">Il marshalling di 'StringBuilder' crea sempre una copia del buffer nativo, di conseguenza vengono generate più allocazioni per una singola operazione di marshalling.</target>

0 commit comments

Comments
 (0)