Let's work through this deployment problem step by step—missing dist files and the "SPA default page middleware could not return /index.html" error are common gotchas, but easy to resolve with a few targeted tweaks.

1. Ensure ClientApp/dist Automatically Copies to Publish Output #

First, let's fix the root issue of your dist folder not being included in the publish output. Manually copying files isn't sustainable, so add this to your .csproj file:

<ItemGroup>
  <!-- Copy Vue's built dist folder to publish directory -->
  <Content Include="ClientApp\dist\**">
    <CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
  </Content>
</ItemGroup>

This tells MSBuild to copy every file in ClientApp/dist to the publish directory's matching ClientApp/dist path during the publish process. No more manual file shuffling!

2. Correct the UseSpa Configuration in Startup.cs #

Your current Startup config has a small ambiguity with how it references production static files. Let's update it to explicitly point the middleware to the correct dist location, and fix middleware execution order:

using System.IO;
// ... other using statements

public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
    // ... other middleware (like routing, authorization)

    // First, enable static file serving—critical for SPA assets to be accessible
    app.UseStaticFiles();

    app.UseSpa(spa =>
    {
        // Set base source path for all SPA operations
        spa.Options.SourcePath = "ClientApp";

        if (env.IsDevelopment())
        {
            // Only use Vue CLI dev server in development mode
            spa.UseVueCli(npmScript: "serve");
        }
        else
        {
            // Explicitly tell the middleware where to find production SPA files
            spa.Options.DefaultPageStaticFileOptions = new StaticFileOptions
            {
                FileProvider = new PhysicalFileProvider(
                    Path.Combine(Directory.GetCurrentDirectory(), "ClientApp", "dist"))
            };
        }
    });
}

Key fixes here: #

• UseStaticFiles() is called before UseSpa()—middleware runs in order, so static files need to be accessible first.
• Production mode uses a PhysicalFileProvider to point directly to ClientApp/dist, eliminating any ambiguity about where index.html lives.
• Consistent casing (ClientApp instead of mixed clientapp) avoids issues on case-sensitive OSes like Linux.

3. Verify Publish Directory Structure #

After publishing, your output folder should follow this structure exactly:

publish/
├── YourApplication.dll
├── YourApplication.pdb
├── ... other .NET runtime files
└── ClientApp/
    └── dist/
        ├── index.html
        ├── js/
        ├── css/
        └── assets/

If you still need to manually copy files temporarily, make sure you match this structure—don't place dist directly in the publish root or rename folders.

4. Confirm Production Environment is Set #

When running the published DLL, ensure the ASPNETCORE_ENVIRONMENT variable is set to Production. If it's accidentally set to Development, the middleware will try to connect to the Vue CLI dev server (which isn't running in production), causing errors.

• Windows Command Prompt:

  set ASPNETCORE_ENVIRONMENT=Production
  dotnet YourApplication.dll
  

• Linux/macOS Terminal:

  export ASPNETCORE_ENVIRONMENT=Production
  dotnet YourApplication.dll
  

After making these changes, republish your app and run the DLL—you should no longer see the "default page not found" error.

内容的提问来源于stack exchange，提问作者Mikkel