Blazor Binding Convention Property or member

Question

Blazor Binding Convention Property or member

J.P. Bachmann 1

Hey,

I am currently working within a Blazor project for my client and we struggled to find a clear docu that shows MS convention on namings for Blazor bindings.
What is the proposed standard for binding values in Blazor views? Is it recommanded to bind to properties or fields because the documentation is all over the place:
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/?view=aspnetcore-5.0

sometimes properties are bound and sometimes fields are

Rena Ni - MSFT 2,066 Reputation points

2021-07-28T01:53:43.037+00:00

Hi @J.P. Bachmann , do your requirement is to want to know what scenario need to use two-way binding?
J.P. Bachmann 1 Reputation point

2021-07-28T05:48:55.833+00:00
Hey @Rena Ni - MSFT not quite. Its more a question in general.

For Example a simple render case:

@code { public string Name { get; set; } public string _name; } <span>@Name</span> <span>@_name</span>

Should we use the property Name or the member _name here?

2end case would be binding to other components/elements:

@code { public string Name { get; set; } public string _name; } <input @bind-value="Name"/> <input @bind-value="_name"/>

My question is what is recommended to be used? Property or member?
Rena Ni - MSFT 2,066 Reputation points

2021-07-28T07:16:50.357+00:00

Hi @J.P. Bachmann , _name here is named Field instead of member. Actually in your scenario, both of them seems no difference, but still suggest using Property. I think you could read the answer here about difference between Filed and Property.
J.P. Bachmann 1 Reputation point

2021-07-28T07:45:48.13+00:00

Hey @Rena Ni - MSFT you are right, a field is a member but a member is not a field. Is there any disadvantage using a field instead of a Property or vice versa?
Rena Ni - MSFT 2,066 Reputation points

2021-07-28T08:33:30.483+00:00

Hi @J.P. Bachmann ,In a lot of cases where data binding is involved, for example, only properties are considered for binding. Fields are ignored. So in Entity Framework Core, a property might represent a column in a database. And it has to be a property. It cannot be a plain field.