DefaultValueAttribute support change introduce new linker warnings

[akoeplinger]

See dotnet/sdk#42496 (comment)

Disabling the test temporarily so we can unblock codeflow, filing this issue to track reenabling it.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-componentmodel
See info in area-owners.md if you want to be subscribed.

[ericstj]

@akoeplinger mentioned that #105766 introduced a new linker warning

+ ILLink : Trim analysis warning IL2026: System.ComponentModel.DefaultValueAttribute.DefaultValueAttribute(Type, String): Using member 'System.ComponentModel.DefaultValueAttribute.<.ctor>g__TryConvertFromInvariantString|5_0(Type, String, Object&)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. DefaultValueAttribute usage of TypeConverter is not compatible with trimming.

Seems the test just creates a very simple hello world.

@steveharter @LakshanF can you have a look and see if this is expected?

We should also make sure the test gets reenabled in SDK. @sbomer who appears to maintain this test.

[sbomer]

The test already has an expected warning for the DefaultValueAttribute(Type, String) ctor's call to the local function TryConvertFromInvariantString, but the name mangling looks like it changed from g__TryConvertFromInvariantString|4_0 to g__TryConvertFromInvariantString|5_0. I think the expected warning in the test just needs to be updated.

[akoeplinger]

Ah thanks, makes sense. I'll open an SDK PR.

[steveharter]

Ah thanks, makes sense. I'll open an SDK PR.

Closing this issue then.