Where/what is the private variable in auto-implemented property?

Question

There is no (explicit) reference to a firstName private variable which FirstName is supposed to be hiding. Could you explain how this works? I assume there is some private variable that is being getted and setted. Thanks.

// auto-implemented property FirstName
public string FirstName { get; set; }

Answer 1

Basically the compiler converts your code into something like this:

private string <__>firstName;

public string FirstName
{
    get { return <__>firstName; }
    set { <__>firstName = value; }
}

That's unlikely to be the exact name, but the use of angle brackets in the name is important - because it makes it an unspeakable name . (That's unofficial terminology, but widely used - I don't know whether Eric Lippert actually coined it, or whether he was just the first person to use it in something I read.) It's a name which isn't a valid C# identifier, but which the CLR is quite happy with. That has two benefits:

• The compiler doesn't need to worry about naming collisions with your identifiers
• The compiler doesn't need to worry about whether you're trying to refer to the field in your own code - you can't, because the name is unspeakable!

It uses the same technique for all kinds of other generated code - anonymous types, anonymous functions, iterator blocks etc.

Answer 2

yes, the compiler creates a private, anonymous backing field that can only be accessed through the property's get and set accessors. (c) msdn

EDIT:
When you define a property, compiler will emit 2 methods: get_XXX and set_XXX . When the C# compiler sees code that's trying to get or set a property, the compiler actually emits a call to one of these methods. (c) "CLR via C#"

Answer 3

C# compiler creates the backing store field behind the scenes, you can try to decompile it. using Reflector. you will come to know, how it's created backing fields . here's the same reply

MSDN Auto-Implemented property

Auto implemented property

Answer 4

The other guys have answered this, but a little further info ... you can find the backing field at run time using reflection. Look for fields with naming like << PropertyName>>k__BackingField.

Another post that may help:

• Does an abstract property create a private backing field?