将.aspx网站迁移至ASP.NET Core（Linux/Apache环境）技术咨询

Alright, let's walk through how to migrate those 40 ASPX sites over to Linux/Apache with ASP.NET Core—this is a common scenario when consolidating legacy hosting, and we can break it down into actionable, manageable steps.

1. 先做站点摸底与分类 #

Before diving into migration, take a day to map out your 40 sites—this will save you tons of headaches later:

• Sort sites by complexity: Flag which are pure Web Forms (.aspx/.ascx) vs. those with mixed MVC, or ones relying on old .NET Framework features (like Web Services, Membership Provider, or COM components).
• Use the dotnet upgrade-assessment analyze tool (install via dotnet tool install -g Microsoft.DotNet.UpgradeAssessment.Tool) to scan each site's codebase. It’ll generate a report of incompatible APIs, missing Linux-compatible dependencies, and high-risk components.
• Pick 1-2 simple, low-traffic sites as your pilot projects. Nail the migration workflow on these first before scaling to the full 40.

2. Choose Your Migration Path (2 Main Options) #

Option A: Upgrade to ASP.NET Core (Long-Term Solution) #

This is the recommended path for sustainability:

• Web Forms to Razor Pages: Microsoft designed Razor Pages as a modern replacement for Web Forms. Convert .aspx pages to .cshtml Razor Pages—most form logic, data binding, and event handlers can be mapped directly to Razor Page handlers (OnGetAsync, OnPostAsync).
• Replace Legacy APIs: Swap out System.Web dependencies for ASP.NET Core equivalents:
  • Replace HttpContext.Current with IHttpContextAccessor (inject it into your pages/services).
  • Swap Response.Redirect for RedirectToPage or Redirect methods.
  • Replace ViewState with session storage (Redis works great for distributed sessions on Linux) or refactor to stateless logic where possible.
• Batch Code Fixes: Use regex find-and-replace in your IDE (VS Code, Rider) to handle repetitive changes—like updating all Page_Load methods to OnGetAsync, or fixing hardcoded Windows file paths to Linux-style paths.

Option B: .NET Framework on Linux (Temporary Transition) #

If some sites have unreplaceable legacy components (e.g., custom COM objects), use this as a stopgap:

• Install Mono or Microsoft’s .NET Framework Linux compatibility layer (note: official support is limited, so this is only for short-term use).
• Configure Apache to reverse-proxy traffic to Mono’s XSP server or a Kestrel instance running the .NET Framework app. Example Apache config snippet:

  <VirtualHost *:80>
      ServerName yoursite.com
      ProxyPass / http://localhost:5000/
      ProxyPassReverse / http://localhost:5000/
      ErrorLog ${APACHE_LOG_DIR}/yoursite-error.log
      CustomLog ${APACHE_LOG_DIR}/yoursite-access.log combined
  </VirtualHost>
  

• Plan to refactor these sites to ASP.NET Core as soon as possible to avoid maintenance overhead.

3. Batch Deployment & Automation #

With 40 sites, manual deployment isn’t feasible—automate everything:

• Containerize with Docker: Package each site into a Docker container using the official ASP.NET Core base image (e.g., mcr.microsoft.com/dotnet/aspnet:6.0). This ensures consistent environments across all Linux servers. A sample Dockerfile might look like:

  FROM mcr.microsoft.com/dotnet/aspnet:6.0
  WORKDIR /app
  COPY . .
  EXPOSE 80
  ENTRYPOINT ["dotnet", "YourSite.dll"]
  

• Automate Apache Configs: Use Ansible or a shell script to generate Apache virtual host files in bulk. The script can pull site names from a CSV, create configs with reverse proxy rules, and reload Apache automatically.
• CI/CD Pipeline: Set up a pipeline (GitHub Actions, GitLab CI) to build Docker images, run tests, and deploy to your Linux servers whenever you push code changes. This eliminates manual deployment errors.

4. Testing & Common Pitfalls to Watch For #

Don’t skip thorough testing—here are the most common issues to check:

• Case Sensitivity: Linux is case-sensitive, so fix all hardcoded file paths and links (e.g., /images/Header.jpg vs. /images/header.jpg).
• File Permissions: Ensure the Apache user (usually www-data) has read/write access to site directories, especially upload folders. Run chown -R www-data:www-data /var/www/your-site to set permissions correctly.
• Database Connections: If your sites use SQL Server, use the official Linux SQL Server container (mcr.microsoft.com/mssql/server) or connect to your existing SQL Server instance via .NET Core’s Microsoft.Data.SqlClient.
• Third-Party Components: Replace any Windows-only libraries (e.g., old PDF generators) with Linux-compatible alternatives (e.g., iTextSharp for .NET Core).

5. Gradual Traffic Switchover #

Avoid a big-bang migration—minimize downtime by rolling out gradually:

• Use DNS weighting or a load balancer to send a small percentage of traffic to the Linux-hosted sites first.
• Monitor logs (Apache access/error logs, .NET Core app logs) closely for errors.
• Keep the original IIS servers online for 2-4 weeks as a rollback option. Once you confirm stability, fully cut over traffic and decommission the old servers.

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