Compatibility with the mvvm community toolkit about generator.equals HOT 4 CLOSED

AFAIK there's no way to "stack" source-code generators. I think this might be a case of picking one or another but not both, and the reason for that is that if you want to use both you might end up in a situation where MVVMToolkit is using one equality strategy for a particular property while Generator.Equals is using a different equality strategy for the same property.

from generator.equals.

I am a bit confused as for what is the problem you're facing.

Source code generators are unaware of each other. So MVVM toolkit will generate some code and Generator.Equals will generate another, and you'll end up with two extra partial definitions of classes that may or may not agree with each other.

Generator.Equals implements equality at the object level so it wouldn't help you with implementing property changed notifications, if that's what you're aiming for.

from generator.equals.

Looks like your best shot is to apply attributes to the backing field and suppress warnings.

Out of curiosity what warnings are you getting by doing this?

from generator.equals.

MVVMTK0034

I still think the key is that tagging [property: DefaultEquality] to my backing field gets the attribute correctly applied to the property generated by the MVVM toolkit, but then the code generated by MVVM toolkit isn't analyzed, so even though the property definition includes DefaultEqualityAttribute, no equality code for that property is generated.

So yes, I think my options are to implement the property manually or ignore / suppress the compiler warning. Unless code generated by one roslyn source generator can be used by another source generator (somehow).

from generator.equals.