Safe migration and observability for async void in legacy .NET codebases
A SaaS platform that scans .NET repositories and analyzes async void usage, call graphs, event-handler patterns, synchronization contexts, and likely behavioral dependencies. It would combine static analysis with optional runtime instrumentation to trace starts, completions, exceptions, and callers, then produce a prioritized migration plan with suggested conversions to Task, safe fire-and-forget wrappers, cancellation handling, and regression alerts.
The problem
Large .NET codebases may contain async void methods outside legitimate top-level event handlers. These fire-and-forget operations make exceptions, completion, cancellation, and execution context difficult to track, while callers may unknowingly depend on non-blocking behavior. Teams lack a safe way to identify dependencies, observe runtime behavior, and gradually migrate the code without introducing regressions.
Who feels this pain
People trying to protect their focus and manage their time run into this often: A SaaS platform that scans .NET repositories and analyzes async void usage, call graphs, event-handler patterns, synchronization contexts, and likely behavioral dependencies. It would combine static analysis with optional runtime instrumentation to trace starts, completions, exceptions, and callers, then produce a prioritized migration plan with suggested conversions to Task, safe fire-and-forget wrappers, cancellation handling, and regression alerts.
Why it matters
Constant distraction is one of the biggest hidden costs of modern work.
Potential SaaS angle
A focused SaaS product built by helping people reclaim the exact kind of focus described here could turn this into a real productivity & time management opportunity — there's already demand behind it.