[2020-02][marshal] Fix VARIANT and BSTR marshaling in structs #20918
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.
Manual backport of #20917 to
2020-02(6.12). but also new BSTR fixesPartial revert of #8732
If a managed struct is declared as
Then the
datafield should be marshalled as a VARIANT.The fix checks that the field's type is
objectand uses VARIANT for marshaling, otherwise it continues as in #8732 and uses MONO_MARSHAL_CONV_OBJECT_STRUCT.Also added support for marshaling BSTR in structs in reverse P/Invokes. Morally it's a piece of #19701 but just for the
BSTR_STRcase