Enables upgraded Visual Basic 6.0 WebClass projects to run in ASP.NET.
Assembly: Microsoft.VisualBasic.Compatibility (in Microsoft.VisualBasic.Compatibility.dll)
|WebItem(String, WebClass, String)|
Initializes a new instance of theclass.
Gets the name that is used in code to identify aobject.
Gets or sets a value that determines whether to rescan for tokens that are contained within replacement text.
Gets or sets the string that is used to prefix replacement tag names in an HTML template.
Determines whether the specified object is equal to the current object.(Inherited from Object.)
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)
Serves as the default hash function. (Inherited from Object.)
Returns a string that represents the current object.(Inherited from Object.)
Processes an HTML template attached to a WebItem object and returns it to the browser.
When a Visual Basic 6.0 WebClass project is upgraded to Visual Basic, it is converted to an ASP.NET Web site project.
Declarations are added to your project: one for the WebClass and one for each of the WebItems and Templates in the WebClass project. A Page_Load event procedure is added to the project, creating first a WebClass object and then WebItem objects for each of the WebItems and Templates associated with the Visual Basic 6.0 WebClass project. Finally, in the Page_Load event procedure, you will see a call to the WebClass Compatibility runtime: ProcessEvents. This enables the runtime to render the specified in the Request URL. This code is the only new code added to your upgraded project and only serves to emulate the underlying behavior of the Visual Basic 6.0 WebClass runtime.
Functions and objects in the Microsoft.VisualBasic.Compatibility.VB6 namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic 2008. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.
Available since 1.1
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.