Reapply "Fix TaskParameterTaskItem serialization perf" #12135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Reattempt of #11638
This broke VS tests due to a
ToList()
not triggering before crossing an AppDomain boundary:Error:
Although the above AppDomain check is used in multiple
ITaskItem
implementations, the out-of-proc TaskHost hits the case where the object was created in the default AppDomain during deserialization, but is copying to anITaskItem
in a separate AppDomain. Therefore, the condition never triggers.Changes Made
This replaces the check with
RemotingServices.IsTransparentProxy(_)
, which matches howProjectItemInstance.TaskItem
handles this scenario.Testing
Added UTs for
TaskParameterTaskItem.CopyMetadataTo(_)
across AppDomains in both directions.