The host product's new release changed its .NET
How you'll know: After the yearly Revit or AutoCAD upgrade, the add-in doesn't load at all.
Fix: Autodesk moved its 2025 products from .NET Framework 4.8 to .NET 8, so older add-ins need retargeting and rebuilding. Keep one build per host version you support, and test it before the office upgrades.
The runtime isn't on the new machine
How you'll know: It runs on the laptop it was built on. On a new PC it asks to download .NET, or opens and does nothing.
Fix: Publish it self-contained so the runtime travels with the app, or install the right .NET Desktop Runtime as part of setup. Pick one and write it in the install notes.
Updates installed by walking round the office
How you'll know: Three versions of the tool are in use, and they give three slightly different numbers.
Fix: Ship it through an installer that updates itself, such as ClickOnce or MSIX, so every PC picks up the same build without anyone visiting it.
An unsigned installer
How you'll know: SmartScreen warns staff the app is from an unknown publisher, and IT blocks it.
Fix: Sign the installer and the app with a code-signing certificate your company owns, not one that belongs to whoever built it.
A service running as someone's own login
How you'll know: The overnight file job stopped the day an employee changed their password or left.
Fix: Run it under its own service account with only the folder and database rights it needs, and log each run to the Windows Event Log or a file someone reads.