Home/ Questions/Q 6535495
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T10:22:49+00:00

I work in a team of 20+ developers that includes a recent influx of

  • 0

I work in a team of 20+ developers that includes a recent influx of newer members. Our coding standards state that the .First() extension method for IEnumerable should never be used, and instead that we should always use FirstOrDefault() and check for a null return.

I appreciate that some members may want to get into a discussion about training, enforcing coding standards or unit tests to pick up such transgressions, but in principle is it possible to cause the attempted use to throw a compile-time error?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The best thing that you can do in terms of compile time help is:

    1. Make your OWN extension method called “First” that does nothing but throw an exception.

    2. Mark that method as “OBSOLETE” so that you get a compile-time warning.

    I think that’s the best you can do.

    (some comments mentioned concern about the namespace… you would simply use the same namespace as Microsoft does [System.Linq] so that the compiler sees both).

    • 0