@page "/"
主页
你好,工业互联网标识
欢迎来到工业互联网标识解析Web端,有什么你想了解的么?
你可以找到一些文档和案例,从
iFactory 文档中心
这里有些什么呢?
基于IDIS_Runtime的一些实现
可以在Web端完成一些手动注册与解析的操作
通常这些操作会由相关的生产系统自动化解析
你可以在<AppBar>的右上角切换夜间模式
如果你觉得暗色主题更好的话
@*
*@
@* 此模板中的交互性 *@
@*
*@
@* *@
@* When you opt for the "Global" Interactivity Location,
*@
@* the render modes are defined in App.razor and consequently apply to all child components.
*@
@* In this case, providers are globally set in the MainLayout.
*@
@*
*@
@* On the other hand, if you choose the "Per page/component" Interactivity Location,
*@
@* it is necessary to include the
*@
@*
*@
@* <MudPopoverProvider />
*@
@* <MudDialogProvider />
*@
@* <MudSnackbarProvider />
*@
@*
*@
@* components on every interactive page.
*@
@*
*@
@* If a render mode is not specified for a page, it defaults to Server-Side Rendering (SSR),
*@
@* similar to this page. While MudBlazor allows pages to be rendered in SSR,
*@
@* please note that interactive features, such as buttons and dropdown menus, will not be functional. *@
@* *@
@* *@
@*
*@
@* What's New in Blazor with the Release of .NET 8 *@
@*
*@
@* Prerendering *@
@* *@
@* If you're exploring the features of .NET 8 Blazor,
you might be pleasantly surprised to learn that each page is prerendered on the server,
regardless of the selected render mode.
*@
@* This means that you'll need to inject all necessary services on the server,
even when opting for the wasm (WebAssembly) render mode.
*@
@* This prerendering functionality is crucial to ensuring that WebAssembly mode feels fast and responsive,
especially when it comes to initial page load times.
*@
@* For more information on how to detect prerendering and leverage the RenderContext, you can refer to the following link: *@
@* *@
@* More details *@
@* *@
@* *@
@* *@
@*
*@
@* InteractiveAuto *@
@* *@
@* A discussion on how to achieve this can be found here: *@
@* *@
@* More details *@
@* *@
@* *@