.NET Framework vs .NET 8 migration
You inherit a .NET Framework 4.8 IIS monolith. How do you plan migration to .NET 8 without a big-bang rewrite?
Answers use simple, clear English.
Quick interview answer
Run upgrade assistant and API compatibility analyzer. Strangler fig: expose new ASP.NET Core APIs behind reverse proxy; migrate module by module. Replace System.Web dependencies, binary formatter, and WCF server with REST/gRPC.
Detailed answer
Run upgrade assistant and API compatibility analyzer. Strangler fig: expose new ASP.NET Core APIs behind reverse proxy; migrate module by module. Replace System.Web dependencies, binary formatter, and WCF server with REST/gRPC. Containerize on Linux for cost. Keep shared DB with schema versioning; parallel run with feature flags and traffic shadowing before cutover. Interviewers want incremental risk reduction, not 'rewrite in React'.
Full explanation
Interviewers want incremental risk reduction, not 'rewrite in React'.
Real example & use case
Billing module moved to Core 8 API on Kestrel; legacy MVC pages call it via HTTP until UI migrates.
Pros & cons
Pros: phased delivery, rollback per module. Cons: dual runtime period, integration test matrix grows.