C#
Silverlight
Access
VB.NET
PowerBuilder
Winforms
ASP.NET Web Forms
Java
Delphi
XML
J2EE
Sharepoint
Windows XP
Informix 4GL
Unisys Linc
Application Assessment
Migration Blueprint
Migration Guide
Post Migration Services
Migration Methodology
Translation with SnowConvert
Edit, Debug & Deploy
Automated Test Case Generation
Metadata Analysis
Source Code Management
Migration and Other Snowflake Services
Get Up and Running with Snowpark
Using the SnowConvert Trial
Build a Cross-Platform Object Inventory
C#
Silverlight
Access
VB.NET
PowerBuilder
Winforms
ASP.NET Web Forms
Java
Delphi
XML
J2EE
Sharepoint
Windows XP
Informix 4GL
Unisys Linc
Application Assessment
Migration Blueprint
Migration Guide
Post Migration Services
Migration Methodology
Translation with SnowConvert
Edit, Debug & Deploy
Automated Test Case Generation
Metadata Analysis
Source Code Management
Migration and Other Snowflake Services
Get Up and Running with Snowpark
Using the SnowConvert Trial
Build a Cross-Platform Object Inventory
How do you upgrade your Visual Basic 6.0 web applications to .NET? Although there are different solutions, you should take into consideration that manual effort will probably be required. For instance, to upgrade VB6 ActiveX documents to .NET, it is necessary to rewrite them to Web user controls in order to recreate similar functionality. VB6 Web classes, on the other hand, can be at least partially upgraded to .NET automatically with the help of the Visual Basic Upgrade Wizard and the WebClass compatibility runtime. Please review the techniques presented in this chapter to address issues with upgrading these types of Web-based applications to Visual Basic .NET.
No, Visual Basic 6.0 ActiveX documents are not supported in Visual Basic .NET. You can still interoperate with ActiveX documents from your Visual Basic .NET Web applications, but development should be maintained in Visual Basic 6.0.
In Visual Basic 6.0, WebClass projects (also known as IIS application projects) are used to create Web applications based on ASP technology. In Visual Basic .NET, ASP.NET Web application projects are used to create Web applications based on the newer ASP.NET technology. When a Visual Basic 6.0 WebClass project is upgraded to Visual Basic .NET, it is converted to an ASP.NET Web application project.
In Visual Basic .NET, ASP.NET Web applications do not have a StateManagement property. Any code related to state management will need to be replaced; there are many options for this. Some options involve keeping information on the client (for example, directly in the page or in a cookie), and others involve storing information on the server between round trips.
Visual Basic 6.0 WebClass events that are not supported in ASP.NET include Initialize, BeginRequest, EndRequest, and Terminate. These event procedures will be upgraded by the upgrade wizard, but they will not be called at run time. After upgrading, you will need to move any code in these events to equivalent ASP.NET events, such as Init or Unload.
9130 Jollyville Rd, Suite 175
Austin, TX 78759
Call us: +(425) 609-8458
info@mobilize.net