-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[BinFmt] Error on serialization custom events in by default in .NET framework #9318
[BinFmt] Error on serialization custom events in by default in .NET framework #9318
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.
Looks good to me.
The changewave should be 17.9 unless you are explicitly convinced it should stay under 17.8
Can you remind me what partner team buyoff we have on this? Are all known first-party uses rectified? |
@rainersigwald I have collected some usage data here: I think most of those are in-process instantiation so it will not be serialized for IPC and hence this change will not break them. Now when I think about it more, chance of this change to cause serious havoc is small. I have rephased NOTE |
Can you run an experimental insertion and try out the build with C++ code analysis and FxCop? I would expect the custom errors to be created at build time and thus in the MSBuild.exe worker, not in devenv.exe.
|
Experimental insertion for #9318
88e03f4
to
c62c8f3
Compare
All prerequisities merged in VS |
Co-authored-by: Ladi Prosek <ladi.prosek@gmail.com>
Fixes #9300
Context
.NET Framework shall throw error when attempting to serialize customer event args by binfmt.
See #9300 for more context.
Changes Made
Testing
Local. Unit tests.
Notes
It is breaking change, but chance of break is small, IMO.