Skip to content

[AI-Suggested] Content update request from UUF signal: Build a Blazor movie database app (Part 2 - Add and scaffold a model) | Microsoft Learn #37996

Open

Description

@gewarren

Documentation Update: Build a Blazor movie database app (Part 2 - Add and scaffold a model) | Microsoft Learn

Customer Feedback

Page: Build a Blazor movie database app (Part 2 - Add and scaffold a model) | Microsoft Learn
Source File: https://github.com/dotnet/AspNetCore.Docs/blob/live/aspnetcore/blazor/tutorials/movie-database-app/part-2.md

Summary

Align the tutorial so it consistently uses a single EF Core database provider (SQLite or SQL Server) across the CLI/package installation steps and the DbContext registration/configuration code, removing the current mixed guidance.

Suggested Fixes

Instructions for Copilot: Copilot should only fix suggestions with a checkmark and do not make any updates for unchecked suggestions.

Note

Suggestions are generated by AI and they should be reviewed by human before assigning it to Copilot. Please uncheck the ones you don't want Copilot to work on. Then assign this issue to Agent (GitHub Copilot). When assigning it to Copilot you can enter additional instructions under "Optional Prompt" dialog.

  • In the “Add NuGet packages and tools” section and the later DbContext/provider configuration snippet (typically in Program.cs), choose one provider for the walkthrough and make all commands/snippets match it. If the intent is SQLite (as implied by the CLI instructions), remove the SQL Server provider package and update the code snippet to use UseSqlite.

    Example fix (SQLite end-to-end):

    • Update package commands to include only SQLite:
      dotnet add package Microsoft.EntityFrameworkCore.Sqlite
      dotnet add package Microsoft.EntityFrameworkCore.Tools
      (Remove any dotnet add package Microsoft.EntityFrameworkCore.SqlServer line.)
    • Update Program.cs (or the section that registers the context) from SQL Server to SQLite:
      builder.Services.AddDbContext<BlazorWebAppMoviesContext>(options =>
          options.UseSqlite(builder.Configuration.GetConnectionString("BlazorWebAppMoviesContext")
              ?? "Data Source=BlazorWebAppMovies.db"));
    • Update appsettings.json connection string accordingly:
      {
        "ConnectionStrings": {
          "BlazorWebAppMoviesContext": "Data Source=BlazorWebAppMovies.db"
        }
      }

    Ensure any dotnet ef migrations / dotnet ef database update steps remain valid for the selected provider.

    (If the intended provider is SQL Server instead, make the opposite change: remove SQLite package/CLI references and ensure the snippet uses UseSqlServer with a SQL Server connection string.)


📚 To learn more about agentic content maintenance workflow, visit Agentic workflow for Learn content maintenance. Sign in using Learn Profile to access the content on this link.

💬 Share your feedback on the Learn Content Maintenance Agentic Workflow here.

Activity

  1. self-assigned this
    on Oct 26, 2026
  2. guardrex commented on Oct 26, 2026

    @guardrex
    Collaborator

    @gewarren ... We have to be very careful about these updates because the tutorial adopts different dB providers by platform by design. I'll examine the tutorial and compare it to the AI analysis to see if changes are truly needed.

  3. gewarren commented on Oct 26, 2026

    @gewarren
    CollaboratorAuthor

    The verbatim that prompted this issue is:

    The content uses Sqlite for generating the database when using the CLI instructions. However the code snippet uses SQLServer. The documentation needs to be properly updated. 7/3/2026, 1:02:33 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions