Leading Low Cost ASP.NET Web Forms Developers Sydney, Melbourne, Brisbane, Perth, Adelaide
It is supported where it is. It just cannot follow .NET forward.
For businesses with an internal system or website built on ASP.NET Web Forms. We keep it supported on .NET Framework, tidy it so it can be changed safely, and migrate it to current .NET a section at a time where that is worth doing.
More about this service
We are an Australian team working with businesses in the United States, the United Kingdom, New Zealand and Australia. Every engagement starts with a scoped technical assessment, so the estimate that follows is based on your code and your data.
- Assessment A scoped technical review before any estimate
- 18+ yrs Building business software
- Independent No licence commission, no reseller agenda
- US UK NZ AU Australian team, no account managers
Built here. Your data stays here.
- No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
- Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
- Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.
It still works, but it cannot follow Microsoft forward
A great many internal business applications were built with Web Forms between roughly 2003 and 2015, and they work. Microsoft continues to support .NET Framework, so nothing has broken. But Web Forms was deliberately left out of .NET Core and everything after it.
Read more
The practical result is that the application cannot follow the platform. New libraries are written for current .NET, new developers have never used Web Forms, and each year the gap is a little wider. None of that makes it urgent. It makes it something to plan.
Our ASP.NET Web Forms developer service is for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide. It covers three kinds of work: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
Three ways forward for a Web Forms application
There is no deadline forcing the third.
-
Keep it and support it
The application stays on .NET Framework, on a supported version of Windows Server. We maintain it, fix security faults and document it. For many internal systems this is the right answer for years.
-
Prepare it
Business rules are moved out of the pages into separate code that current .NET can also run, and automated tests are added. The application works as before, and a later migration becomes much smaller.
-
Migrate it a section at a time
Pages are rebuilt in current .NET and take over behind the same addresses, with old and new running together against the same database.
What we do with Web Forms applications
Six kinds of work. Most engagements are two or three of them.
-
Web Forms maintenance
Changes and fixes in existing pages and the code behind them.
-
.NET Framework upgrades
Applications on old .NET Framework versions moved to 4.8, on a supported Windows Server.
-
Security review
Sign in, session handling, unsafe queries and outdated libraries checked and fixed.
-
Separating the rules
Business rules moved out of page code into libraries that can be tested and reused.
-
Staged migration
Sections rebuilt in current .NET, as server rendered pages or Blazor, behind the same addresses.
-
Third-party controls
Grids, charts and report viewers from control vendors assessed, and replaced where no current version exists.
Staying, preparing and migrating are different projects
Each trades cost against how long the application has to last.
-
Stay on Web Forms
Lowest cost, and supported. Right for an internal system with a known lifespan. It gets no new features from Microsoft, and people who want to work on it get harder to find.
-
Prepare, then decide
A modest spend that pays off either way: the application is easier to maintain now, and cheaper to migrate later.
-
Migrate to current .NET
The interface is rebuilt, because Web Forms pages do not convert. The business rules and the database usually carry across. Right for an application the business will depend on for another ten years.
What a Web Forms assessment looks at
The support facts are from Microsoft. The rest is about how the application was written.
-
Support status
Microsoft does not offer Web Forms in ASP.NET Core or later. It supports .NET Framework 4.8.1 for as long as it is installed on a supported version of Windows. So the question is which .NET Framework and which Windows Server you are on.
-
Where the business rules are
In the code behind each page, or in separate classes. Rules buried in page code have to be dug out before anything can be reused.
-
View state and server controls
The Web Forms way of remembering what is on the page. It has no equivalent in current .NET, which is why pages are rebuilt and not converted.
-
Third-party controls
Grid, chart and editor controls bought from vendors. Each needs a current replacement, and they are often the largest part of the interface work.
-
Sign in and security
The older membership system, Windows sign in, or something hand built, and how it maps to current practice.
-
Data access
Typed datasets, early Entity Framework, or SQL in the pages. This decides how easily the data layer carries forward.
-
Reports and exports
Report viewers and document exports built into pages. They are easy to forget and slow to rebuild.
-
Size
The number of pages, and how many are used. Usage logs usually show a long tail nobody opens.
A Web Forms system that works, with nobody keen to touch it?
What the assessment needs from you
A fixed-scope piece of work with a written result: the options, the risks of each, and a staged estimate. No production data is sent by email. We agree a secure way to share it first.
-
Versions
The .NET Framework version and the Windows Server it runs on.
-
Size
A rough count of pages, and whether the code is in source control.
-
The database
Product, version and size.
-
Controls
Any third-party control suites the application uses.
-
Users
How many people use it, and whether it faces the internet.
-
Lifespan
How long the business expects to depend on it.
-
What is hurting
The two or three problems that started the conversation.
-
The way back
How long the business can run on the old system if a cutover has to be reversed.
From assessment to a supported application
By video call and screen share, at meeting times agreed to suit you.
-
Technical assessment
We read the code, check the versions and the controls, and measure how much of the application is used. You get written options with the risks of each and a staged estimate.
-
Make it safe to change
Source control, a working build and a first set of automated tests, so later changes can be proven.
-
Proof of concept
One section is rebuilt in current .NET and run behind the same addresses, against the same database.
-
Staged work
The work is done in stages agreed from the assessment, each with its own scope and estimate, starting with whatever is hurting the business most.
-
Comparison and user testing
Old and new are compared on the same data, and your staff test the work they do every day.
-
Cutover and support
Each switch is planned with a way back. We watch the first days of live use, then maintain the system for as long as it stays in service.
What people ask us about Web Forms
Is ASP.NET Web Forms still supported?
Yes, on .NET Framework. Microsoft supports .NET Framework 4.8.1 for as long as it is installed on a supported version of Windows. Web Forms was not carried into ASP.NET Core or later, so it keeps running and does not move forward.
What should we migrate to?
It depends on your team. Current .NET with server rendered pages is the smallest step. Blazor suits teams that want to stay in C#. A JavaScript front end with an API suits teams that already work that way.
Can Web Forms pages be converted automatically?
No. View state and server controls have no equivalent in current .NET, so the interface is rebuilt. The business rules underneath usually carry across well, especially once they have been separated from the pages.
Can we do it gradually?
Yes, and you should. Section by section behind the same addresses, with both running side by side, avoids a single risky switch on a system the business depends on.
Does the database have to change?
Usually not at all. Keeping SQL Server as it is makes checking much simpler, and keeps the project on the layer that has to move.
Do we have to migrate at all?
Not on any deadline. If the application has a few years left and nobody needs it to do anything new, supporting it where it is can be the right answer, and we will say so.
Do you provide ASP.NET Web Forms developers in Sydney, Melbourne, Brisbane, Perth and Adelaide?
Yes. We are an Australian team and we take on ASP.NET Web Forms work for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide, and elsewhere in Australia. The work runs by video call and screen share, with secure access to a copy of your system. The service is the same in every city: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
How does this work from the United States, the United Kingdom or New Zealand?
By video call and screen share, at meeting times agreed to suit you, from discovery to handover. Confidentiality, who can reach your systems and where your data is held are agreed in writing before work starts.
What does it cost?
The assessment is a fixed-scope piece of work with an agreed fee. The estimate for anything after it comes from what the assessment finds, in stages, so you are not asked to commit to a whole project on a guess.
Sending your details…
You can stay on this page while we send it.
Tell us about your Web Forms application
What the application does, the .NET Framework version, roughly how many pages it has, and what is forcing the question. Include your country so we can suggest meeting times. Please do not send production data.
Prefer a quick chat? Call 0425 531 127. We answer it ourselves, in Australia.
Kasun Wijayamanna, founderYou deal with Kasun from scope to delivery. No account managers and no offshore handoff.