-
-
Notifications
You must be signed in to change notification settings - Fork 404
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 requirement for Serializable attribute #3687
Comments
We can't remove the attribute, it would be too breaking :) It's just nothing will care about it. |
@blowdart agreed - though Microsoft might remove the attribute (I don't know). |
In this case I am Microsoft. We don't have any plans to remove it as yet. A much more detailed white paper will be coming soon, my issue in the dotnet repo is really just an overview. Hopefully that will set your mind to rest, but honestly removing the requirement is probably a decent idea if your serializers don't need it. |
That's excellent Barry, I wasn't really paying attention to the identity of the person doing the reply 🫢 I agree with the idea that removing the attribute from .NET would be a massive breaking change. In the case of CSLA though, removing the checks that require it (I think) makes sense, because other serializers (including the one that's now default in CSLA) don't use it for anything - it was literally a vestige of the way CSLA was originally based on BinaryFormatter 20 years ago. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Microsoft is removing support for BinaryFormatter in .NET 9, and presumably this means they might remove the
SerializableAttribute
type.dotnet/runtime#98245
CSLA never really used this, but does require it as a vestige of when we used to support BinaryFormatter.
CSLA should no longer require the use of the
Serializable
attribute for serializable types.The text was updated successfully, but these errors were encountered: