Senior .NET Razor Developer (Classic ASP to Razor Pages conversion)

VettedBench; United States; Remoto; USD 120.000 - 170.000; Tempo integral

Resumo da vaga

VettedBench is seeking an experienced .NET web developer to lead a migration of Classic ASP screens to ASP.NET Core 8 Razor Pages for a large banking web app. You’ll work hands-on from day one on complex forms and multi-tab editors, preserving behavior and data integrity.

You will review generated code against the legacy source, enforce the team’s conversion standard, and collaborate with QA to prove equivalence. Strong knowledge of ASP.NET Core and SQL Server is essential.

Qualificações

• Experience with 9–12 years in .NET web development.
• Hands-on migration from Classic ASP to ASP.NET Core Razor Pages.
• Strong SQL Server and ADO.NET background, with EF/EF Core knowledge.

Responsabilidades

• Convert screens from Classic ASP to ASP.NET Core Razor Pages like-for-like.
• Review generated or third-party code against the legacy source line by line.
• Follow team conversion standards and verify equivalence with QA.

Conhecimentos

ASP/VBScript legacy

ASP.NET Core Razor Pages

C# .NET 8

SQL Server

ADO.NET / stored procedures

Entity Framework / EF Core

JavaScript / jQuery / AJAX

Git & PR review

CI/CD (Azure DevOps)

Ferramentas

Kendo UI / Telerik UI

TypeScript

webpack

Playwright

Selenium

Azure DevOps

CI/CD pipelines

Descrição da vaga

Experience: 9–12 years in .NET web development, including hands-on work with Classic ASP or ASP.NET Web Forms/MVC on .NET Framework.

About the work: We are converting screens of a large banking web application from Classic ASP (VBScript) to ASP.NET Core 8 Razor Pages. The new pages run inside the team existing Razor application, alongside the legacy pages, on the same SQL Server database. Each screen is converted like for like: same behaviour, same data written, same user experience. Some screens are very large, for example an account and loan editor with thousands of form fields and eight tab panels.

An AI-assisted migration platform produces the first draft of each converted file. You review every file against the legacy source, fix what is wrong, and make sure it follows the team written conversion standard.

Required skills

Reading and understanding Classic ASP (VBScript): include files, Request() handling, ADO recordsets, On Error Resume Next, and VBScript type and rounding behaviour.

Reviewing generated or third-party code line by line against a legacy original, and finding what is missing, changed or invented.

Strong hands-on ASP.NET Core Razor Pages, including pages that keep their server code inline in the .cshtml file (no page model), partial views, layouts and sections.

Converting legacy screens like for like: preserving behaviour by default, and fixing a legacy defect only when it is proven, agreed and documented.

Handling large forms in ASP.NET Core: form value limits, fields that repeat or are missing, server-side validation, and POST-only saving with anti-forgery tokens.

C# on .NET 8, with SQL Server: parameterised SQL through ADO.NET, stored procedures, and transactions across multi-table saves. Entity Framework 6 or EF Core.

JavaScript and jQuery, AJAX, HTML5 and CSS3.

Git and pull-request-based code review.

Preferred skills

Kendo UI for jQuery or Telerik UI for ASP.NET Core, including upgrading from an older Kendo UI version.

TypeScript, SCSS and webpack.

An ASP.NET Core app hosted under a sub-path behind a reverse proxy, and authentication shared between a legacy app and a new one.

Moving state that the legacy app keeps in Session to the new pages.

Browser and integration testing (Playwright or Selenium, xUnit with WebApplicationFactory).

Daily use of AI coding tools (GitHub Copilot, Cursor, Claude Code or similar), with a critical eye for their output.

Banking or financial-services applications.

Azure DevOps, CI/CD and Agile delivery.

Role expectations

Work hands-on from day one: quickly understand an unfamiliar legacy screen, its include files, its database calls and the pages around it.

Review every generated file against the legacy source before it goes to QA, and record findings so the generator's output improves.

Follow the team conversion standard and existing conventions rather than introducing new patterns or architecture.

Prove equivalence with the QA engineer: same values on screen, same rows saved, same messages and redirects.

Deliver quality code within tight timelines on a short, fixed-scope engagement.