如何检测应用程序安装后的首次运行（含卸载重装场景）

Great question! The problem with your current Properties.Settings approach is that the configuration file lives in the user's AppData folder, which almost all uninstallers leave untouched. So when someone reinstalls your app, the old CheckFirstTime value is still there, and your code thinks it's not a first run.

Since you want to avoid databases, here are three practical, lightweight solutions to fix this:

1. Use a Unique Flag File Tied to Your App's Install Instance #

Create a separate file (independent of app settings) linked to your app's unique product GUID or installation path. This way, if the app is uninstalled and reinstalled, you can either have the installer clean up the file, or use logic to detect a new installation.

Example Code (C#): #

using System.IO;
using System.Windows.Forms;

public void CheckFirstRun()
{
    // Replace this with your app's unique Product GUID (from your installer)
    string productGuid = "YOUR_APP_UNIQUE_GUID";
    string appDataFolder = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData), "YourAppName");
    string flagFilePath = Path.Combine(appDataFolder, $"FirstRun_{productGuid}.txt");

    if (!File.Exists(flagFilePath))
    {
        // Execute first-run logic
        MessageBox.Show("1st run (including after reinstall!)");
        
        // Create the folder and flag file
        Directory.CreateDirectory(appDataFolder);
        using (File.Create(flagFilePath)) { } // Quick way to create an empty file
    }
    else
    {
        MessageBox.Show("Later run");
    }
}

How it works: If you use an MSI installer, you can add a custom action to delete this file during uninstall. Even if you don't, using a unique product GUID ensures that if you ever release a new version with a different GUID, it'll trigger a first run.

2. Check Your App's Executable Creation Time #

This method compares the creation time of your app's main .exe file with a stored timestamp. If the .exe is newer than the stored time, it means the app was reinstalled (or updated), so you treat it as a first run.

Example Code (C#): #

using System.IO;
using System.Windows.Forms;

public void CheckFirstRunAfterReinstall()
{
    string exePath = Application.ExecutablePath;
    FileInfo exeInfo = new FileInfo(exePath);
    DateTime currentExeCreationTime = exeInfo.CreationTime;

    string appDataFolder = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData), "YourAppName");
    string timestampFilePath = Path.Combine(appDataFolder, "InstallTimestamp.txt");

    if (!File.Exists(timestampFilePath))
    {
        // First run ever
        MessageBox.Show("1st run");
        Directory.CreateDirectory(appDataFolder);
        File.WriteAllText(timestampFilePath, currentExeCreationTime.ToString());
    }
    else
    {
        string storedTimestamp = File.ReadAllText(timestampFilePath);
        if (DateTime.TryParse(storedTimestamp, out DateTime storedTime))
        {
            if (currentExeCreationTime > storedTime)
            {
                // App was reinstalled/updated—treat as first run
                MessageBox.Show("1st run after reinstall!");
                File.WriteAllText(timestampFilePath, currentExeCreationTime.ToString());
            }
            else
            {
                MessageBox.Show("Later run");
            }
        }
        else
        {
            // Corrupted timestamp—reset to first run
            MessageBox.Show("1st run (corrupted timestamp)");
            File.WriteAllText(timestampFilePath, currentExeCreationTime.ToString());
        }
    }
}

How it works: Every time you reinstall the app, the .exe file gets a new creation time. This method automatically detects that and resets the first-run flag, no installer configuration needed.

3. Use User-Level Registry Entries #

Instead of a file, you can store a first-run flag in the user's registry (under HKCU, so no admin rights needed). Like the file method, you can tie it to your app's product GUID or installation path.

Example Code (C#): #

using Microsoft.Win32;
using System.Windows.Forms;

public void CheckFirstRunWithRegistry()
{
    string productGuid = "YOUR_APP_UNIQUE_GUID";
    string registryPath = $"Software\\YourAppName\\Installs\\{productGuid}";

    using (RegistryKey key = Registry.CurrentUser.OpenSubKey(registryPath))
    {
        if (key == null)
        {
            // First run
            MessageBox.Show("1st run (including after reinstall!)");
            
            // Create the registry key to mark first run as complete
            Registry.CurrentUser.CreateSubKey(registryPath);
        }
        else
        {
            MessageBox.Show("Later run");
        }
    }
}

How it works: Similar to the file approach, you can configure your installer to delete this registry key during uninstall. If you don't, the unique product GUID ensures new installations (with a new GUID) will trigger a first run.

All these methods avoid databases and solve the reinstall detection problem—pick the one that fits your installer setup and app needs best!

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