IIS的未来版本中的ASP支持 [英] ASP support in future versions of IIS

问题描述

我在IIS中搜索了有关ASP主题和未来支持模式的任何帖子

。我看到很多基于当前使用等的猜测，

但是我们不要忘记Visual Basic 6.0是一个死产品 - 无论

多少人们还在使用它。让我们也不要忘记微软

改变了C ++（实际上是C）的一些核心语法，这些语法已经存在了30多年b
。

无论如何，任何人都可以向我指出任何正式的Microsoft文档

概述ASP的生命周期或IIS的良好路线图？我试过了
http://support.microsoft.com/lifecycle/search / ，但它不存在，因为ASP

在技术上不是产品。


谢谢。

I did a search for any posts on the topic of ASP and the future support model
for it within IIS. I see a lot of speculation based on current use, etc.,
but let''s not forget that Visual Basic 6.0 is a dead product - regardless of
how many people are still using it. Let us also not forget that Microsoft
changed some core syntax of C++ (actually C) that had been in place for 30+
years.

Anyway, can anyone point me to any official Microsoft documentation that
outlines the lifecycle for ASP or a good roadmap for IIS? I tried
http://support.microsoft.com/lifecycle/search/, but it is not there since ASP
is not technically a product.

Thanks.

推荐答案

>但是，我们不要忘记Visual Basic 6.0是一个死产品 - 无论

> but let''s not forget that Visual Basic 6.0 is a dead product - regardless

有多少人还在使用它。


但这都是关于是否使用它;还有什么其他定义

那里？如果我的系统上安装了Visual Basic 6.0，如果我需要启动一个简单的应用程序或

dll，我是否关心我的环境以外的任何东西？b $ b？微软的支持生命周期肯定不会阻止我这样做。

无论如何，任何人都可以指向任何正式的Microsoft文档
概述ASP的生命周期或IIS的良好路线图？我试过了
http://support.microsoft.com/lifecycle/search / ，但它不存在，因为
ASP
在技术上不是产品。

of
how many people are still using it.
But this is all about whether to use it or not; what other definition is
there? If I have Visual Basic 6.0 installed on my system, do I care about
anything external to my environment if I need to whip up a simple app or
dll? Microsoft''s support lifecycle certainly isn''t going to prevent me from
doing it.
Anyway, can anyone point me to any official Microsoft documentation that
outlines the lifecycle for ASP or a good roadmap for IIS? I tried
http://support.microsoft.com/lifecycle/search/, but it is not there since
ASP
is not technically a product.

我不认为你我会特别找到ASP的时间表。 ASP是IIS的一部分，而IIS是操作系统的一个组件，因此特定操作系统（例如Windows XP）的生命周期决定了
随附的ASP版本的生命周期（例如IIS 5.1 / ASP

3.0）。

I don''t think you''re going to find a timeline for ASP specifically. ASP is
part of IIS, and IIS is a component of the operating system, so the
lifecycle of a specific operating system (e.g. Windows XP) dictates the
lifecycle of the version of ASP that shipped with it (e.g. IIS 5.1 / ASP
3.0).

我同意，但我的观点是，微软在创新时并不一定要考虑用户群的大小。看看16位到32位，

Visual Basic 6，删除了While，Wend（授予，他们从未真正拿过

那一个），太阳套装结束了对Java标准的修改，对C ++语法的修改，对JSR 168的不符合等等。


当然，这不是必要的是他们是否会取消对ASP的支持 - 毕竟，这是一个静态代码库，他们只需要b $ b需要留在那里。我的观点是，我对微软对向后兼容性的承诺没有多少信心，特别是当他们没有像他们希望获得的那样成功的时候。支持.NET。


您对产品的支持生命周期绝对正确

产品 - 而非产品功能。我只是希望能从他们那里找到一些关于他们是否会支持或抛弃

ASP的官方承诺。我的公司在我们的网站上有几英里长的东西。


由于我至少有两到三年的时间，这不一定是个大问题
$剩下b $ b保证的主流支持。


Aaron Bertrand [SQL Server MVP]"写道：

I agree, but my point is that Microsoft doesn''t necessarily take the size of
the user base into account when they "innovate." Look at 16 bit to 32 bit,
Visual Basic 6, the removal of While ,Wend (granted, they never actually took
that one out), the Sun suit over modifications to the Java standard, the
modifications to C++ syntax, non-compliance with JSR 168, etc, etc.

Granted, this doesn''t necessary have anything to do with whether they will
remove support for ASP - it is, after all, a static code base that they just
need to leave in there. My point is that I do not have much confidence in
Microsoft''s commitment to backward compatibility, particularly when they have
not been as successfull as they had hoped in garnering support for .NET.

You are absolutely right about the support lifecycle pertaining specifically
to products - not features of products. I am just hoping to find some
official commitment from them about whether they will either sustain or dump
ASP. My company has miles and miles of the stuff all over our web site.

This isn''t necessarily a huge issue since I have at least two to three years
of guaranteed, mainstream support left.


"Aaron Bertrand [SQL Server MVP]" wrote:

但是不要忘记Visual Basic 6.0是一个死产品 - 无论

多少人们仍在使用它。

but let''s not forget that Visual Basic 6.0 is a dead product - regardless
of
how many people are still using it.

但这都是关于是否使用它;那还有什么定义呢？如果我的系统上安装了Visual Basic 6.0，如果我需要启动一个简单的应用程序或
dll，我是否关心环境外的任何内容？微软的支持生命周期肯定不会阻止我这样做。

But this is all about whether to use it or not; what other definition is
there? If I have Visual Basic 6.0 installed on my system, do I care about
anything external to my environment if I need to whip up a simple app or
dll? Microsoft''s support lifecycle certainly isn''t going to prevent me from
doing it.

无论如何，任何人都可以指向任何正式的Microsoft文档
概述ASP的生命周期或IIS的良好路线图？我试过了
http://support.microsoft.com/lifecycle/search / ，但它不存在，因为ASP
在技术上不是产品。

Anyway, can anyone point me to any official Microsoft documentation that
outlines the lifecycle for ASP or a good roadmap for IIS? I tried
http://support.microsoft.com/lifecycle/search/, but it is not there since
ASP
is not technically a product.

我不认为你会去专门为ASP找时间表。 ASP是IIS的一部分，IIS是操作系统的一个组件，因此特定操作系统（例如Windows XP）的生命周期决定了ASP版本的生命周期。与它一起发货（例如IIS 5.1 / ASP
3.0）。

I don''t think you''re going to find a timeline for ASP specifically. ASP is
part of IIS, and IIS is a component of the operating system, so the
lifecycle of a specific operating system (e.g. Windows XP) dictates the
lifecycle of the version of ASP that shipped with it (e.g. IIS 5.1 / ASP
3.0).

顺便说一句，你们所使用的产品是什么ASP开发？你是否仍然使用Interdev或者你换了别的东西吗？


谢谢

By the way, what products are you all using for ASP development? Are you
still using Interdev or have you switched to something else?

Thanks

这篇关于IIS的未来版本中的ASP支持的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！