ParameterInfo.RawDefaultValue throws when default value is string.empty

[mjkkirschner]

Description

When using a metaDataLoadContext to find static methods in an assembly, invoking ParameterInfo.RawDefaultValue throws a badformat exception - I've tracked down the line of code to here:
https://github.com/dotnet/runtime/blob/main/src/libraries/System.Reflection.MetadataLoadContext/src/System/Reflection/TypeLoading/General/Ecma/EcmaDefaultValueProcessing.cs#L18

this appears to throw when the parameter in question is an optional string with a default value of empty string ""
It looks like constantValue.Value is nil in this case. I'm not sure if it's simply an issue with empty strings in all cases or its an environment issue.

Configuration

• Which version of .NET is the code running on? .net 4.8
• What OS and version, and what distro if applicable? windows 10 2004
• What is the architecture (x64, x86, ARM, ARM64)? x64
• Do you know whether it is specific to that configuration? do not know
• If you're using Blazor, which web browser(s) do you see this issue in? NA

Regression?

Don't know at this time.

Other information

[joperezr]

@mjkkirschner thanks for the report. Did you try if this repros in .NET 5 or .NET Core? Can you please add a code snippet of the repro so that we can take a look?

[ghost]

This issue has been automatically marked no recent activity because it has been marked as needs more info but has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no recent activity.

Please refer to our contribution guidelines for tips on what information might be required.

[ghost]

This issue will now be closed since it had been marked no recent activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

[svick]

I was able to reproduce this issue and have created a PR to fix it: #61457, so I think this should be reopened.