Support for .NET5-rc1 Fields on RenderTreeFrame breaking change

When running BlazorStyled in .NET5-rc1, I experience the following issue:

warn: Microsoft.AspNetCore.Components.Server.Circuits.RemoteRenderer[100]
      Unhandled exception rendering component: Field not found: 'Microsoft.AspNetCore.Components.RenderTree.RenderTreeFrame.FrameType'.
      System.MissingFieldException: Field not found: 'Microsoft.AspNetCore.Components.RenderTree.RenderTreeFrame.FrameType'.
         at BlazorStyled.Internal.RenderFragmentExtensions.RenderAsSimpleString(RenderFragment childContent)
         at BlazorStyled.Styled.ProcessParameters()
         at BlazorStyled.Styled.OnAfterRenderAsync(Boolean firstRender)
fail: Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost[111]
      Unhandled exception in circuit 'OMUpj4LKP-YliJQf-xXpCFPQKKLft3UpHJniZf7FHww'.
      System.AggregateException: One or more errors occurred. (Field not found: 'Microsoft.AspNetCore.Components.RenderTree.RenderTreeFrame.FrameType'.)
       ---> System.MissingFieldException: Field not found: 'Microsoft.AspNetCore.Components.RenderTree.RenderTreeFrame.FrameType'.
         at BlazorStyled.Internal.RenderFragmentExtensions.RenderAsSimpleString(RenderFragment childContent)
         at BlazorStyled.Styled.ProcessParameters()
         at BlazorStyled.Styled.OnAfterRenderAsync(Boolean firstRender)
         --- End of inner exception stack trace ---

A search brought me here, where it was written:

Old behavior

Public members on RenderTreeFrame were defined as fields, for example renderTreeFrame.Sequence and renderTreeFrame.ElementName.

New behavior

Public members on RenderTreeFrame are defined as properties with the same names as before, for example renderTreeFrame.Sequence and renderTreeFrame.ElementName.

If older precompiled code has not been recompiled since this change, it may throw an exception similar to MissingFieldException: Field not found: ‘Microsoft.AspNetCore.Components.RenderTree.RenderTreeFrame.FrameType’.

[chanan]

I wasn’t planning on it till it gets released, but if people are using this library and are stuck due to this, I will try to do it sooner. Of course, if you feel up to it, feel free to send a PR, which will increase the speed this gets done at

[chanan]

Released 3.1