Note: This API is now obsolete.
Enables upgraded Visual Basic 6.0 WebClass projects to run in ASP.NET.
Assembly: Microsoft.VisualBasic.Compatibility (in Microsoft.VisualBasic.Compatibility.dll)
Thetype exposes the following members.
|Equals(Object)||Determines whether the specified object is equal to the current object. (Inherited from Object.)|
|Finalize||Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.)|
|GetHashCode||Serves as the default hash function. (Inherited from Object.)|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|MemberwiseClone||Creates a shallow copy of the current Object. (Inherited from Object.)|
|ProcessEvents||Renders a WebItem in a .|
|ToString||Returns a string that represents the current object. (Inherited from Object.)|
|URLFor(String, String)||Specifies the URL that the system must have to reference a WebItem in the browser.|
|URLFor(WebItem, String)||Specifies the URL that the system must have to reference a WebItem in 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 WebItem and Template in the WebClass project. A Page_Load event procedure is added to the project. This creates first a WebClass object and then WebItem objects for each WebItem and Template 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 WebItem specified in the Request URL. This code is the only new code added to your upgraded project and serves only 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.