Syntactic refactor to C# standards.

[ferhatorjatsalo]

• Changed framework types to .NET types
• Namespace scope changed to standard
• Removed '_' prefix for some member variables
• Corrected usage of this keyword
• Removed .editorconfig file

[akihirvonen]

Should we also use the more explicit way here? Indicate somehow that this is a class/instance variable? That is, use this keyboard with the same reasoning as using base.

I think we should be consistent and select one of these ways:

1. Use the MS style
2. Use our own "better" style with a consistent way. Use both this and base (or neither of them).

[ferhatorjatsalo]

this is more universally recognized across programming languages, such as Java, C++ JS, Dart, Scala etc. Python and Swift use self, but this aligns better with broader conventions than underscores, which are specific to C#.

[akihirvonen]

Good reasoning. I usually prefer the language-specific way if there is one (like in Python). But I can see benefits on both sides.

[akihirvonen]

Even if using the PluginResources prefix is not mandatory, it's more expressive. So once again, do we want to be explicit or remove extra clutter?

Both are ok for me, but it would be good to select one way and stick with it.

[ferhatorjatsalo]

Defining explicitly PluginResources within PluginResources is redundant. You'd know the member var is within the static class anyway. If it was public, then it'd make more sense.

[akihirvonen]

I agree, the extra text can distract the reader. I remember fighting against this rule when I joined the LPS team :).