在Visual Studio 2019中为WPF Core 3.1制作安装程序后生成DLL而非EXE如何解决？

Hey there, I’ve run into this exact issue before with .NET Core WPF installers—let’s walk through the steps to get your EXE showing up post-install:

1. Verify You’re Adding Project Output, Not Raw DLLs #

This is the most common culprit. In your VS2019 Installer Project:

• Right-click the installer project > Add > Project Output
• Select your WPF Core 3.1 project from the dropdown
• Make sure to check both Primary Output and Content Files—Primary Output includes your compiled EXE, while Content Files pulls in necessary assets like appsettings.json or resource files.

2. Check Your WPF Project’s Build/Publish Settings #

First, confirm your project is actually configured to generate an EXE:

• Open your WPF project’s properties, go to the Build tab
• Open the advanced build settings (small button at the bottom right) and ensure Output type is set to Windows Application (not Class Library). You can also verify this directly in your .csproj file—look for this line:

  <OutputType>WinExe</OutputType>
  

• Next, head to the Publish tab:
  • Choose your target runtime (x64, x86, or Any CPU) to match your installer project’s target platform
  • If using framework-dependent deployment, ensure the "Produce single file" option isn’t enabled unless you specifically want that (though single-file should still generate an EXE, it’s worth ruling out as a potential issue)

3. Align Installer Project Target Platform with WPF Project #

Mismatched platforms often cause missing files:

• Right-click your installer project > Properties
• Set the Target Platform to match your WPF project (e.g., x64 if your WPF app is built for x64)
• Return to the File System view of the installer, and re-add the Primary Output if you changed the platform—this ensures it pulls the correct build artifacts.

4. Validate the MSI Contains the EXE Before Installing #

Before running the installer, confirm the EXE is included in the MSI:

• You can use a tool like Orca (part of the Windows SDK) to open the MSI and inspect the File table, or simply rename the MSI to .zip and extract its contents
• If the EXE is missing here, the problem lies in the packaging step—double-check steps 1-3 to ensure you’re pulling the right output from your WPF project.

5. Check Installed Application Directory Structure #

If the installer runs but you can’t find the EXE, navigate to the installed directory (default is C:\Program Files\[Your App Name]):

• Sometimes with framework-dependent deployments, the EXE might be in a subfolder under runtime—but this is unusual if you added Primary Output correctly. If this happens, adjust the installer’s file system mappings to move the EXE to the root directory.

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