Get string truncated to max length

There is an inconsistency - negative values of maxLength would be forgiven for value being null, but cause an exception for every other input (since Substring would throw an ArgumentOutOfRangeException).

There's two possible approaches that remove this inconsistency - fail fast

public static string WithMaxLength(this string value, int maxLength)
{
    if (maxLength < 0)
    {
       throw new ArgumentOutOfRangeException("maxLength must be equal to or greater than 0");
    }
    // ...

Or ignore negative values for both cases:

public static string WithMaxLength(this string value, int maxLength)
{
    if (value == null)
    {
        return null;
    }
    if (maxLength < 0)
    {
        return "";
    }
    return value.Substring(0, Math.Min(value.Length, maxLength));
}

Personally I'd be inclined to choose the former - maxLength being smaller than 0 could be a symptom of a problem (implementation error) that we wouldn't want to sweep under the carpet. It's also consistent with the way Substring itself behaves.

Well, Mat's Mug already gave the only improvement for the code in the extension-method I could find, using the conditional-member-access operator.

Aside from that, there's only the methods name. Which is far too long and awkward.
Truncate has a nice ring to it, and everybody understands it.

public static class StringExtensions
{
    public static string Truncate(this string value, int maxLength)
    {
        return value?.Substring(0, Math.Min(value.Length, maxLength));
    }
}

Per Mat's Mug's answer:

I'd try to find a name that better indicates that truncation will occur when value is longer than maxLength... but WithMaxLength isn't a bad name.

I disagree that the method's name is the place to do this. It's not. And WithMaxLength is a perfectly fine name.

But... that truncation occurs should be documented. I'm not sure what's available exactly for C#, but most all languages have a format for showing in-IDE documentation.

I've been told the C# version of this looks something like this:

<summary>
This function does something.
<param name="string">The string to do things with</param>
</summary>

We should certainly add this sort of documentation to our method to be clear on exactly what happens with the method. I think any other sort of name for the method itself goes beyond to descriptive and ventures into the realm of too verbose (and this is coming from someone who writes Objective-C...).