Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Blazor Server and Client side, yes, and now?
PRO CLIENT SIDE
PRO SERVER SIDE
So what do you say? Have you ever thought about it? It could also be a temporary solution, which would not deny in future having even full dotnet components (as today for react, not all components are full react made)
For those who want the repo is available with all the changes to the base code of blazor (https://github.com/uazo/Blazor/tree/remove-custom-tag).
I have just installed Blazor 0.5.1, created
And that is true: https://caniuse.com/#feat=promises
This is explained somewhat in the original issue that introduced disallowing script tags, #552.
@chucker, it needn't script tags,
after compile the above code, this c# function become two file:
As a developer, however, I would not be interested in using an existing ready-made js library, if something specifically made for Blazor existed. The problem is that developing libraries for Blazor for now is extremely difficult, because there is no simple, maintainable and scalable method to develop the js part.
About converting c # to js, I guess it's not in Blazor's target, and inserting <script> tag is not the solution, even just thinking about CSP.
The simplest smarter and fast change solution in my opinion is to associate a js component with a blazor side component:
Starting from this I created a Blazor-React layer that allows the use of DevExtreme components.