为什么不:

string NormalizeLength(string value, int maxLength)
{
    //check String.IsNullOrEmpty(value) and act on it. 
    return value.PadRight(maxLength).Substring(0, maxLength);
}

即在事件值中。Length < maxLength填充空格到末尾或截断多余部分。

这是我通常使用的代码:

string getSubString(string value, int index, int length)
        {
            if (string.IsNullOrEmpty(value) || value.Length <= length)
            {
                return value;
            }
            System.Text.StringBuilder sb = new System.Text.StringBuilder();
            for (int i = index; i < length; i++)
            {
                sb.AppendLine(value[i].ToString());
            }
            return sb.ToString();
        }

另一个解决方案:

return input.Substring(0, Math.Min(input.Length, maxLength));

在。net 4.0中，你可以使用Take方法:

string.Concat(myString.Take(maxLength));

没有测试效率!

因为性能测试很有趣:(使用linqpad扩展方法)

var val = string.Concat(Enumerable.Range(0, 50).Select(i => i % 10));

foreach(var limit in new[] { 10, 25, 44, 64 })
    new Perf<string> {
        { "newstring" + limit, n => new string(val.Take(limit).ToArray()) },
        { "concat" + limit, n => string.Concat(val.Take(limit)) },
        { "truncate" + limit, n => val.Substring(0, Math.Min(val.Length, limit)) },
        { "smart-trunc" + limit, n => val.Length <= limit ? val : val.Substring(0, limit) },
        { "stringbuilder" + limit, n => new StringBuilder(val, 0, Math.Min(val.Length, limit), limit).ToString() },
    }.Vs();

截断法“明显”更快。# microoptimization

早期

truncate10 5788滴答流逝(0.5788 ms) [10K次，5.788E-05 ms /次] smart-trunc10 8206滴答流逝(0.8206 ms) [10K次，8.206E-05 ms /次] stringbuilder10 10557滴答流逝(1.0557 ms) [10K次，0.00010557 ms /次] concat10 45495滴答流逝(4.5495 ms) [10K次，0.00045495 ms /次] 时间流逝(7.2535 ms) [10K次，0.00072535 ms /次]

Late

truncate44 8835滴答流逝(0.8835 ms) [10K次，8.835E-05 ms /次] 13106滴答流逝(1.3106 ms) [10K次，0.00013106 ms /次] smart-trunc44 14821滴答流逝(1.4821毫秒)[10K次，0.00014821毫秒/次] 时间流逝(14.4324 ms) [10K次，0.00144324 ms /次] concat44 174610滴答流逝(17.461毫秒)[每10K次，0.0017461毫秒]

太长时间

smart-trunc64 6944滴答流逝(0.6944毫秒)[在10K次中，6.944E-05毫秒每] truncate64 7686滴答流逝(0.7686 ms) [10K次，7.686E-05 ms /次] stringbuilder64 13314滴答流逝(1.3314 ms) [10K次，0.00013314 ms /次] 时间流逝(17.7481 ms) [10K次，0.00177481 ms /次] concat64 241601滴答流逝(24.1601毫秒)[每10K次，0.00241601毫秒]

所有其他答案都没有考虑到Span的性能，它比。net中字符串类型的Substring的性能更好

如果你还不知道有一个版本的系统。内存(为以下情况提供了Span, ReadOnlySpan, Memory和ReadOnlyMemory:

这样的简单实现可以如下所示:

public static string Truncate(this string value, int maxLength)
{
    if (!string.IsNullOrEmpty(value) && value.Length > maxLength)
    {
        return value.AsSpan(0, maxLength).ToString(); /* Note the use of AsSpan instead of Substring. */
    }

    return value;
}

该方法理论上可以返回Span<char>，以避免使用Span<T>的ToString()成员分配新字符串。

The BCL itself internally uses Span's, ReadOnlySpan's, Memory's, and ReadOnlyMemory's where possible to avoid issues and to help optimize the code, especially when you compile arrays that are known at compile time and so using an property that returns that new'd up array as an ReadOnlySpan<byte> actually optimizes the code at runtime as then the JIT would not call memcpy on the data and instead uses it since it just returns a Span and as such is a window to the data that is already allocated ahead of time resulting in:

更少的分配。 更少的分配时间。 使代码总体上更快地使用。