Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wasm System.Reflection.MemberInfo.ToString() returns different string for some types in public field compare to desktop #88637

Closed
jjzhang12 opened this issue Jul 10, 2023 · 0 comments · Fixed by #88648
Assignees
Labels
needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners

Comments

@jjzhang12
Copy link

Description

Call MemberInfo.ToString() on int, double in public field
desktop returns
Int32 int1
Double double1

wasm returns
System.Int32 int1
System.Double double1

For properties, both return same
Int32 Int1
Double Double1

We are serialize the string in desktop and then use the same string to find the member in wasm. Because they are mismatched, we cannot find the corresponding fields.

Reproduction Steps

https://github.com/jjzhang12/MonoType

Run the Blazor app BlazorApp and ConsoleApp1 can see the difference.

Expected behavior

wasm should return the same string as desktop.

Actual behavior

wasm returns different than desktop. See description.

Regression?

Not sure.

Known Workarounds

No response

Configuration

No response

Other information

No response

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jul 10, 2023
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 10, 2023
@jjzhang12 jjzhang12 changed the title wasm MemberInfo.ToString() returns different string for some types in public field compare to desktop wasm System.Reflection.MemberInfo.ToString() returns different string for some types in public field compare to desktop Jul 10, 2023
@vargaz vargaz self-assigned this Jul 10, 2023
vargaz added a commit to vargaz/runtime that referenced this issue Jul 11, 2023
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jul 11, 2023
vargaz added a commit that referenced this issue Jul 11, 2023
@ghost ghost removed in-pr There is an active PR which will close this issue when it is merged untriaged New issue has not been triaged by the area owner labels Jul 11, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Aug 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants