Modern .NET and Azure migration
Aviation Operations Software
Move older .NET workloads toward modern hosting, deployment, and cloud-supported architecture.
What this bullet means
The team also needs engineers who can understand an existing Windows or IIS application and plan a practical modernization path.
Sample app idea
Legacy Application Modernization Planner for dependencies, migration risks, target Azure services, rollout steps, and verification results.
Main build outline
- Record the current hosting, dependencies, database, and authentication approach for a fictional older application.
- Add target architecture choices for modern .NET, Azure App Service, containers, or managed services.
- Track risks and create phased rollout and rollback checklists.
Portfolio proof
- Before-and-after architecture diagram using a fictional older .NET application.
- Migration plan with dependencies, risks, rollout steps, and rollback notes.
Minimal documentation
- README with the business problem, screenshots, setup notes, and technology stack.
- One requirements note that maps the job bullet to the sample feature.
- One test plan note with happy path, validation, and edge case checks.
- One honest portfolio note that says this is self-directed practice, not employer work.
Modern .NET stack
- Blazor Server or ASP.NET Core Razor Pages.
- C# services with validation and dependency injection.
- SQL Server locally, then SmarterASP SQL Server or Azure SQL.
- Optional Azure App Service, GitHub Actions, Docker, and AI helper feature.