Outlook AddIn Checklist

Version: 2.1
Scope: VSTO/COM patterns, Ribbon/UI state, and deployment hygiene.

MUST

  • [ ] Explorer vs Inspector contexts are handled explicitly; no cross-contamination of state
  • [ ] UI toggles reflect the current pane state reliably across windows
  • [ ] COM objects are released deterministically; no event handler leaks
  • [ ] Threading model is respected (UI thread affinity); no blocking calls in UI events
  • [ ] Add-in startup and shutdown are resilient; failure does not break Outlook session
  • [ ] Sensitive data is not stored in item properties unless encrypted and explicitly required
  • [ ] Logging avoids PII and secret leakage; errors are mapped without oracle behavior

SHOULD

  • [ ] Feature flags/config can disable risky features without redeploy
  • [ ] Clear versioning and compatibility statement (Office versions, 32/64-bit, Office.js/VSTO)

NICE

  • [ ] Provide diagnostic mode with safe redactions
  • [ ] Add integration tests for ribbon callbacks and pane toggle logic

Version: 2.1 (Split)
Author: Wolfgang van der Stille

Back to Stack Checklists | Review Checklists

Zuletzt geändert: on 2026/01/08 at 01:50 AM