Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 631997
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T20:01:40+00:00 2026-05-13T20:01:40+00:00

MSDN defines System.Enum as an abstract class: [SerializableAttribute] [ComVisibleAttribute(true)] public abstract class Enum :

  • 0

MSDN defines System.Enum as an abstract class:

[SerializableAttribute]
[ComVisibleAttribute(true)]
public abstract class Enum : ValueType, IComparable, IFormattable, IConvertible

And also MSDN make such statement about abstract class:

An abstract class cannot be
instantiated. The purpose of an
abstract class is to provide a common
definition of a base class that
multiple derived classes can share.

But I simply cannot derive from System.Enum. According to Jeffery Richter in his book “CLR via C#”, it is C# compiler that forbid that derivation.

And I checked System.Enum’s members, most of them are static, which is reasonable for it cannot be instantiated and static methods don’t need an object instance to invoke. But there are also some instance methods, such a GetHashCode() and GetTypeCode().

So, my first question is, if System.Enum cannot
be instantiated or derived, how could
these instance methods be invoked?
Isn’t this some kind of a paradox?

I know I could use the following
approach to invoke these instance
methods, but why? Is there some kind
of System.Enum or derived type object
instance
created? When? and by whom?

public enum Days:byte { Saturday, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday };
Days d = Days.Friday;
d.GetTypeCode();
d.GetHashCode();
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T20:01:40+00:00Added an answer on May 13, 2026 at 8:01 pm

    You can derive from Enum, e.g.

    public enum MyEnum
    {
        // ...
    }
    

    Will be compiled down to something like:

    .class public auto ansi sealed MyEnum
        extends System.Enum
    {
        // ...
    }
    

    The restriction the C# compiler places is that it won’t let you write the derivation manually, but instead requires you to use the enum keyword when declaring the type.

    As to why this is… my guess is because enumerations are a bit weird in the CLR. For example, the ValueType and Enum base types are both themselves reference types, not value types. There’s a whole bunch of magic going on under the covers, and if you force the use of a keyword and prevent derivation from the magic base class, then you are keeping your intent separate from the magic.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

MSDN says that public static members of System.Windows.Application are thread safe. But when I
MSDN defines System.Predicate this way : Represents the method that defines a set of
Microsoft shows how to create a dynamic class here: http://msdn.microsoft.com/en-us/library/system.reflection.emit.modulebuilder(v=vs.71).aspx This defines a custom
The base class WebPart has a property defined like this: [WebBrowsable(true)] public virtual string
MSDN states that String.Intern retrieves the system's reference to the specified String and String.IsInterned
In the MSDN documentation, System.Reflection.Assembly has a property called CodeBase which is defined as
The MSDN page for System.Windows.Application lists a property called StartupUri . However, this MSDN
According to http://msdn.microsoft.com/en-us/library/ms633500(v=vs.85).aspx I define FindWindowEx function. using System.Runtime.InteropServices; [DllImport(user32.dll, CharSet=CharSet.Unicode)] static extern IntPtr
I've got a property contained in a class for example public class Greeter {
In http://msdn.microsoft.com/en-us/library/system.security.cryptography.pkcs(VS.85).aspx we can see that the following digital signature attributes are defined: Pkcs9ContentType

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.