Skip to content

Conversation

@enisn
Copy link
Member

@enisn enisn commented Nov 20, 2025

Description

Adjusted instructions to reference the correct Components/Pages folder for BlazorServer projects instead of Pages, ensuring clarity for users following the tutorial.

Resolves https://github.com/volosoft/vs-internal/issues/6875

Closes https://github.com/volosoft/vs-internal/issues/7055

Checklist

  • I fully tested it as developer / designer and created unit / integration tests
  • I documented it (or no need to document or I will create a separate documentation issue)

Adjusted instructions to reference the correct `Components/Pages` folder for BlazorServer projects instead of `Pages`, ensuring clarity for users following the tutorial.
@enisn enisn added this to the 10.0-patch milestone Nov 20, 2025
@enisn enisn requested a review from EngincanV November 20, 2025 11:29
Adjusted the namespace declaration in the Blazor tutorial to conditionally use 'TodoApp.Pages' for Blazor UI and 'TodoApp.Components.Pages' otherwise. This clarifies the correct namespace usage based on the UI framework.
@EngincanV EngincanV merged commit 3bb9ff9 into rel-10.0 Nov 20, 2025
2 checks passed
@EngincanV EngincanV deleted the 10.0-blazor-docs-fix branch November 20, 2025 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants