Interfaces built with FAST adapt to your design system
Interfaces built with FAST adapt to your design system and can be used with any modern UI Framework by leveraging industry standard Web Components.
Let’s put this to the test using Blazor.
In this article you’ll find answers to the following questions:
- What is fast in a nutshell
- What are the pitfalls of integrating Blazor with FAST
- Why we created Blazor.Fast (a very tiny wrapper around FAST)
- How we abstracted away the Themes
- How we integrated the
<Input*/> | <EditForm>components - How you can integrate Blazor.Fast in your own project.
What is fast?
FAST tries to solve the -redundant- problem I have in…
For one of our clients we needed a “Save As” or “Print As” dialog option specifically for PDF files(invoices and such). Unfortunately there are no native components or wrappers which handle this specific case using Blazor. So we started building our own.
The final result
Exploring the alternatives
In our initial release we tried to use the built-inNavigationManager. Which can easily download a file (even if the file is returned by a Controller action or on any other domain) using the foreLoadparameter. I even recall an entire discussion about it on the old Blazor repository in the early days of Blazor (2018). But unfortunately it just…
