Summary
Two custom exception classes implement the obsolete ISerializable pattern inherited from .NET Framework, producing SYSLIB0051 warnings on every build:
ApiDoctor.Validation/Http/HttpParserRequestException.cs:46ApiDoctor.Validation/Params/PlaceholderValueNotFoundException.cs:46
Both have a constructor of the form:
```csharp
protected MyException(SerializationInfo info, StreamingContext context) : base(info, context)
```
Why this should be fixed
In .NET 8, BinaryFormatter and the ISerializable infrastructure were deprecated. This constructor is marked [Obsolete] via SYSLIB0051. The constructors are never called anywhere in the codebase — they exist solely to satisfy the old pattern.
Fix
Delete the protected serialization constructors from both classes. No callers need updating.
Summary
Two custom exception classes implement the obsolete
ISerializablepattern inherited from .NET Framework, producingSYSLIB0051warnings on every build:ApiDoctor.Validation/Http/HttpParserRequestException.cs:46ApiDoctor.Validation/Params/PlaceholderValueNotFoundException.cs:46Both have a constructor of the form:
```csharp
protected MyException(SerializationInfo info, StreamingContext context) : base(info, context)
```
Why this should be fixed
In .NET 8,
BinaryFormatterand theISerializableinfrastructure were deprecated. This constructor is marked[Obsolete]viaSYSLIB0051. The constructors are never called anywhere in the codebase — they exist solely to satisfy the old pattern.Fix
Delete the protected serialization constructors from both classes. No callers need updating.