Blazor Tutorial - Ep17 - Component Lifecycle a) When is rendering triggered

Поделиться
HTML-код
  • Опубликовано: 18 окт 2024

Комментарии • 9

  • @armandollewellyn1521
    @armandollewellyn1521 3 года назад +1

    Thank you Frank. I really enjoy the quality that you put into these videos. I look forward to watching your blazor videos from this point forward. Thank you very much and stay safe and well.

  • @FrankLiuSoftware
    @FrankLiuSoftware  3 года назад

    💎My New Blazor Course: Build an e-commerce app with ASP.NET Blazor and Clean Architecture
    ruclips.net/video/C8xIE_3I7JQ/видео.html

  • @FourDollarBill
    @FourDollarBill 3 года назад

    Very helpful. Thank you, Frank!

  • @farrenyoung
    @farrenyoung 4 года назад

    Good stuff. Thanks for sharing!

  • @gyanookharel7440
    @gyanookharel7440 Год назад

    Compiler can choose to not re-render the component if the values displayed in the component are not changed even after an event. If there is an event but it’s not changing any state then the component most likely won’t re-render.

  • @naveedkhanhome
    @naveedkhanhome 4 года назад

    Nice man

  • @abrahamjaimes7643
    @abrahamjaimes7643 Год назад

    when you are explaining about the OnAfterRender method , that method only renders the comopent once , if you clicked a button like in your example and see the results on the console, the component is not being render , why you seeing is only the result of calling the Console method , but the compoent still not being rerendered, that is why OnAfterMethod has the bool firstRender param , to proof that the component renderes only once , unless you change from page or refresh the page oviouslly will render once one more time...