1. C#自定义异常完全指南在C#开发中异常处理是保证程序健壮性的关键机制。当.NET框架提供的标准异常类型无法准确描述特定业务场景的错误时自定义异常就成为了专业开发者的必备技能。上周我在处理一个金融交易系统时就遇到了标准异常无法清晰表达账户余额不足业务规则的困境——系统抛出InvalidOperationException虽然能中断流程但无法携带具体的差额数据导致前端无法展示友好的提示信息。2. 自定义异常的核心实现2.1 基础继承结构所有C#异常都继承自System.Exception基类。创建自定义异常时我们通常采用三级继承体系public class InsufficientBalanceException : InvalidOperationException { public decimal CurrentBalance { get; } public decimal RequiredAmount { get; } public InsufficientBalanceException(decimal current, decimal required) : base($当前余额{current}不足需要{required}) { CurrentBalance current; RequiredAmount required; } }这种设计遵循了以下原则继承自最接近语义的框架异常如InvalidOperationException包含完整的错误上下文数据当前余额和所需金额提供人性化的错误消息模板2.2 序列化支持考虑跨进程/机器通信场景时必须实现序列化[Serializable] public class InsufficientBalanceException : InvalidOperationException { // 新增序列化构造器 protected InsufficientBalanceException(SerializationInfo info, StreamingContext context) : base(info, context) { CurrentBalance info.GetDecimal(nameof(CurrentBalance)); RequiredAmount info.GetDecimal(nameof(RequiredAmount)); } public override void GetObjectData(SerializationInfo info, StreamingContext context) { base.GetObjectData(info, context); info.AddValue(nameof(CurrentBalance), CurrentBalance); info.AddValue(nameof(RequiredAmount), RequiredAmount); } }3. 高级设计模式3.1 异常代码体系企业级应用建议采用标准化错误代码public enum ErrorCode { BalanceInsufficient 1001, AccountFrozen 1002 } public class BusinessException : Exception { public ErrorCode ErrorCode { get; } public BusinessException(ErrorCode code, string message) : base(message) ErrorCode code; }3.2 异常过滤器C# 6.0引入的异常过滤器可以优化处理逻辑try { ProcessTransaction(); } catch (BusinessException ex) when (ex.ErrorCode ErrorCode.BalanceInsufficient) { // 专用于余额不足的处理 ShowAlert($操作失败{ex.Message}); }4. 性能优化要点4.1 StackTrace生成控制异常实例化时会自动捕获堆栈跟踪可通过以下方式优化public class LightweightException : Exception { public override string StackTrace null; public LightweightException(string message) : base(message) { } }4.2 异常池技术高频场景可考虑对象池模式public static class ExceptionPoolT where T : Exception, new() { private static readonly ConcurrentBagT _pool new(); public static T Rent() _pool.TryTake(out var item) ? item : new T(); public static void Return(T item) _pool.Add(item); }5. 实战中的黄金法则语义明确原则异常类型名必须准确描述错误性质如NetworkTimeoutException比TimeoutException更明确上下文完整原则异常对象应包含诊断所需的全部数据例如public class DatabaseConflictException : Exception { public string TableName { get; } public object EntityId { get; } public string ConflictColumn { get; } }处理标记原则对已处理的异常设置IsHandled标记catch (Exception ex) { ex.Data[IsHandled] true; // 处理逻辑... }6. 诊断增强技巧6.1 异常链可视化public static string FormatExceptionChain(this Exception ex) { var sb new StringBuilder(); while (ex ! null) { sb.AppendLine($[{ex.GetType().Name}] {ex.Message}); if (ex is BusinessException bex) sb.AppendLine($ErrorCode: {bex.ErrorCode}); ex ex.InnerException; } return sb.ToString(); }6.2 智能日志记录结合Serilog等工具实现结构化日志catch (Exception ex) { Log.ForContext(ExceptionData, ex.ToDictionary()) .Error(ex, 处理交易时发生异常); } public static Dictionarystring, object ToDictionary(this Exception ex) { var dict new Dictionarystring, object { [Type] ex.GetType().Name, [Message] ex.Message }; if (ex is BusinessException bex) dict[ErrorCode] bex.ErrorCode; return dict; }7. 单元测试策略7.1 异常断言[TestMethod] public void Transfer_ShouldThrowInsufficientBalanceException() { var account new Account(balance: 100); Assert.ThrowsExceptionInsufficientBalanceException( () account.Transfer(amount: 200)); // 验证异常属性 var ex Assert.ThrowsExceptionInsufficientBalanceException( () account.Transfer(200)); Assert.AreEqual(100m, ex.CurrentBalance); Assert.AreEqual(200m, ex.RequiredAmount); }7.2 异常序列化测试[TestMethod] public void Exception_ShouldSerializeCorrectly() { var original new InsufficientBalanceException(100m, 200m); var formatter new BinaryFormatter(); using var stream new MemoryStream(); formatter.Serialize(stream, original); stream.Position 0; var deserialized (InsufficientBalanceException)formatter.Deserialize(stream); Assert.AreEqual(original.CurrentBalance, deserialized.CurrentBalance); Assert.AreEqual(original.RequiredAmount, deserialized.RequiredAmount); }8. 框架集成实践8.1 ASP.NET Core中间件public class ExceptionHandlingMiddleware { public async Task InvokeAsync(HttpContext context) { try { await _next(context); } catch (BusinessException ex) { context.Response.StatusCode 400; await context.Response.WriteAsJsonAsync(new { Code ex.ErrorCode, ex.Message }); } catch (Exception ex) { context.Response.StatusCode 500; await context.Response.WriteAsJsonAsync(new { Code SYSTEM_ERROR, Message 系统繁忙请稍后重试 }); _logger.LogError(ex, 未处理的系统异常); } } }8.2 WCF错误契约[DataContract] public class FaultInfo { [DataMember] public string Code { get; set; } [DataMember] public string Message { get; set; } } [ServiceContract] public interface IAccountService { [OperationContract] [FaultContract(typeof(FaultInfo))] void Transfer(decimal amount); } public class AccountService : IAccountService { public void Transfer(decimal amount) { try { /* 业务逻辑 */ } catch (BusinessException ex) { throw new FaultExceptionFaultInfo( new FaultInfo { Code ex.ErrorCode.ToString(), Message ex.Message }); } } }9. 性能对比数据通过BenchmarkDotNet测试不同实现方式的性能差异实现方式平均耗时(ns)内存分配标准异常1,2001KB无堆栈跟踪异常350512B异常池复用1500B返回错误码(对比组)500B实际项目应在可维护性和性能间取得平衡关键路径代码可考虑异常池方案10. 领域特定异常设计10.1 金融领域示例public abstract class FinancialException : Exception { public string AccountNumber { get; } public DateTimeOffset OccurredAt { get; } DateTimeOffset.UtcNow; protected FinancialException(string account, string message) : base(message) AccountNumber account; } public class AntiMoneyLaunderingException : FinancialException { public decimal SuspiciousAmount { get; } public AntiMoneyLaunderingException(string account, decimal amount) : base(account, $账户{account}交易金额{amount}触发反洗钱规则) { SuspiciousAmount amount; } }10.2 IoT设备异常public class DeviceException : Exception { public string DeviceId { get; } public DeviceStatus Status { get; } public DeviceException(string deviceId, DeviceStatus status, string message) : base(message) { DeviceId deviceId; Status status; } } public enum DeviceStatus { Offline 0, Busy 1, Fault 2 }在最近参与的工业物联网项目中我们通过设备异常体系将故障处理时间缩短了40%关键是通过异常类型就能立即判断是网络问题还是设备硬件故障