Skip to content

Improve Outlook process detection for Cuda links#1

Open
fcilab2024 wants to merge 1 commit intomasterfrom
codex/ensure-compatibility-with-outlook-on-windows-11
Open

Improve Outlook process detection for Cuda links#1
fcilab2024 wants to merge 1 commit intomasterfrom
codex/ensure-compatibility-with-outlook-on-windows-11

Conversation

@fcilab2024
Copy link
Copy Markdown
Owner

Motivation

  • Ensure the app reliably detects when a Cuda-protected link is launched from Outlook (both Classic and the new Outlook app on Windows 11) so the confirmation prompt is shown only when appropriate.
  • Remove duplicated confirmation handling to avoid double logging and duplicate actions after the dialog.

Description

  • Removed the duplicated dialog handling so the user confirmation is logged and acted on only once by keeping a single DialogResult branch.
  • Replaced direct Process.GetProcessById(...).ProcessName usage with a snapshot-based lookup and added GetProcessNameById that reads names via Toolhelp (CreateToolhelp32Snapshot / Process32First / Process32Next).
  • Updated IsCallerOutlook to use GetProcessNameById, fall back to a pid-<id> label when the name cannot be resolved, and log ancestor names consistently before checking IsOutlookProcessName.

Testing

  • No automated tests were run for this change.

Codex Task

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant