部署ASP.NET Core 2至IIS后异常的解决方法咨询

Hey there, let's work through these IIS deployment issues together—since your app runs fine locally (both Debug/Release, direct run or IIS Express) but breaks on full IIS, the culprit is almost always related to server configuration, file paths, permissions, or static asset loading. Here's a step-by-step breakdown to fix it:

• Check .NET Version & Hosting Mode:
  • If you're using .NET Framework, ensure your app pool targets the correct .NET version (e.g., v4.0) and is set to Integrated managed pipeline mode (avoid Classic mode—it causes routing and static file issues).
  • If you're on .NET Core, make sure the .NET Core Hosting Bundle is installed on the server. Set your app pool to No Managed Code (since .NET Core handles its own runtime).
• Confirm Physical Path: Double-check that your IIS site's physical path points directly to the root folder of your published app (e.g., C:\inetpub\wwwroot\YourApp). If the path is wrong, IIS can't find your controllers or static files.
• Set Folder Permissions: Grant the IIS_IUSRS and IUSR accounts Read & Execute, List Folder Contents, and Read permissions on your app's published folder. Right-click the folder → Properties → Security → Edit → Add these accounts and apply the permissions.

• Validate Default Route:
  • For .NET Framework, open RouteConfig.cs and confirm your default route points to the Home controller's Index action:

    routes.MapRoute(
        name: "Default",
        url: "{controller}/{action}/{id}",
        defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
    );
    

  • For .NET Core, check Program.cs to ensure you have the default controller route configured, and that routing middleware is added in the correct order:

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

• Check for Route Conflicts: Make sure no other routes are overriding the default Home/Index route (e.g., attribute routes on other controllers that might catch the root URL).

• Fix Resource Paths: Always use root-relative paths (starting with ~/) for static assets like CSS, JS, and images. For example:

  <script src="~/Scripts/jquery.min.js"></script>
  <link href="~/Content/site.css" rel="stylesheet" />
  

  This ensures the path resolves correctly regardless of IIS virtual directories.
• Ensure Static Files Are Published:
  • For .NET Framework: Right-click your project → Properties → Build → Ensure "Copy to Output Directory" is set to Copy always or Copy if newer for your static files (Scripts, Content folders).
  • For .NET Core: In your publish profile, make sure "Include all files from the project directory" is enabled, or check that your .csproj has <Content Include="**/*" CopyToPublishDirectory="PreserveNewest" /> for static assets.
• Enable Static Files in IIS: In IIS Manager, select your site, double-click the Static Files feature, and confirm it's set to Enabled. For .NET Core, also ensure app.UseStaticFiles(); is added in Program.cs before routing middleware.

By default, IIS hides detailed errors to protect server info—turn this on to see exactly what's breaking:

• .NET Framework: Add this to your web.config inside <system.web>:

  <customErrors mode="Off" />
  

• .NET Core: Update appsettings.json:

  "DetailedErrors": true,
  "Logging": {
      "LogLevel": {
          "Default": "Information",
          "Microsoft.AspNetCore": "Warning"
      }
  }
  

Restart your IIS site, then try accessing the homepage again—you'll get a specific error (e.g., "jQuery not found", "Permission denied", "Route not matched") that points directly to the issue.

Sometimes Release mode optimizations (like bundling/minification) can break paths. Try publishing in Debug mode first to see if the problem goes away. If it does:

• Check your bundling configuration (e.g., BundleConfig.cs in .NET Framework) to ensure bundle paths are correct for IIS.
• Disable bundling temporarily to confirm it's the cause, then adjust the configuration to work with your IIS setup.

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