打包为MS应用商店Appx的WPF程序启动URI的问题

Ah, I’ve dealt with this exact problem when moving desktop apps to MSIX/Appx packages! The root cause is the sandboxed environment that Appx-packaged applications run in—your original Process.Start() calls fail because the sandbox restricts direct access to external processes and system resources. Let’s walk through the two most reliable solutions:

Solution 1: Use UWP Launcher APIs (Store-Compliant) #

This is the recommended approach since it follows Microsoft’s guidelines for packaged apps and works seamlessly with the App Store.

Launching Web URLs #

Replace your Process.Start() calls with the UWP Launcher.LaunchUriAsync() method. Here’s how to implement it:

1. First, add the necessary using directive to your WPF code:

   using Windows.System;
   

2. Update your URL-launching code to use the async API:

   private async void OpenWebUrl(string url)
   {
       var targetUri = new Uri(url);
       bool launchSuccess = await Launcher.LaunchUriAsync(targetUri);
       
       if (!launchSuccess)
       {
           // Handle launch failure (e.g., show an error message to the user)
           MessageBox.Show("Failed to open the web link.");
       }
   }
   

Launching Local File Paths #

For local files, you’ll need to use Launcher.LaunchFileAsync(), but first ensure your app has permission to access the target file:

1. Add the required using directives:

   using Windows.Storage;
   using Windows.System;
   

2. Implement the file-launching logic:

   private async void OpenLocalFile(string filePath)
   {
       try
       {
           // Get a StorageFile reference to the target file
           StorageFile targetFile = await StorageFile.GetFileFromPathAsync(filePath);
           
           bool launchSuccess = await Launcher.LaunchFileAsync(targetFile);
           
           if (!launchSuccess)
           {
               MessageBox.Show("Failed to open the file.");
           }
       }
       catch (UnauthorizedAccessException)
       {
           // Handle permission issues—your app doesn't have access to this path
           MessageBox.Show("Permission denied: Cannot access this file path.");
       }
       catch (FileNotFoundException)
       {
           MessageBox.Show("The specified file was not found.");
       }
   }
   

3. Configure File Permissions (if needed):

   • If you’re accessing files in standard libraries (Documents, Pictures, etc.), open your Package.appxmanifest, go to the Capabilities tab, and check the corresponding library access boxes.
   • For access to arbitrary file paths, enable the BroadFileSystemAccess capability (note: this requires justification when submitting to the Microsoft Store, and users must grant permission during app installation).

Solution 2: Enable Full Trust (Legacy Code Compatibility) #

If you want to keep using your original Process.Start() code without major changes, you can configure your packaged app to run with full trust:

1. Open your Windows Application Packaging Project.
2. Double-click Package.appxmanifest to open it.
3. Switch to the Capabilities tab and check the Full Trust Application option.
4. Alternatively, edit the manifest XML directly to add this capability:

   <Capabilities>
       <rescap:Capability Name="runFullTrust" />
   </Capabilities>
   

Once enabled, your existing Process.Start() calls should work as they did in the MSI version. Keep in mind that full trust requires additional scrutiny during Microsoft Store submission—you’ll need to explain why your app needs this level of access.

Key Notes #

• Always test your code in the packaged environment (not just debugging the raw WPF project) to catch sandbox-related issues early.
• Avoid accessing sensitive system paths (like C:\Windows) even with full trust, as this may lead to Store rejection.
• The UWP Launcher APIs are asynchronous, so make sure to use async/await properly to avoid blocking the UI thread.

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