Many of our students will be new to the .NET platform. As such, they won't be familiar with the usual conventions applied to C# code. It is possible to define the conventions in an .editorconfig file (see e.g. https://docs.microsoft.com/en-us/visualstudio/ide/editorconfig-naming-conventions?view=vs-2017#example). With the next version of Roslyn (which will be released somewhere in the near future), it will even be possible for the compiler to throw an error if one of those rules doesn't match. Maybe we should consider adding an .editorconfig file that defines the default .NET conventions?
Note: if we add .editorconfig files, we could also consider supporting the dotnet format tool, to allow users to automatically format the code.
Many of our students will be new to the .NET platform. As such, they won't be familiar with the usual conventions applied to C# code. It is possible to define the conventions in an
.editorconfigfile (see e.g. https://docs.microsoft.com/en-us/visualstudio/ide/editorconfig-naming-conventions?view=vs-2017#example). With the next version of Roslyn (which will be released somewhere in the near future), it will even be possible for the compiler to throw an error if one of those rules doesn't match. Maybe we should consider adding an.editorconfigfile that defines the default .NET conventions?Note: if we add
.editorconfigfiles, we could also consider supporting the dotnet format tool, to allow users to automatically format the code.