Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    It all depends on whether you suspect users will be declaring using statements. If someone declares using System; then you don't need the System:: prefix for any class declared inside of it. Commented Jan 24, 2020 at 19:13
  • And this is all internal code? Sounds like System::Monitor would be preferred in that case. Commented Jan 24, 2020 at 19:36
  • @BerinLoritsch May be the other way round. If everything is called SystemThis, SystemThat then there is much more temptation to use "using System;". Commented Jan 24, 2020 at 23:07
  • This is called 'Smurf-naming', and a lot of people frown about it. Commented Jan 24, 2020 at 23:08
  • 3
    Does this answer your question? The problems with Avoiding Smurf Naming classes with namespaces Commented Jan 25, 2020 at 1:41