Timeline for Am I understanding the new C# naming conventions right?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 8, 2021 at 15:26 | comment | added | 17 of 26 | Using an underscore prefix is no different than applying PascalCase vs camelCase for a name. | |
| Sep 28, 2021 at 14:14 | comment | added | Martin Maat | @DavidArno Resharper is not Microsoft, this is about Microsoft recommendations. Third party add-ons are not relevant. | |
| Sep 28, 2021 at 14:04 | comment | added | David Arno | @MartinMaat, R# is ReSharper, a VS plugin that massively expands VS's C# capabilities. There's not many C# devs that I know of to be honest that haven't heard of ReSharper. So yes, this is absolutely about C# ;) | |
| Sep 28, 2021 at 13:20 | comment | added | Martin Maat | @DavidArno How interesting. However, this is about C# exclusively, hence the label. | |
| Sep 28, 2021 at 6:10 | comment | added | David Arno | Sorry but I have to downvote this as it is factually incorrect. R# out of the box for example recommends PascalCase for static fields. It’s a very common standard as far as I was aware until now. | |
| Sep 27, 2021 at 20:30 | comment | added | Evorlor | Thank you for your answer. I was moreso asking about internal fields, where I have always used PascalCase in the past, instead of _camelCase. | |
| Sep 27, 2021 at 19:34 | comment | added | davidbak | Not just for type safety. Also for situations pre-IDE where you couldn't just hover over a variable and find out its access (or other attributes). It was a marker that a field was private, or static, which you might have wanted to know without going to find the decl. (It was used quite frequently in C++ which is pretty type-safe, and was even then (compared to the alternatives)). | |
| Sep 27, 2021 at 18:34 | history | answered | Martin Maat | CC BY-SA 4.0 |