The Wayback Machine - https://web.archive.org/web/20220201120658/https://github.com/dotnet/aspnetcore/issues/39906
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

Unhandled exception rendering component: The provided expression contains a PropertyExpression which is not supported. FieldIdentifier only supports simple member accessors (fields, properties) of an object #39906

Open
1 task done
nyluhe opened this issue Feb 1, 2022 · 1 comment

Comments

@nyluhe
Copy link

@nyluhe nyluhe commented Feb 1, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

image

I am getting the above exception when trying to load any razor component that contains a Blazor Input. Any Razor component that contains simple html inputs is working fine. The issue we're having is that this isn't an issue when running locally, but when we upload this project to a Web App in Azure, we see this exception.

Here is the view I am trying to render:
image

I have tried removing the ValidationMessages, the DataAnnotation Validators and using InputText's for both of the fields in the form. The Dto is a simple class:

public class UserLoginDto { public string Email { get; set; } public string Password { get; set; } public bool IsPersistent { get; set; } }

I believe this to be an issue with dotnet.5.0.13.js/dotnet.5.0.13 in general as we have multiple projects that run on dotnet 5.0.9 - 5.0.11 without issue in Azure - all using WASM and all using the exact same Azure configurations.

Expected Behavior

The Edit Form renders.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

@nyluhe
Copy link
Author

@nyluhe nyluhe commented Feb 1, 2022

I can attempt to link to a GitHub repo if necessary, but you'd be required to upload to Azure to see an impact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant