Merhaba ,

TÜRKÖZ Yönetim Paneli

Hoş Geldiniz...

Satış Grafiği

204060 OcaŞubMarNisMayHaz
2023

Son Aktiviteler

Yeni kullanıcı kaydı

Ahmet Yılmaz

Yeni sipariş

#ORD-4562

Proje güncellemesi

E-ticaret sitesi

Destek talebi cevaplandı

#TICKET-124

Son Siparişler

Sipariş No Müşteri Tutar Durum Tarih İşlem
#ORD-4562 Ayşe Demir ₺1.250,00
Tamamlandı
5.10.2025
#ORD-4561 Mehmet Kaya ₺890,00
İşleniyor
4.10.2025
#ORD-4560 Zeynep Şahin ₺2.450,00
Gönderildi
3.10.2025
#ORD-4559 Can Aydın ₺540,00
Tamamlandı
2.10.2025
#ORD-4558 Elif Yılmaz ₺3.200,00
İptal Edildi
1.10.2025
warning_amber
Radzen. Alert with close button
check_circle
Radzen. Alert without close button
info
Alert with Title
Radzen. Alert with title
Radzen. Alert without message icon

Hello, world! I am MudText Component

Welcome to your new app, powered by MudBlazor and the .NET 8 Template!

You can find documentation and examples on our website here: www.mudblazor.com

Interactivity in this Template

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

An unhandled error has occurred. Reload 🗙