Using set and get in C Sharp

[complete]

What is the point of using set and get in C Sharp?
It seems variables are used differently in this language than in C++.
For some reason, you have to have a static variable defined like this:

public static uint Somenum
{
   set { m_somenum = value; }
   get { return m_somenum; }
}

and prior to this declaration, you need to have this:
public uint m_sumenum;
This seems to be the only way to expose a member of a class to other classes in C#.
The problem is that I seem to be doing this improperly because I get a compile error:
An object reference is required for the non-static field, metod, or property '.......m_somenum"
I think I see the problem. The problem is that I cannot use a static varable like this.
So you have to instantiate the class in order to set these members of the class.
So how would you do the equivalent of a global class in C Sharp?
Would I do it something like this:

public clase SomeClass
{
    SomeClass someclass = new SomeClass();
 public static uint Somenum
 {
    set { m_somenum = value; }
    get { return m_somenum; }
 }
}

Or perhaps this "new" needs to be outside of the class in order to work. So my next question is this. How and where would that command be such that it the internal set methods could be accessed by the other classes in the code?

[vekipeki]

Please use CODE tags when posting. You should read the Posting guidelines before posting. Although the link seems to be broken right now? :)

The problem is that you are accessing a non-static field in a static property. It your property must be static, the your backing field must also be static.

private static int _number;
public static int Number
{
     get { return _number; }
     set { _number = value; }
}
 

Note that the _number field is private and static, accessible only withing the class containing it, while Number field is public, and exposed to the rest of the world.

For example, by using only a 'get' accessor, you can make your property read-only:

private static int _number;
public static int Number
{
     get { return _number; } // there is no 'set' accessor
}
 

[tlhintoq]

Get and Set can also be used to map a variable in one form or chunk of code to something else. In this example a form uses a local variable for preferences, but it is really just passing through the program level preference object (PrefObj)

        PrefObj myPreferences { get { return Program.myPrefs; } }
 

Instead of using 100 references to Program.myPrefs in this form we only make one. The form only has references to the local variable 'myPreferences'. If you decide later that the preferences will come from someplace else, you only have to make 1 code change, not 100.

Get and Set also can run code. They can be used for range checking and help avoid nulls being passed around

 
string bob = string.empty;
 public string RangeCheck
        {
            get 
            { 
                if (string.IsNullOrEmpty(bob)) return "Not yet set.";
                else return bob;
            }
            set { bob = value; }
        }
 

An empty field in a form looks like you are missing data. A field that clearly states "Not set" doesn't look like a bug.

You could apply this to integers as well. If someone tries to set a value to 500, but your program expects or requires a maximum of no more than 100...

 
int bob = 0;
 public int RangeCheck
        {
            get 
            { 
                return bob;
            }
            set 
            { 
                  if (value > 100) bob = 100;
                  if (value < 1) bob = 1;  
             }
        }
 

Or maybe you want your code to be smart enough to actually react to values being set. In this example, when the value is set we also run the method that saves our values then we update our display.

        public string RangeCheck
        {
            get 
            { 
                if (string.IsNullOrEmpty(bob)) return "Not yet set.";
                else return bob;
            }
            set { bob = value; SaveMethod(); UpdateDisplay(); }
        }
 

Now our code is a little smarter and a lot easier to maintain. We don't have to call the save and update methods from all 100 places we set this value. Just setting the value will do it for us, every time, every place. Giving us consistent behavior with less work.