What problem does it solve?
Thread.Abort-based termination breaks when migrating .NET Framework code to modern .NET because managed threads can’t be forcibly aborted, causing PlatformNotSupportedException and SYSLIB0006 warnings.
Core Features & Use Cases
- Pattern inventory and classification: Locates Thread.Abort, ThreadAbortException, Thread.ResetAbort, Thread.Interrupt, and ASP.NET Response.End/Response.Redirect(url, true) usages and groups them by intent.
- Cooperative cancellation replacements: Converts each pattern to CancellationToken-based control flow, including cancellable loops, timeouts, and blocked-call wakeups, while updating ASP.NET termination behavior.
- Cleanup and verification guidance: Ensures removed APIs are fully eradicated and provides a checklist to build cleanly and validate runtime behavior with updated tests.
Use case example: You retarget an ASP.NET application to .NET 8 and hit SYSLIB0006 for Thread.Abort; this skill helps you replace Response.End/Response.Redirect(url, true) and thread-abort exception handlers with cooperative cancellation using RequestAborted and proper cleanup.
Quick Start
Use the thread-abort-migration skill to migrate your .NET Framework project that uses Thread.Abort to a modern target like net8.0 by replacing each usage pattern with CancellationToken-based logic and then verifying the project builds with no remaining SYSLIB0006 warnings.