Using a different base component class

MvvmComponentBase inherits from ComponentBase. What’s the best practice if we want to use a different base component class, say OwningComponentBase or AbpComponentBase as we are using the ABP framework, yet still want to keep the functionalities provided by MvvmComponentBase?

[klemmchr]

Since we now got code generators in .NET I’m not a huge fan of Fody weavers any more. They served their purpose, but the built in source generators should do the job. The docs cover our use case.

My plan would be to ship that source generator too (either in a separate NuGet package or directly with the main one). This way, any integration would happen by defining a partial class with a given attribute that would be picked up by the source generator.

[hillin]

So the problem here is misusing of the ISyntaxContextReceiver. For each compilation unit (assembly), only one instance of each ISyntaxContextReceiver is created and they are being reused again and again, for all GeneratorSyntaxContexts.

In the MvvmBlazor project, there are 3 classes annotated with the MvvmComponentAttribute. The MvvmSyntaxReceiver visits them one by one, and only keeps the ComponentClass and ComponentSymbol values for the last of them, which I see is MvvmOwningComponentBase. Therefore you can see the code was only generated for that last class, but not for other classes, e.g. MvvmComponentBase<T>, which is used in the sample project and thus it did not compile.

With that fixed, some minor issues expose, like MvvmComponentBase<T> and MvvmComponentBase has the same identifier, but you have to generate their code to different files, and the generic source template missed the partial modifier etc.

I’ve fixed those problems here, the solution now compiles, except for a test project which I did not bother to look: https://github.com/klemmchr/MvvmBlazor/pull/54