Why should I consider replacing Registry API with .NET Intrinsic Functions?
Built-in registry manipulation from within Visual Basic 6.0 has been somewhat limited to the following four functions: SaveSetting, GetSetting, GetAllSettings, and DeleteSettings. Although these functions allow registry editing, they are limited in the subtrees they can access: HKEY_CURRENT_USER\Software\VB and VBA. Because of this limitation, many programmers use the Windows API to perform registry modification tasks from within Visual Basic 6.0. Two new classes that offer the same registry manipulation functionality as the Windows Registry API have been added to the .NET Framework. These classes are the Registry class and the RegistryKey class; they are located in the Microsoft.Win32 namespace. The Registry class provides the set of standard base keys found in the registry. Using it, you can define the root key on which you will be working. After the base key is defined, you can use the RegistryKey methods to perform the necessary registry actions, like adding, deleting or changing s
