Skip to content

Translate FileAccessData in TaskHostTaskComplete#9271

Merged
rainersigwald merged 1 commit intodotnet:vs17.8from
rainersigwald:translate-null-for-new-field
Sep 26, 2023
Merged

Translate FileAccessData in TaskHostTaskComplete#9271
rainersigwald merged 1 commit intodotnet:vs17.8from
rainersigwald:translate-null-for-new-field

Conversation

@rainersigwald
Copy link
Copy Markdown
Member

Summary

Fix a reported regression that causes MSBuild to crash in net35-targeting projects.

Customer Impact

Projects that use the .NET 3.5 taskhost (like projects that target .NET 3.5 and have .resx files) fail with error MSB4217: Task host node exited prematurely.

Regression?

Yes, from 17.7. Introduced in #9214.

Testing

Repro case from VSUnitTesting repo manually validated, automated tests.

Risk

Low, adds a bool to the translation only in the known-broken case.

Details

TaskHostTaskComplete packets can be sent between nodes that differ in
FEATURE_REPORTFILEACCESS, causing confusion when the sending side (for
example a net35 taskhost) does not send the FileAccessData field, but
the receiving side (net48) expects it.

Unify this by explicitly sending a bool false (no data) in the
!FEATURE_REPORTFILEACCESS case, so there's no difference on the
receiving end between "no data" and "couldn't be any data".

TaskHostTaskComplete packets can be sent between nodes that differ in
FEATURE_REPORTFILEACCESS, causing confusion when the sending side (for
example a net35 taskhost) does not send the FileAccessData field, but
the receiving side (net48) expects it.

Unify this by explicitly sending a bool `false` (no data) in the
!FEATURE_REPORTFILEACCESS case, so there's no difference on the
receiving end between "no data" and "couldn't be any data".
@ghost
Copy link
Copy Markdown

ghost commented Sep 26, 2023

Hello! I noticed that you're targeting one of our servicing branches. Please consider updating the version.

@ghost
Copy link
Copy Markdown

ghost commented Sep 26, 2023

Hello! I noticed that you're targeting one of our servicing branches. Please consider updating the version.

@rainersigwald rainersigwald merged commit 585e097 into dotnet:vs17.8 Sep 26, 2023
@rainersigwald rainersigwald deleted the translate-null-for-new-field branch September 26, 2023 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants