Closed qin-guan closed 3 years ago
Thanks for the report, we did not convert the project yet to .net5, so it's not a surprise that things are breaking in .net5. We will address this when we convert over to .net5.
@chanan thanks for the quick reply, do you have a rough timeline on when that would be?
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
@qin-guan I created a branch for .net 5: https://github.com/chanan/BlazorStyled/tree/net5rc1 I was not able to run web assembly - some missing file error, but I was able to run server side without a problem. I am not currently sure what the error you are seeing is. But once I figure out why cleint side isnt working, I will create a build as 4.0.0-alpha-01
@chanan thanks! do you think u could copy the error here? i've been having some issue running blazor wasm as well.
I am missing some setting somewhere, just not sure where. I am not getting a compile error, it just wont run.
If I "run" I get a blank browser with the address not filled in. If I "run without debugging" - I get an error in the browser that it can't find _framework/blazor.webassembly.js
Checking the bin folder it doesnt have the wwwroot folder in it. Comparing it to a blank .net blazer wasm project, I haven't yet located what I am missing.
@chanan have you been able to get .NET5 working, since it has been just released?
I plan to work on this weekend. Hopefully shouldn't have major issues
I have .net 5 working, I checked both server side and client side sample doc site and everything seems to work. I will release it in a few hours, please check your defect at that time and see if it still occurs.
I just pushed: BlazorStyled.3.1.0-rc1 compiled in net5.0
i can verify that 3.1.0-rc1 works with .net5, thanks :)
Released 3.1
When running BlazorStyled in .NET5-rc1, I experience the following issue:
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'.