classic asp will also be abandoned?

@啸 轩

Active Server Pages (ASP) enables web servers to dynamically generate webpages and create interactive web applications by using server-side scripting technology. The use of ASP pages with Microsoft Internet Information Services (IIS) is currently supported in all supported versions of IIS.

IIS is included in Windows operating systems. Therefore, both ASP and IIS support lifetimes are tied to the support lifecycle of the host operating system.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

I think the answer is clearly "yes, it will", but more interesting the next question is when? For that we might turn to the history for hints.

First, let's review the "VBScript deprecation plan" (as detailed in https://techcommunity.microsoft.com/t5/windows-it-pro-blog/vbscript-deprecation-timelines-and-next-steps/ba-p/4148301),

• Phase 1: Windows 11 version 24H2 will make VBScript available as features on demand (FODs) and VBScript will be enabled by default. Literally that's business as usual.
• Phase 2: Around 2027, VBScript FODs will be disabled by default but you can still manually enable it.
• Phase 3: Only in a distant future beyond 2027 (TBD) VBScript will be completely removed.

Then, what about classic ASP? It has been available as FODs since IIS 7 (Windows Vista in 2007) and disabled by default,

https://learn.microsoft.com/en-us/iis/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8/classic-asp-not-installed-by-default-on-iis

So, we can say classic ASP entered its phase 2 of its deprecation (though there was never an announcement similar to the VBScript one) as early as 2007. However, up-to-now (after more than 17 years) it remained part of Windows.

I believe it will take Microsoft many more years to ultimately remove classic ASP and VBScript from Windows, but you should migrate to modern technologies as early as you can.

along with vbscript deprecation (though oddly the jscript which I used for Active Server Pages hasn't been), there is the issue that it is 32 bit. As 32 bit support wanes, the com objects used by asp may also become unsupported. Some legacy com objects are so insecure, MS recommends not using them with server code.

as there is no modern vb/vbscript replacement, you might look at migrating the asp code to jscript. this can be done a file at a time or even parts of a file. once migrated to jscript, you could then port to a node solution. there a many asp like templates engines. see ejs:

https://ejs.co

currently the best Microsoft porting solution is to C# and razor pages, basically a complete rewrite. using the yarp proxy, you can do a migration like:

https://learn.microsoft.com/en-us/aspnet/core/migration/inc/start?view=aspnetcore-9.0