How to Use Code Behind for Blazor Components | 2 Solutions 

I initially disliked having the code and the markup in the same file, being used to separate files for many years. But, having decided to give the singe-file approach a try a few years ago, I actually much prefer keeping the code and the markup together now. The main reason is that doing so encourages keeping the UI component code itself as simple as possible, delegating complex work to separate non-component classes where they can be isolated and reasoned about and tested easier. If I find my UI component file to be getting large and unwieldy, that's a sign that I should take a closer look at the component to see how I can simplify it by maybe breaking it down into smaller components or possibly extracting the complex logic into a separate class or classes decoupled from the component. IMO, a well-designed component is much easier to read when the code and the markup are together.

Thanks for your kind comment and thanks for watching.

Thanks a lot. That's very kind of you and means a lot to me. I try to make every video a little bit better than the previous. 😎

I'm not sure I understand your question, but I give it my best to provide a helpful answer here. Every Blazor/Razor component inherits from the ComponentBase class. You can use either of the inheritance definition models, but you cannot mix and match. I would not advise building a component tree. I would always build components based on the ComponentBase class. I do not have any experience with components inheriting from each other and overriding functionality. In my opinion, this adds too much complexity to justify it. I'd rather extract code into another class to share code between two Blazor components. I hope that helps answer your question. Otherwise, feel free to provide a link to a GitHub repo or a Gist so we can discuss more hands-on.

@@ClaudioBernasconi - oh let me rephrase, in your video you created a component base class, call it MyComponentBase, and then used the @inherit MyComponentBase in your blazor component. Can you then override MyComponentBase methods, from your blazor page, if you needed to?

Yes, it's possible with one of the "code-behind" approaches: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-kjWsGlpYGmQ.html

@@ClaudioBernasconi great, thanks

Great question! It doesn't work for me. I could only speculate why it's not possible, but I'm not the right person to provide that information. As far as I can tell, only parameter injection works for Blazor components.

That sounds like trust issues. However, I don't judge you.