Home/ Questions/Q 4100212
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T20:32:15+00:00

In this post Jon Skeet pointed out that the following code should be changed

  • 0

In this post Jon Skeet pointed out that the following code should be changed to conform with the .NET naming conventions. Doing that would also decrease the amount of noise in the code.

Enum enUtilityTypeDetailStudentEntryWorkflow As Integer
    enUTDSEW_Default = 379
    enUTDSEW_ApplicantRecordBook = 380
End Enum

I must admit, I was pretty much like a sheep and was following what others have done before me. I thought the prefix did not look right and then to have it twice did not make sense either.
After looking at a couple of .NET Framework examples, it looks like this would be closer to the standard.

Enum StudentEntryWorkflow As Integer
    Default = 379
    ApplicantRecordBook = 380
End Enum

Am I on the mark with using these names?
Any other suggestions or comments in general?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t know about standard, but using Hungarian notation on enums and enum values is not something I have seen before.

    Your second example is closer to the kind of code I normally see, so in that respect, yes, it is more standard.

    See section 8.2.3 on this guideline – pascal casing and no prefix/postfix.

    Guideline 16 of Section 2.1 of Lance Hunt’s C# coding standards also says to avoid prefixes and postfixes.

    I would say this is pretty universal – the point of having enums it to aid readability. Using prefixes and postfixed reduces readability and thus is pretty universally discouraged.

    • 0