问题描述

我正在将 ASP 经典页面转换为 ASP.NET.将扩展名为 .inc 的文件包含到 aspx 页面的正确方法是什么?

I'm converting ASP classic page to ASP.NET. What's the proper way of including files with .inc extension to aspx pages?

<!--#include virtual = "adovbs.inc" -->

我注意到，每次我将包含指向 .inc 文件的包含指令的页面之一更改为 aspx 时，我都会从这些 .inc 文件中得到各种错误.

I've notice that each time that I change one of those pages containing the include directive pointing to .inc files to aspx, I'm getting all sort of errors from those .inc files.

我觉得只是将那些 .inc 文件中的逻辑重写为 vb 类.

I feel like just rewriting the logic inside those .inc files into vb classes.

推荐答案

adovbs.inc 或 adovbs.asp 的目的是提供命名常量值的列表来自 ADODB DLL (由于 Classic ASP 的大部分功能依赖于 VBScript 中的后期绑定).

The purpose of adovbs.inc or adovbs.asp was to provide a list of named constant values from the ADODB DLL (due to Classic ASP relying on late binding in VBScript for most of it's functionality).

adovbs.asp

'--------------------------------------------------------------------
' Microsoft ADO
'
' (c) 1996-1998 Microsoft Corporation.  All Rights Reserved.
'
'
'
' ADO constants include file for VBScript
'
'--------------------------------------------------------------------

'---- CursorTypeEnum Values ----
Const adOpenForwardOnly = 0
Const adOpenKeyset = 1
Const adOpenDynamic = 2
Const adOpenStatic = 3

'---- CursorOptionEnum Values ----
Const adHoldRecords = &H00000100
Const adMovePrevious = &H00000200
Const adAddNew = &H01000400
Const adDelete = &H01000800

直到人们意识到您可以使用 METADATA 数据标签来导入DLL 常量直接来自类型库，而不需要 adovbs 包含文件.

This was until people realised you could use the METADATA data tag to import DLL constants direct from the Type Library instead of needing the adovbs include file.

<!-- METADATA 
        TYPE="typelib" 
        UUID="00000200-0000-0010-8000-00AA006D2EA4"
-->

在 ASP.Net 中，所有内容都已编译，因此不需要这些常量文件，因为它们已经以某种形式存在于 ADO.Net 中.

In ASP.Net everything is compiled so there is no need for these constant files as they will already exist in some form in ADO.Net.

这篇关于如何在 aspx 页面中包含 adovbs.inc 文件?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！