-
Notifications
You must be signed in to change notification settings - Fork 295
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
Move into Shared for SqlError.cs #1322
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the behavior of a public API would cause a breaking change. I think it'd better keep it as same as before and using the OptionalField
attribute if we didn't want to announce a breaking change here.
I suggest applying the same behavior for netcore too.
…rties back to fields for serializations and included a serialization test for SqlError
… in NET5 to suppress a test compiler error
I noticed there's some compiler error in compiling the new SqlErrorTest in NET5 because the binary serialization is obsolete, I have a fix to that in the next commit |
Relates to #1261 . Merged netfx into netcore for SqlError.cs and move it into shared src and updated the references in the csprojs. I did notice the SqlError in netfx uses the [Serializable] attribute for the class, and has 2 fields that are marked as [System.Runtime.Serialization.OptionalField] with a version number, but in netcore, they've all been switched over to auto properties so they don't get serialized anyway. I ran the functional tests and manual tests for netfx and it seems to be pass and didn't notice any issues, so hopefully we don't need to use them.