Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove obsolete properties, methods, and classes for 3.0 #138

Conversation

erikmav
Copy link
Contributor

@erikmav erikmav commented Mar 28, 2024

Add BinaryFormattter serialize-deserialze testing across versions, and correct serialization property bag names broken by modernization (#124).

Commented out obsolete tag for FixFlags.Mdc as the obsolete tags in MDC.cs are commented out.

…ormattter serialize-deserialze testing across versions, and correct serialization property bag names broken by modernization (apache#124).
@erikmav
Copy link
Contributor Author

erikmav commented Mar 28, 2024

For #125

@erikmav erikmav changed the base branch from master to Feature/111-Dropping-support-for-older-runtimes March 28, 2024 19:40
Copy link
Contributor

@FreeAndNil FreeAndNil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot.
Just one question.

I've noted the breaking changes in #125 (comment)

src/log4net/Config/RepositoryAttribute.cs Show resolved Hide resolved
@FreeAndNil FreeAndNil force-pushed the Feature/111-Dropping-support-for-older-runtimes branch from 7e93b50 to 6d23e81 Compare April 3, 2024 20:33
Copy link
Contributor

@FreeAndNil FreeAndNil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

@FreeAndNil FreeAndNil merged commit 202bb5c into apache:Feature/111-Dropping-support-for-older-runtimes Apr 4, 2024
@erikmav erikmav deleted the dev/erikmav/obsolete branch April 4, 2024 16:23
@FreeAndNil
Copy link
Contributor

@erikmav because of https://learn.microsoft.com/en-us/dotnet/standard/serialization/binaryformatter-security-guide we think about removing ISerializable and [Serializable] (at least for netstandard).
What do you think?
Where are you using this serialization for log4net objects?

@erikmav
Copy link
Contributor Author

erikmav commented Sep 5, 2024 via email

@FreeAndNil
Copy link
Contributor

@erikmav thanks for your feedback.
We have only three failing tests, when removing it.
The two from you and PropertiesDictionaryTest.
When we remove the old serialization we will maybe switch to DataContractSerializer and adjust the tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants