如何在Web API项目中定义初始URL？Mac下VS Code配置故障求助

Hey there! Let's figure out why your default page setup in Startup.cs isn't working and you're hitting that "controller not found" error. I've run into this a bunch of times, so here are the most common fixes to walk through:

1. Double-check your default route configuration (ASP.NET Core) #

First, make sure you've set up the default route correctly in the Configure method of Startup.cs. If you're using MVC, your endpoint mapping needs to explicitly define the fallback controller and action. Here's what that should look like:

public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
    // Keep your existing middleware (like error pages) here
    
    // If you want to use a static index.html as the default, add this BEFORE routing
    app.UseStaticFiles();

    app.UseRouting();

    // Add authorization if your project uses it
    app.UseAuthorization();

    app.UseEndpoints(endpoints =>
    {
        // This sets Home/Index as the default route
        endpoints.MapControllerRoute(
            name: "default",
            pattern: "{controller=Home}/{action=Index}/{id?}");
    });
}

If you're aiming for a static HTML page (like wwwroot/index.html), ensure UseStaticFiles() comes before UseRouting—this tells the app to check for static files first before hitting the controller route.

2. Verify your controller exists and is named correctly #

The "controller not found" error often boils down to a missing or misnamed controller:

• You need a controller class named HomeController (the Controller suffix is mandatory—Home alone won't work!)
• Inside that controller, you need an Index action method. Here's a minimal example:

public class HomeController : Controller
{
    public IActionResult Index()
    {
        return View(); // Or return Content("Test page"); for quick testing
    }
}

Also, make sure you've added MVC services in ConfigureServices:

public void ConfigureServices(IServiceCollection services)
{
    // For MVC projects with views
    services.AddControllersWithViews();
    // For API-only projects (though API usually doesn't use default pages)
    // services.AddControllers();
}

3. Fix your middleware order #

Middleware order is critical in ASP.NET Core—if you have it wrong, your routing won't fire as expected. Stick to this general order:

• UseDeveloperExceptionPage() (only for development)
• UseStaticFiles()
• UseRouting()
• UseAuthorization()
• UseEndpoints()

For example, if UseEndpoints comes before UseStaticFiles, your static default page will never be prioritized.

4. Clean and rebuild your project #

Sometimes VS Code or the .NET CLI leaves behind cached builds that cause weird issues. Run these commands in your terminal:

dotnet clean
dotnet build
dotnet run

This clears old artifacts and ensures you're running the latest code.

5. Check your launch settings #

Open Properties/launchSettings.json and make sure the launchUrl isn't set to a non-existent path. A blank launchUrl will use your default route, which is what you want:

"profiles": {
  "YourProjectName": {
    "commandName": "Project",
    "launchBrowser": true,
    "launchUrl": "",
    "environmentVariables": {
      "ASPNETCORE_ENVIRONMENT": "Development"
    }
  }
}

Start with these steps—9 times out of 10, one of these will fix the issue. Let me know if you still hit snags after trying them!

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