Clearly classic ASP is not dying the quite death that was predicted.
显然经典的ASP并不是所认为的那样死了。
It possible that you haven't got Classic ASP support installed in IIS.
这可能是你没有安装IIS中的经典ASP支持。
For various reasons concerning a 3rd party tool it has to be classic ASP.
由于关于第三方工具的各种原因，它必须是经典的ASP。
Classic ASP Intellisense and debugging, cut in VS 2008, have been restored.
VS 2008所消减的经典ASP的智能提示和调试，已经得到恢复。
With Classic ASP it is impossible to separate executable code from the HTML itself.
使用经典ASP是很难达到将执行代码于HTML本身相分离的。
Instead of controls, developers will find themselves using a lot of inline scripting that looks like Classic ASP.
和在页面中使用控件的传统开发方式不同的是，开发人员会发现他们需要使用大量的内联代码，就好像传统的ASP应用一样。
This isn't the first time Visual Basic was used as a templating language, VBScript was the default language for classic ASP.
VisualBasic并非首次用在模板语言中，VBScript是传统ASP开发的默认语言。
For a lot of popular languages it's done already (I suppose) but I haven't found one for classic ASP... so here it comes.
对于许多流行的语言，它的已经做了(我假设)，但是我没有发现一个关于ASP类的。
Because this is classic ASP I think the only straightforward way to do this is to expose this class library as a COM object.
因为这是经典的ASP我认为这么做的唯一直接的方法是将此类库公开为COM对象。
The code above illustrates a limitation in Classic ASP: the code block has to be placed where you want the output to appear.
上面的代码说明了在经典ASP中的一个局限性：代码块必须放置在需要显示的地方。
If your goal is storing a hash of a password in a database, you could use SHA256. See my answer here SHA256 with classic ASP.
如果你的目标是存储的哈希数据库中的密码，你可以使用SHA256。看到我的答案在这里与经典的ASP实现。
To force detailed error reporting by Classic ASP, open the ASP 'feature' page for the website then expand the Debugging Properties node.
要强制详细的错误报告通过经典ASP，打开ASP“功能页面的网站，然后展开调试属性节点。”
I gave up and ended up installing classic ASP, as I couldn't get the mapping to work (received a combination of 404.17 and 404.3 errors).
我放弃了并安装经典的ASP，因为我无法使映射工作(收到404.17和404.3错误的组合)。
With Classic ASP it is impossible to separate executable code from the HTML itself. This makes the page difficult to read, and difficult to maintain.
使用经典ASP是很难达到将执行代码于HTML本身相分离的。这会使得页面难以阅读，并且在操作上也会带来困难。
I'd like to store the contents of classic ASP pages in a table in a database, and have the ability to dynamically retrieve said contents and execute on the fly.
我想经典的ASP页面的内容存储在一个数据库表中，并有动态检索的能力表示内容和执行的飞行。
In both classic ASP and ASP.NET, developers were used to using <%= expression %> to mix static and dynamic content. Unfortunately it is prone to HTML-injection errors.
在ASP和ASP.NET中，开发人员可以使用<%=expression%>来混合静态与动态内容，但这样也很容易造成HTML注入错误。
For example, when a request for a classic asp Web page arrives, IIS hands off the request to the asp.dll ISAPI extension, whose task it is to return the HTML markup for the requested asp page.
例如，在请求传统的asp网页时，IIS将请求传递给asp . dllISAPI扩展，该扩展的任务是返回被请求的asp页面的HTML标记。
Its an extra step for ASP Classic people to jump through but not the end of the world.
其asp经典的人一个额外的步骤，以通过跳跃，但不是世界的尽头。
I don't think you're going to be able to use generics with ASP Classic, I think you're going to need to convert it to an array.
我不认为你将能够使用泛型与asp经典，我想你会需要将其转换为一个数组。
I don't think you're going to be able to use generics with ASP Classic, I think you're going to need to convert it to an array.
我不认为你将能够使用泛型与asp经典，我想你会需要将其转换为一个数组。
应用推荐