Closed IvanKitanov17 closed 4 months ago
Please update your HeadOutlet and Routes with the following to get this working
<HeadOutlet @rendermode="@InteractiveServer" />
<Routes @rendermode="@InteractiveServer" />
@IvanKitanov17 I also assigned myself work item 31163. If my suggestion fixes the issue for you we can close that too.
Note, I first looked into this issue when a customer was looking for aspire compatibility https://www.infragistics.com/community/forums/f/ignite-ui-for-blazor/126066/found-the-problem-adding-igniteui-to-a-blazor-project
https://my.slingshotapp.io/openTopic/e97e10ef_03d82d56-1f06-43cb-941d-009fc94fa481
@mddifilippo89 It resolves the issue, thank you for the clarification!
This resolved my issue.
Is this a workaround or a permanent fix going forward for .net 8.0 and later versions?
Description
Components render as normal html elements instead of IgniteUI for Blazor controls when using Blazor WebApp template with .NET 8
Since the Blazor WebApp template has different file structure, the issue might be caused from this.
The following issue might be connected.
Steps to reproduce
Run the attached sample
Result
When the page loads the card component should be present, however only native html elements are present.
Expected result
The IgniteUI for Blazor comonents should render correctly.
Attachments
Sample.zip