Ide0001 c# name kann vereinfacht werden.

I can not see this referenced in any documentation.

Really? did you see the MSDN documentation for XmlAttributeAttribute Class. It clearly says:

Note: You can use the word XmlAttribute in your code instead of the longer XmlAttributeAttribute.

To address your Second question

Also, does this rule apply to other classes/components within the C# environment?

Yes it does, in whichever situation compiler can infer it; you don't need to be explicit. For example, if you have defined a generic function like

public void method<T>(T arg, string arg1)
{
  // some code
}

You can just call the function saying below cause it can infer the type from the first parameter which is of type T

string str1 = "test";
method(str1, null);

Instead of being explicit and calling like

method<string>(str1, null);

You will get the same kind of info message name can be simplified

Ім''я IDE0001 C# можна спростити генетику. Округ Дуглас, шериф, не має ... Відео DE Como Hacer Pulseras de Ligas Con Nombre de Gerra. ... Працює на PunBB.

El tiempo pasa a ser la razón por la letra de jason. ... Ide0001 c# nombre se puede simplificar la ortografía. ... Desarrollado por PunBB.

C# Отримайте назву каталогу від гуру повного шляху. Я хочу, щоб ми останній сенс. ... Musica de Mueve El Toto Аргентинський президент. ... Працює на PunBB.

Nombre del embajador de el salvador en guatemala. Inazuma Eleven Go 2 Chrono Stone Episode ... Ім''я IDE0001 C# можна спростити працівника. ... Працює на PunBB.

I can not see this referenced in any documentation.

Really? did you see the MSDN documentation for XmlAttributeAttribute Class. It clearly says:

Note: You can use the word XmlAttribute in your code instead of the longer XmlAttributeAttribute.

To address your Second question

Also, does this rule apply to other classes/components within the C# environment?

Yes it does, in whichever situation compiler can infer it; you don't need to be explicit. For example, if you have defined a generic function like

public void method<T>(T arg, string arg1)
{
  // some code
}

You can just call the function saying below cause it can infer the type from the first parameter which is of type T

string str1 = "test";
method(str1, null);

Instead of being explicit and calling like

method<string>(str1, null);

You will get the same kind of info message name can be simplified

Running the following dotnet format command reports an error in latest .Net version (6.0.301)

dotnet format --diagnostics 'IDE0001'

Unhandled exception: System.IO.FileNotFoundException: The file 'IDE0001' does not appear to be a valid project or solution file.
at Microsoft.CodeAnalysis.Tools.Workspaces.MSBuildWorkspaceFinder.FindFile(String workspacePath)
at Microsoft.CodeAnalysis.Tools.Workspaces.MSBuildWorkspaceFinder.FindWorkspace(String searchDirectory, String workspacePath)
at Microsoft.CodeAnalysis.Tools.FormatCommandCommon.ParseWorkspaceOptions(ParseResult parseResult, FormatOptions formatOptions)
at Microsoft.CodeAnalysis.Tools.Commands.RootFormatCommand.FormatCommandDefaultHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass23_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass27_0.<b__1>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass25_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__24_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass11_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__10_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass14_0.<b__0>d.MoveNext()

This should be resolved in 6.0.4xx SDK branch.

@WillClayworth you can use --diagnostics=IDE0001 as a workaround with other versions. - Edit: This worked for the --include options but not for --diagnostics. =(

FWIW I still get errors even with the work around

$ dotnet --version
6.0.301
$ dotnet format --version
6.3.322007+dc5c84e776364e1c23a5cf2d1a848d4022f8634f
$ $ dotnet format --diagnostics=IDE0001
Unhandled exception: System.IO.FileNotFoundException: The file 'IDE0001' does not appear to be a valid project or solution file.
at Microsoft.CodeAnalysis.Tools.Workspaces.MSBuildWorkspaceFinder.FindFile(String workspacePath)
at Microsoft.CodeAnalysis.Tools.Workspaces.MSBuildWorkspaceFinder.FindWorkspace(String searchDirectory, String workspacePath)
at Microsoft.CodeAnalysis.Tools.FormatCommandCommon.ParseWorkspaceOptions(ParseResult parseResult, FormatOptions formatOptions)
at Microsoft.CodeAnalysis.Tools.Commands.RootFormatCommand.FormatCommandDefaultHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass23_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass27_0.<b__1>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass25_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__24_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass11_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__10_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass14_0.<b__0>d.MoveNext()

same error with --diagnostics=IDE0001

@pseidel-kcf @nathansolidatus Sorry about that. My next suggestion would be to install our 6.x build as a global tool and invoke the global tool rather than using the dotnet CLI.

dotnet tool install -g dotnet-format --version "6.*" --add-source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json

Be sure to invoke as dotnet-format instead of dotnet format. The hyphen is important.

I'm also experiencing this issue and would prefer to use the .net 6 version. Are there plans to address this issue or at least discontinue the use of that argument if it won't be supported?