Severity: Info
Related: Follow-up to #724

#724 flagged the Process.GetCurrentProcess().MainModule!.FileName! null-forgiving pattern in RotatingStreamWriter.cs:449 and explicitly noted: "The same fallback pattern is worth reusing anywhere else the codebase needs 'the app's install directory'."

Seven additional callsites use the same (or a weaker, unguarded) pattern and are still unfixed:

Callsites 6 and 7 are arguably worse than #724 because they do not even suppress the warning — any null MainModule surfaces as a plain NullReferenceException inside App.OnStartup, crashing the WPF application before the dispatcher unhandled-exception handler is wired.

Suggested fix:

Extract the fallback chain from #724 into a shared helper (e.g. AppConfig.GetAppBaseDirectory() or PathHelper.GetAppInstallDirectory()) and replace all eight callsites (the original plus these seven) with a single call. This also removes the duplication that would otherwise force a seven-copy fix when #724 is addressed.

public static string GetAppInstallDirectory()
{
    try
    {
        var fileName = Process.GetCurrentProcess().MainModule?.FileName;
        if (!string.IsNullOrEmpty(fileName))
        {
            var dir = Path.GetDirectoryName(fileName);
            if (!string.IsNullOrEmpty(dir)) return dir;
        }
    }
    catch { /* restricted session */ }

    return AppContext.BaseDirectory;
}