Chapter 4. Post-migration Changes

Snoops

---

  

	Migrating to .NET: A Pragmatic Path to Visual Basic .NET, Visual C++ .NET, and ASP.NET By Dhananjay  Katre, Prashant  Halari, Narayana  Rao  Surapaneni, Manu  Gupta, Meghana  Deshpande
	Table of Contents

---

As seen in the previous chapter, Microsoft has provided an upgrade wizard with Visual Studio .NET. When a Visual Basic 6.0 project is opened in Visual Studio .NET, it automatically invokes the upgrade wizard. This wizard performs most of the syntax changes and converts Visual Basic Forms into equivalent Windows Forms. However, the difference in the syntax and structural architecture between Visual Basic 6.0 and Visual Basic .NET are so vast that the upgrade tool cannot automatically make all the required changes. There are many code changes that have to be made manually in the upgraded code. For this reason, the upgrade tool produces an upgrade report that lists all the errors and warnings encountered during the upgrade process. This report also mentions why certain code was not upgraded and provides links to MSDN documentation, which describe how the required functionality can be coded in Visual Basic .NET.

This chapter maps commonly used functionality found in Visual Basic 6.0 and shows how that functionality can be achieved in Visual Basic .NET. The chapter emphasizes the code examples, which show one of the ways in which the same functionality of a Visual Basic 6.0 application can be achieved in a Visual Basic .NET application.

---

Snoops

Top