Home > Articles > Programming > C#

The New nameof Expressions in C# 6: Painless Conversion of Symbols to Strings

Translating symbol names into text is common in modern code. The task isn't exactly odious, but it still takes time, it's tedious, and it's easy to make mistakes. Bill Wagner, author of Effective C#: 50 Specific Ways to Improve Your C#, Second Edition, happily skips all that work (and the associated runtime costs) with the help of the new nameof expression in C# 6.
Like this article? We recommend

One of the more specific of the new features in C# 6, the nameof expression replaces a C# symbol with the string representation of that symbol. Many of the idioms we use in modern development—reflection, late binding, wire-transfer protocols like JSON, logging scenarios—require us to translate symbol names into text. Copying the symbol name and putting it inside quotes to create a string; it's so easy that we do it without thinking—and that's the problem. When we write code without thinking, we make mistakes. Sometimes we catch those mistakes immediately. Sometimes we catch them with tests. And sometimes we don't catch them until after the product ships.

In previous versions of C#, options were limited. We copied symbol names, or we wrote dynamic code that used expressions and reflection to find the name of a symbol. That dynamic code was error-prone and came with significant runtime performance costs. The Windows 8 Store templates used the CallerMemberName attribute to build a reusable feature that would raise the correct PropertyChanged events in a view. Even this had runtime costs.

Overall, we expended a lot of brainpower to convert C# symbols to strings. All those different techniques used a runtime conversion, and therefore came with significant runtime costs. Converting symbols to strings started to look like a great language feature.

Introducing nameof

The new nameof expression in C# 6 addresses these concerns. It takes an expression and evaluates to the string representation of the local name of that expression. The canonical example is raising the PropertyChanged event in a class that implements INotifyPropertyChanged:

public class Person : INotifyPropertyChanged
    public string FirstName
            return firstName;
            if (value != firstName)
                firstName = value;
                    new PropertyChangedEventArgs(nameof(FirstName)));
    private string firstName;

    public event PropertyChangedEventHandler PropertyChanged;

    // more elided

In the example above, the nameof expression generates the string used in the constructor to the PropertyChangedEventArgs object. (Notice that I'm also using the new ?. operator I discussed in "Using the New Null Conditional Operator in C# 6.") Using the nameof operator eliminates any chance of mistyping the property name. If I mistype the symbol name, the compiler complains, and I must fix it. The symbol has semantic meaning.

Making the compiler prevent you from mistyping a property name is only the beginning. Equally important, any static analysis tools you use can also benefit from having the symbol information, rather than just a text string. Figure 1 shows the code from the preceding example, after I've used the Rename refactoring (F2) to change the property name from "FirstName" to "GivenName". Notice that the refactoring tool finds and highlights the symbol in the nameof expression. Because it's a valid C# symbol, not a string literal, the symbol participates in all of the analysis.

The refactoring tools and the compiler validation show why this feature is important for modern developers. The size of our modern codebases mandates using software tools to help us manage our software development activities. Those tools often rely on static analysis of our software to understand our code and to suggest where we may have made mistakes.

Also, unlike earlier attempts to convert symbols to human-readable text, the nameof expression involves no runtime cost. The nameof expression is evaluated at compile time, and the generated code contains the replacement text.

Valid nameof Expressions

In the examples to this point, I've used the property name as the expression. You can qualify the expression with the type name, if that's more readable to you:

    new PropertyChangedEventArgs(nameof(Person.FirstName)));

The compiler generates text for the rightmost name. In this case, it generates "FirstName", not "Person.FirstName". It follows that you can use the fully qualified name, including any namespaces:

    new PropertyChangedEventArgs(nameof(ExampleNamespace.ExampleCode.Person.FirstName)));

The result is still the string "FirstName".

The argument to nameof must resolve to a named expression. I've used property names in the examples so far, but several other named expressions are also valid. You can use local variables. Non-generic class names, struct names, and delegate types are also legal.

Anonymous types, numeric literals, and string literals, on the other hand, are not legal. They produce CS 8081, "Expression does not have a name". The same is true for lambda expressions.

Generics are an interesting case. You can use closed generic types anywhere, if every type parameter has been specified. For example:


This expression evaluates to "List". The type parameters are omitted from the generated string.

You can use a generic type definition (where the type parameters are placeholders, such as in List<T>) only inside a generic type definition that has the same named-type parameter. I couldn't use List<T> inside the Person class shown in my examples, but I could use IEnumerable<T> inside a class like List<T>, where the 'T' type parameter has been declared.

Those rules might seem a bit hard to comprehend when written in English, but they're reasonable as you write code. Just remember that the argument to the nameof expression must have a name, and the symbol must resolve at compile time. Just as you can't declare a variable of the type List<T> outside a generic definition (where T is a type parameter), you can't use List<T> in a nameof expression when T has not been defined.

Some Initial Guidance on nameof, and a Look into the Future

As with the other new features I've discussed in previous articles, I've made it a habit to use the new feature in new code that I write. It helps me to create correct code and, in this case, to avoid simple mistakes that come from translating program symbols to text by hand.

However, with this feature, I'm not updating my existing code very aggressively. I don't update existing code with the nameof expression unless I already have tests surrounding that code, to verify that its behavior is correct. It may seem a reasonable assumption to correct strings that you see in code. But in many cases a text string may be different from a program symbol name for good reason. It may be easy to make all those changes. However, be careful to make sure that the text is intended to match the symbol. It may be a coincidence, rather than part of a design. That means being cautious about any changes.

I'm more excited about what might happen in future releases. In Visual Studio 2015, any of the tools and features work with C#—and only C#. In future releases, I'd like to see the tools extend to places where C# interacts with other languages. This could be a huge help in XAML bindings, or bindings in Razor syntax. One day, maybe it could even extend to matching names in C# with bindings in view models in an Angular-based application. None of these features are promised, but they would be welcome.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020