fix v5: Missing @using in _Imports.razor in template
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start with src/Templates/templates/blazorweb-csharp-10/.template.config/template.json and reproduce a .NET 10.0 Fluent Blazor Web App using PerPage/Component interactivity and the sample pages. Check the generated _Imports.razor; done means it includes @using NameOfMyApplication.Client.Layout and the navigation menu appears as it does for .NET 9.0.
Written by the indexing model from the issue text.
Description
🐛 Bug Report
First, thank you very much for this incredible library.
🤔 Expected Behavior
This is about templates for .Net10.0 .
😯 Current Behavior
Some @using statement is missing in the “import.razor” file generated by the templates.
More precisely the problem occurs when the following parameters used when creating a new application:
- Template: Fluent Blazor Web App
- Target Framework: Net10.0
- Interactive render mode: Auto (Server and WebAssembly)
- Interactivity location: PerPage/Component
- Include Sample Pages: Yes (default)
- Auth: No authentication
The missing line is:
@using NameOfMyApplication.Client.Layout
As a result, the navigation menu does not appears.
Note that everything is Ok when the Net 9.0 parameter is used.
💻 Repro or Code Sample
Use the last 5.0 templates for creating a new application.
Seems to occur when the Interactivity location parameter is set to PerPage/Component (just with .Net 10.0).
💁 Possible Solution
Some problem here : src/Templates/templates/blazorweb-csharp-10/.template.config/template.json .
🌍 Your Environment
- Windows 10.0
- Microsoft Edge, Google Chrome, Mozilla FireFox
- .NET 10.0 and Fluent UI Blazor library Version 5
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 483
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 77
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/fluentui-blazor
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/fluentui-blazor#5365 ·
Maintainers usually reply within 1 day
-
[v5] FluentDatePicker year navigation stops before MinDate and changes after switching calendar viewsPossibly taken @dvoituron claimed this 9 days ago. Openstatus:needs-investigation v5
microsoft/fluentui-blazor#5311 · 1 assignee ·
Maintainers usually reply within 1 day
-
bug v5
Difficulty 3/5 1-2 days Newbie friendliness 68/100
microsoft/fluentui-blazor#5281 · 1 comment ·
Maintainers usually reply within 1 day
-
feature v5
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/fluentui-blazor#5277 · 5 comments ·
Maintainers usually reply within 1 day
-
Preview NuGet packages produce NU3018, NU3027, and NU3042 signature warningsPossibly taken @dvoituron claimed this 17 days ago. Openstatus:needs-investigation v5
microsoft/fluentui-blazor#5252 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in microsoft/fluentui-blazor
Similar issues
-
.NET triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/agent-framework#8811 ·
Maintainers usually reply within 1 day
-
.NET Docs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
getsentry/sentry-dotnet#5637 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QuantConnect/Lean#9842 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NethermindEth/nethermind#14012 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aws/aws-dotnet-ai#73 ·