Fody and especially Fody.PropertyChanged should be built in

[buzzware]

Summary

Fody and especially Fody.PropertyChanged should be built in.

Epics

Epics under this Theme:

• [Title of the linked Epic](hyperlink to the Epic issue).

[scalablecory]

What is Fody? Can you expand on your suggestion?

[svick]

@scalablecory Fody is an open source IL weaver tool and PropertyChanged.Fody is a Fody plugin that lets you avoid boilerplate code that is very common in many apps. (My employer, PostSharp, has a similar commercial tool with a similar plugin.)

Though I think the intention of the C# team is that source generators are the solution for these kinds of problems.

[JanTamis]

I think there is even a sample for it.

[buzzware]

If you compare Xamarin binding template development with say EmberJs, you'll see how horrible MVVM is without Fody.PropertyChanged. We should not have to manually implement propeties that raise events for every property.

[scalablecory]

Thanks @svick. I suspect you're right about source generators 👍

[buzzware]

Regarding source generators, it all depends on the developer experience and the tidiness of the models.
People from the Roslyn team should site down with the MVVM framework people and make sure the ideal model definitions are possible.

I'm thinking from a Xamarin point of view, and I recommend looking at https://mobx-state-tree.js.org/intro/philosophy and https://guides.emberjs.com/release/in-depth-topics/autotracking-in-depth/#toc_tracked-properties-in-custom-classes.

In both State Tree and Ember you can model not just a single entity class but the live state of the entire application in a bindable form including entities and their relationships, all without a line of visual representation. Then you render this state and mutate it with UI actions, and you're done.

In particular, notice the handling of arrays, dependent properties and caching. There is no declaring anything like a BindableProperty.

Normally I avoid source generation because there are issues in keeping the generated source fresh with the actual source. However if that is solved at development time in .Net (and Xamarin already generates source) then I suppose its not an issue.