ASP.NET MVC单项目实现指定外观视图的条件发布方案咨询

Great question—this is a super common pain point when scaling multi-theme MVC apps, and I’ve helped several teams refactor this exact setup to cut down on maintenance overhead. Here are three practical solutions, ordered by how easy they are to implement with your current codebase:

1. MSBuild Conditioned Publishing (Quickest Fix for Existing Code) #

This approach lets you keep all themes in a single project, but only publish the selected theme’s Views and CSS by leveraging Visual Studio publish configurations and MSBuild rules.

Step-by-Step Implementation: #

• Refactor your project structure
  Move all theme-specific files into dedicated subdirectories, like this:

  YourProject/
  ├── Views/
  │   ├── Modern/          # All Modern view files
  │   ├── Contemporary/    # All Contemporary view files
  │   └── Shared/          # Shared layouts/partials (if any)
  ├── Content/
  │   ├── CSS/
  │   │   ├── Modern/      # Modern CSS files
  │   │   └── Contemporary/# Contemporary CSS files
  ├── Controllers/         # Shared code (unchanged)
  ├── Models/              # Shared code (unchanged)
  └── Scripts/             # Shared JS (unchanged)
  

• Create publish configurations
  In Visual Studio, go to Build > Configuration Manager and create new release configurations for each theme (e.g., Release-Modern, Release-Contemporary).

• Add MSBuild rules to your .csproj
  Edit your project file to conditionally include/exclude theme files based on the active publish configuration. Here’s a sample snippet:

  <Choose>
    <When Condition="'$(Configuration)' == 'Release-Modern'">
      <ItemGroup>
        <!-- Map Modern views to the standard Views directory -->
        <Content Include="Views\Modern\**\*.cshtml">
          <Link>Views\%(RecursiveDir)%(Filename)%(Extension)</Link>
        </Content>
        <!-- Map Modern CSS to the standard CSS directory -->
        <Content Include="Content\CSS\Modern\**\*.css">
          <Link>Content\CSS\%(RecursiveDir)%(Filename)%(Extension)</Link>
        </Content>
        <!-- Exclude all other theme files -->
        <Content Remove="Views\**\*.cshtml" Exclude="Views\Modern\**\*.cshtml;Views\Shared\**\*.cshtml" />
        <Content Remove="Content\CSS\**\*.css" Exclude="Content\CSS\Modern\**\*.css" />
      </ItemGroup>
    </When>
    <When Condition="'$(Configuration)' == 'Release-Contemporary'">
      <!-- Repeat the same logic for Contemporary -->
      <ItemGroup>
        <Content Include="Views\Contemporary\**\*.cshtml">
          <Link>Views\%(RecursiveDir)%(Filename)%(Extension)</Link>
        </Content>
        <Content Include="Content\CSS\Contemporary\**\*.css">
          <Link>Content\CSS\%(RecursiveDir)%(Filename)%(Extension)</Link>
        </Content>
        <Content Remove="Views\**\*.cshtml" Exclude="Views\Contemporary\**\*.cshtml;Views\Shared\**\*.cshtml" />
        <Content Remove="Content\CSS\**\*.css" Exclude="Content\CSS\Contemporary\**\*.css" />
      </ItemGroup>
    </When>
  </Choose>
  

• Publish to Azure
  When publishing, select the corresponding release configuration (e.g., Release-Modern). Visual Studio or Azure DevOps will only package and deploy the files matching that theme.

2. Runtime Theme Switching + Targeted Publishing #

If you want the flexibility to switch themes post-deployment (or still publish only one theme at a time), this approach uses a custom view engine to load theme-specific files dynamically.

Key Steps: #

• Customize the view engine
  Create a theme-aware view engine that looks for views in the theme directory first:

  public class ThemedViewEngine : RazorViewEngine
  {
      private readonly string _activeTheme;
  
      public ThemedViewEngine(IConfiguration config)
      {
          _activeTheme = config["ActiveTheme"] ?? "Modern";
          // Prioritize themed views over default ones
          ViewLocationFormats = new[]
          {
              $"~/Views/{_activeTheme}/{{1}}/{{0}}.cshtml",
              $"~/Views/{_activeTheme}/Shared/{{0}}.cshtml",
              "~/Views/{1}/{0}.cshtml",
              "~/Views/Shared/{0}.cshtml"
          };
      }
  }
  

  Register it in Startup.cs:

  services.AddControllersWithViews()
      .AddRazorOptions(options =>
      {
          options.ViewEngines.Clear();
          options.ViewEngines.Add(typeof(ThemedViewEngine));
      });
  

• Targeted publishing
  Use MSBuild or Azure DevOps tasks to copy only the selected theme’s files during publishing. For example, in a DevOps pipeline, add a Copy Files task that copies Views/$(SelectedTheme)/** to $(Build.ArtifactStagingDirectory)/Views and Content/CSS/$(SelectedTheme)/** to $(Build.ArtifactStagingDirectory)/Content/CSS.

3. Razor Class Libraries (RCL) for Clean Separation #

For long-term maintainability, package each theme into a separate Razor Class Library. This keeps themes isolated but lets you reference only the one you need for deployment.

Implementation: #

• Create RCLs for each theme
  For each theme, create a new Razor Class Library project. Add all theme-specific Views and CSS to it, and set the RCL to expose these files as content.

• Reference the desired RCL in your main project
  In your main MVC project, add a reference to the RCL for the theme you want to publish. You can use conditional references in your .csproj to switch RCLs based on publish configuration:

  <ItemGroup>
    <ProjectReference Include="..\ModernThemeRCL\ModernThemeRCL.csproj" Condition="'$(Configuration)' == 'Release-Modern'" />
    <ProjectReference Include="..\ContemporaryThemeRCL\ContemporaryThemeRCL.csproj" Condition="'$(Configuration)' == 'Release-Contemporary'" />
  </ItemGroup>
  

• Publish
  When you publish with a specific configuration, only the referenced RCL’s files will be included in the deployment package.

Pro Tips: #

• Use MSBuild variables (e.g., $(ActiveTheme)) to avoid duplicating code in your .csproj for each theme.
• Test publish outputs locally first with dotnet publish -c Release-Modern to verify only the correct files are included.
• For Azure DevOps, create a single pipeline with a dropdown variable to select the theme, then use that variable to set the publish configuration or copy the right files.

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