Why should I consider replacing API Calls with .NET Framework Intrinsic Functions?
Because of some limitations in Visual Basic 6.0, many programmers have been forced to use the different functions that are available in the Windows API. For operations such as registry manipulation, finding window names, or finding the names of special folders, Visual Basic 6.0 developers were forced to use the Windows API because there was no other way to carry out these tasks. In Microsoft Visual Basic .NET, all the barriers that held back Visual Basic 6.0 developers and forced them to resort to the Windows API are completely gone. For every function that accomplished a specific task in the Windows API, there is a way to achieve the same result in .NET using intrinsic functions. You can still use Windows API calls by means of using interop services, but your .NET applications are usually be better off using the functions included in the .NET Framework. The amount of work required to get your .NET application working with the same API calls from Visual Basic 6.0 may be more than what
