Conversation
|
Updating with latest main as we had a build break that just got fixed with 6b3a36d |
|
@dotnet/domestic-cat is the frequency of OSX leg build failures expected? I'm reruning for 4th time :-O |
Unfortunately the macOS arm64 leg specifically is timing out, and we haven't figured out why yet, so not your fault in this case. We made it optional so we can merge past it with 1 approving review. |
|
@JanKrivanek, this looks good to me. Do you want it backported? 9.0.3xx is open for changes. I think this would be low-risk enough that you could argue for it for 9.0.1xx or 9.0.2xx |
|
Looks like we would want to take it for all 9.x SDKs if possible, based on the recommendation from the binaryformatter working group in the linked issue. |
|
/backport to release/9.0.1xx |
|
Started backporting to release/9.0.1xx: https://github.com/dotnet/sdk/actions/runs/12796505954 |
|
/backport to release/9.0.2xx |
|
Started backporting to release/9.0.2xx: https://github.com/dotnet/sdk/actions/runs/12803666854 |
Contributes to dotnet/msbuild#11185
Context
dotnet/msbuild#11185 (comment)
It was decided that MSB3825 should not be applicalbe to NET9+ - as BinaryFormatter is being used only in a very limited number of subcases, where it needs to be explicitly opted in via
System.Resources.Extensions.UseBinaryFormatterswitch.