如何制作包含FFmpeg安装的C# YouTube MP3下载器安装包？

Hey Konrad! Great question—packaging your C# YouTube MP3 downloader with FFmpeg included is totally manageable, and there are a couple of solid tools to get this done right. Let’s walk through the two most popular approaches, since they’re both well-suited for .NET projects.

Option 1: WiX Toolset (Integrated with Visual Studio) #

WiX is a powerful, MSI-based tool that integrates seamlessly with Visual Studio, making it a great fit for .NET developers. Here’s how to include FFmpeg:

1. Prepare FFmpeg Files

   • Download the appropriate FFmpeg build (match your app’s architecture: x86/x64), extract the bin folder containing ffmpeg.exe (and ffprobe.exe if your app uses it).
   • Add these files to your C# project, then set their Copy to Output Directory property to Copy if newer or Copy always. This ensures they’re in your build output folder.

2. Create a WiX Setup Project

   • Install the WiX Toolset extension for Visual Studio.
   • Add a new "WiX Setup Project" to your solution.
   • Right-click the setup project > Add > Project Output, then select the primary output of your downloader app.

3. Add FFmpeg to the Installer

   • Open the Product.wxs file in your WiX project.
   • Inside the <DirectoryRef Id="INSTALLFOLDER"> element, add a <Component> for each FFmpeg executable. Replace the GUID with a new unique one (generate one via Tools > Create GUID in Visual Studio):

     <Component Id="FFmpegExe" Guid="YOUR-UNIQUE-GUID-HERE">
         <File Id="ffmpeg.exe" Source="$(var.YourDownloaderProject.TargetDir)ffmpeg.exe" KeyPath="yes" />
         <File Id="ffprobe.exe" Source="$(var.YourDownloaderProject.TargetDir)ffprobe.exe" />
     </Component>
     

   • Make sure this component is referenced in your <Feature> element so it gets installed:

     <Feature Id="ProductFeature" Title="YouTube MP3 Downloader" Level="1">
         <ComponentRef Id="ProductComponent" /> <!-- Your main app -->
         <ComponentRef Id="FFmpegExe" /> <!-- FFmpeg files -->
     </Feature>
     

4. Build and Test

   • Build the WiX project to generate the MSI installer. When users run it, FFmpeg will be installed to the same directory as your app, so your code can reference it via a relative path like:

     var ffmpegPath = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "ffmpeg.exe");
     

Option 2: Inno Setup (Lightweight, Easy to Use) #

Inno Setup is a lightweight, script-based installer tool that’s perfect if you want a simpler setup without Visual Studio integration. Here’s how to set it up:

1. Prepare FFmpeg Files

   • Same as above: get the right FFmpeg build, add the bin files to your project’s output directory.

2. Write the Inno Setup Script

   • Download and install Inno Setup, then create a new .iss script file.
   • Use this template, replacing placeholders with your app’s details:

     [Setup]
     AppName=My YouTube MP3 Downloader
     AppVersion=1.0
     DefaultDirName={pf}\YouTubeMP3Downloader
     DefaultGroupName=YouTube MP3 Downloader
     OutputDir=.\InstallerOutput
     OutputBaseFilename=YouTubeMP3Downloader_Setup
     
     [Files]
     ; Your main application executable
     Source: "bin\Release\YourDownloader.exe"; DestDir: "{app}"; Flags: ignoreversion
     ; FFmpeg files
     Source: "bin\Release\ffmpeg.exe"; DestDir: "{app}"; Flags: ignoreversion
     Source: "bin\Release\ffprobe.exe"; DestDir: "{app}"; Flags: ignoreversion
     
     [Icons]
     ; Start menu shortcut
     Name: "{group}\YouTube MP3 Downloader"; Filename: "{app}\YourDownloader.exe"
     ; Desktop shortcut (optional)
     Name: "{commondesktop}\YouTube MP3 Downloader"; Filename: "{app}\YourDownloader.exe"; Flags: commonpath
     

3. Compile and Test

   • Open the script in Inno Setup Compiler, click "Compile" to generate the setup EXE. When installed, FFmpeg will live alongside your app, and your C# code can reference it the same way as with WiX.

Bonus: Download FFmpeg During Installation (Reduce Installer Size) #

If you don’t want to bundle FFmpeg (to keep your installer small), you can add a step to download it during installation. For Inno Setup, add this to your script’s [Run] section (using PowerShell to handle download/extraction):

[Run]
; Download FFmpeg zip to temp folder
Filename: "powershell.exe"; Parameters: "-Command ""Invoke-WebRequest -Uri 'https://ffmpeg.org/releases/ffmpeg-6.0-full_build.zip' -OutFile '{tmp}\ffmpeg.zip'"""; Flags: runhidden waituntilterminated
; Extract the zip
Filename: "powershell.exe"; Parameters: "-Command ""Expand-Archive -Path '{tmp}\ffmpeg.zip' -DestinationPath '{tmp}\ffmpeg'"""; Flags: runhidden waituntilterminated
; Copy ffmpeg.exe to app directory
Filename: "cmd.exe"; Parameters: "/C copy ""{tmp}\ffmpeg\bin\ffmpeg.exe"" ""{app}\ffmpeg.exe"""; Flags: runhidden waituntilterminated

Note: Update the FFmpeg download URL to match the latest version and your app’s architecture.

Important Notes #

• FFmpeg Licensing: Make sure you comply with FFmpeg’s LGPL/GPL license terms. If your app is closed-source, use a build that doesn’t include GPL-licensed components, or provide clear attribution and access to FFmpeg’s source code.
• Architecture Matching: Always use an FFmpeg build that matches your app’s target platform (x86 vs x64) to avoid runtime errors.
• Path Testing: Verify your app can locate FFmpeg by using relative paths (as shown earlier) instead of hardcoding absolute paths.

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