Why should you care?

Every page needs CSS and JS. Serving them efficiently reduces server load and improves load time.

See it live — copy this example

Create an MVC project (dotnet new mvc), add the code, and run dotnet run.

app.UseStaticFiles();

// Optional — second folder
app.UseStaticFiles(new StaticFileOptions {
    FileProvider = new PhysicalFileProvider(
        Path.Combine(builder.Environment.ContentRootPath, "Uploads")),
    RequestPath = "/uploads"
});

Run Example »

Edit the code and click Run — like W3Schools Try it Yourself.

What happened?

• UseStaticFiles must appear before routing in typical setups.
• Default cache headers can be tuned for production CDN.

Try it yourself

1. Confirm UseStaticFiles in Program.cs.
2. Request a missing file — 404 from static middleware.
3. Add cache-control headers in production config if needed.
4. Change text or labels in the example and run again — watch the browser update.
5. Break the code on purpose (remove a semicolon), read the error message, then fix it.

Remember

UseStaticFiles enables wwwroot. Runs early in the pipeline. Can map extra folders with RequestPath.