What Is ASP? From Classic ASP to ASP.NET Core and Modern .NET

"ASP" is one of the most overloaded acronyms in Microsoft web development. It has described a scripting platform, a runtime family, a file extension, and — informally — every web application Microsoft has shipped since 1996. This guide answers the question directly, then walks the full path from classic ASP to ASP.NET Core and modern .NET so the names stop blurring together.

What does ASP stand for?

ASP means Active Server Pages. Microsoft introduced it in 1996 as a way to run server-side script inside an HTML page on Internet Information Services (IIS). A request for a file ending in .asp was executed on the server, and the resulting HTML was sent to the browser. The page logic was written in VBScript or JScript and mixed directly with markup.

Two clarifications save a lot of confusion. First, ASP is not a programming language, a framework, or a runtime — it was a templating and scripting model hosted by IIS. Second, "ASP" is occasionally used for unrelated phrases such as "Application Service Provider", a business term from the late 1990s with nothing to do with web development. In a web development context, ASP always refers to the Microsoft server-side technology.

<%
    Dim name, total
    name = Request.QueryString("name")
    total = 0
    For i = 1 To 5
        total = total + i
    Next
    Response.Write "Hello, " & name & " (total " & total & ")"
%>

That snippet is classic ASP: instructions between <% and %> run on the server, and the output is written into the response stream. It was simple, direct, and quickly became a very common way to build dynamic intranet and commerce sites.

Classic ASP: server-side scripting before .NET

Classic ASP shipped with IIS 3.0 and was refined through IIS versions on Windows NT, Windows 2000, and Windows Server. Its strengths were real: a short learning curve, first-class access to databases through ADO, and no compile step — you edited an .asp file and refreshed the browser.

Its limits were also real, and they shaped everything Microsoft built afterwards:

Interpreted script. Every request re-interpreted the page, with no compiled, strongly typed model.
Mixing everything. Markup, data access, business rules, and HTML rendering lived in one file by default.
No type safety. Errors that a compiler would catch surfaced at runtime, in production.
Difficult testing. Logic embedded in a page cannot be unit tested in isolation.

Classic ASP still runs on supported Windows Server and IIS installations, and plenty of legacy systems rely on it. But it receives no new features, and no sane team starts a new project with it in 2026.

ASP.NET: the .NET rewrite (2002)

ASP.NET arrived with .NET Framework 1.0 in 2002. It kept the .aspx page model but changed almost everything underneath: pages were compiled to .NET assemblies, code could be written in C# or VB.NET, and the framework was object oriented from top to bottom. The dominant application style was Web Forms, which tried to make web development feel like building a Windows desktop form — server controls, events, and the famous ViewState field that persisted control state between requests.

Web Forms was productive for rapid business applications, but the abstraction fought the stateless nature of HTTP. Rendering HTML you could not fully control, heavyweight page lifecycles, and awkward testability pushed the community toward a different idea that already worked well in other ecosystems: Model-View-Controller.

ASP.NET MVC and the return of separation

ASP.NET MVC shipped in 2009 as an alternative to Web Forms on the same .NET Framework. It brought the Model-View-Controller pattern, routing instead of file paths, clean HTML you control, and controllers that can be unit tested without a web server. Over several releases it matured into the recommended approach for new Microsoft web applications, and millions of developers learned MVC in exactly the form this guide describes in later parts.

Even so, ASP.NET MVC was tied to .NET Framework: Windows only, IIS first, and versioned with the framework rather than the web platform.

ASP.NET Core: one framework, many application styles (2016)

ASP.NET Core 1.0 was a ground-up rewrite, released in 2016. It is open source, cross-platform (Windows, Linux, and macOS), and much faster. It also unified things that had been separate products:

MVC for server-rendered applications with controllers and Razor views.
Web API for JSON services — previously a separate framework, now part of the same pipeline.
Razor Pages for page-focused scenarios.
Minimal APIs for small, focused HTTP endpoints, added in .NET 6.
Blazor for interactive UIs built with C#.

All of these styles share one dependency injection container, one configuration system, one middleware pipeline, and one hosting model. That is why modern ASP.NET Core applications can mix an MVC page with a JSON endpoint without leaving the same project — a theme the later parts of this guide build on.

Modern .NET: what ASP.NET Core runs on today

In 2020, Microsoft dropped "Core" from the product name. ASP.NET Core now runs on modern .NET, the cross-platform runtime line that continues .NET Core: .NET 5, 6, 7, 8, 9, and .NET 10 — the current Long Term Support release. New versions ship yearly, and each application targets a specific runtime version that can be deployed side by side with others.

The older Windows-only line still exists as .NET Framework 4.8, which is serviced but receives no new language or runtime features. If you want the full comparison, read the next part of this guide: What Is .NET Framework? .NET Framework vs Modern .NET Explained.

A short history in dates

1996 — Classic ASP ships with IIS 3.0.
2002 — ASP.NET 1.0 and Web Forms arrive with .NET Framework.
2009 — ASP.NET MVC brings the Model-View-Controller pattern to .NET.
2016 — ASP.NET Core 1.0 unifies web frameworks on a cross-platform runtime.
2020 — .NET 5 unifies the naming; "Core" disappears from the product name.
2025 — .NET 10 becomes the current Long Term Support release.

Which "ASP" are you actually dealing with?

When you inherit a project or read documentation, identify the generation first:

Files ending in .asp with VBScript → Classic ASP on IIS.
Files ending in .aspx with server controls and ViewState → ASP.NET Web Forms on .NET Framework.
Controllers, Razor views ending in .cshtml, and a web.config → ASP.NET MVC on .NET Framework.
A .csproj that targets net10.0, Kestrel, and Program.cs → ASP.NET Core on modern .NET.

Everything in the rest of this guide targets the last category. For the official overview, start with Microsoft Learn: ASP.NET Core overview and Microsoft Learn: .NET introduction.

Key Takeaways

ASP stands for Active Server Pages — Microsoft's server-side web technology introduced in 1996.
Classic ASP, ASP.NET Web Forms, ASP.NET MVC, ASP.NET Core, and modern .NET are generations of the same family, not synonyms.
ASP.NET Core is open source, cross-platform, and unifies MVC, Web API, Razor Pages, Minimal APIs, and Blazor.
New applications should target modern .NET (.NET 10 today), not .NET Framework or classic ASP.

FAQ

Is ASP still used today?

Classic ASP still runs legacy sites on IIS, but new development uses ASP.NET Core on modern .NET. When people say "ASP" today, they usually mean the modern stack without saying "Core".

What is the difference between ASP and ASP.NET?

ASP is the 1996 scripting model with interpreted code in .asp files. ASP.NET is the compiled .NET successor introduced in 2002, and ASP.NET Core is its modern, cross-platform rewrite.

Is classic ASP dead?

It is not removed from supported Windows Server versions, but it is frozen: no new features, no modern tooling, and no reason to start a new project with it.

Should beginners learn ASP.NET Framework or ASP.NET Core?

Learn ASP.NET Core on modern .NET. It is where the platform invests, it is cross-platform, and the concepts transfer if you later maintain an older .NET Framework application.