Don't bother looping input streams in MimeParser benchmarks #1498
Annotations
1 error and 8 warnings
|
Run unit tests
Process completed with exit code 1.
|
|
Build solution:
MimeKit/Cryptography/CryptographyContext.cs#L737
Using member 'MimeKit.Cryptography.DefaultSecureMimeContext.DefaultSecureMimeContext()' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Uses Reflection to load System.Data.SQLite on Windows or Mono.Data.Sqlite on Linux / macOS.
|
|
Build solution:
UnitTests/Cryptography/ApplicationPkcs7MimeTests.cs#L1058
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build solution:
UnitTests/Cryptography/ApplicationPkcs7MimeTests.cs#L1158
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build solution:
UnitTests/Cryptography/SecureMimeTests.cs#L3105
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build solution:
UnitTests/Cryptography/SecureMimeTests.cs#L3257
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build solution:
UnitTests/Utils/ValueStringBuilderTests.cs#L88
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build solution:
UnitTests/Utils/ValueStringBuilderTests.cs#L108
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build solution:
UnitTests/Cryptography/DefaultSecureMimeContextTests.cs#L93
'X509CertificateDatabase.Update(X509CrlRecord)' is obsolete: 'This method is not used and will be removed in a future release.'
|
Loading