Outlook运行时安装的ClickOnce版VSTO Add-In无法加载，如何免重启加载？

Great question—this is a super common pain point with VSTO add-ins and ClickOnce. The good news is there are a couple of reliable ways to load your add-in immediately after installation without forcing users to restart Outlook. Let’s break them down:

1. COM Automation + Post-Install Script (Most Reliable) #

This method uses Outlook’s COM object model to manually trigger your add-in’s load from a script that runs right after ClickOnce finishes installing. It’s the most stable approach I’ve used in production.

Step 1: Prepare Your Add-In for External Automation (Optional but Useful) #

First, expose an initialization method so external scripts can kick off your add-in’s logic once loaded:

protected override object RequestComAddInAutomationService()
{
    return new AddInAutomationHelper();
}

[ComVisible(true)]
public class AddInAutomationHelper
{
    public void InitializeAddIn()
    {
        // Run your add-in's core setup logic here
        ThisAddIn.Current.SetupToolbar();
        ThisAddIn.Current.LoadSettings();
    }
}

Step 2: Write a Post-Install PowerShell Script #

This script connects to the running Outlook instance and enables your add-in. Replace the ProgID with the one from your VSTO project properties:

try {
    # Grab the active Outlook application instance
    $outlook = [System.Runtime.InteropServices.Marshal]::GetActiveObject('Outlook.Application')
    
    # Replace with your add-in's ProgID (found in Project > Properties > Publish > Options > Manifests)
    $addInProgId = "YourVSTOAddIn.Connect"
    
    $comAddIn = $outlook.COMAddIns.Item($addInProgId)
    
    if (-not $comAddIn.Connect) {
        $comAddIn.Connect = $true
        # Optional: Trigger your initialization method
        $automationObj = $comAddIn.Object
        $automationObj.InitializeAddIn()
        Write-Host "Add-in loaded successfully—no restart needed!"
    }
}
catch {
    Write-Warning "Couldn't load add-in automatically: $_"
    # Fallback: Prompt user to restart Outlook if the script fails
    [System.Windows.MessageBox]::Show("Please restart Outlook to finish loading the add-in.", "Info")
}

Step 3: Hook the Script to ClickOnce’s Post-Install Event #

• In your ClickOnce project settings, add a custom action to run this script after installation. For .NET apps, you can also trigger it programmatically using ApplicationDeployment.CurrentDeployment in your post-install logic.

2. Hacky Quick Fix: Force Outlook to Rescan Add-Ins #

If you want a simpler (but less reliable) approach, use Windows API to send a refresh signal to Outlook. Note this works best with older Outlook versions:

[DllImport("user32.dll", CharSet = CharSet.Auto)]
private static extern IntPtr SendMessage(IntPtr hWnd, uint Msg, IntPtr wParam, IntPtr lParam);

private void RefreshOutlookAddIns()
{
    var outlookProcesses = Process.GetProcessesByName("OUTLOOK");
    foreach (var proc in outlookProcesses)
    {
        // Replace 0x7D0 with the correct refresh command ID for your Outlook version (you may need to look this up)
        SendMessage(proc.MainWindowHandle, 0x0111, (IntPtr)0x7D0, IntPtr.Zero);
    }
}

Critical Tips to Avoid Headaches #

• User Context: Ensure the script runs as the same user who’s running Outlook (ClickOnce installs per-user by default, so this is usually covered).
• Multiple Instances: If users have multiple Outlook profiles open, your script needs to target each running process.
• Security: Some Outlook versions block external COM calls by default. Add your add-in to Outlook’s trusted add-ins list via ClickOnce manifest or group policy to avoid this.

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