Registry API Wrapper

 Download Source Code and Example

I personally find the Win32 Registry API to be overly complex for performing simple operations. The Win32 Registry API is very "rich". You can do a lot with it, but most of the time you just want to read or write a value. The error checking involved in doing even simple registry operations is enough to hide the meaning of the code. Most of the time you either want the operation to succeed or fail as a whole, you're not interested in handling errors at each stage and performing recovery operations...

I've seen many Win32 Registry API wrapper classes but all of them failed to actually make it easier to use the registry than the API. Most have been simple wrappers which add no value (apart from saving you the bother or having to pass the HKEY to each function...).

CRegistryKey is essentially just a very simple wrapper around a HKEY. It adds value by converting errors to exceptions, defaulting most of the rarely used parameters with sensible values and providing STL style iterators for sub keys and values. All of the Win32 Registry API  is present as member functions, but if you want to check for errors without using exceptions there's a conversion operator that will allow access to the underlying HKEY.

CRegistryKey was designed to make code like this as easy as possible...

try
{
   CRegistryKey key = CRegistryKey(HKEY_LOCAL_MACHINE, _T("SOFTWARE"));
  
   // for each sub key of this key...
  
   for (CRegistryKey::SubkeyIterator it = key.BeginSubkeyIteraton();
        it != key.EndSubkeyIteraton();
        ++it)
   {
      // Dump out the key's name

      tcout << it.GetName() << endl;

      // Then display each value
  
      CRegistryKey subKey = it.OpenKey();
  
      for (CRegistryKey::ValueIterator val = subKey.BeginValueIteration();
           val != subKey.EndValueIteration();  
           ++val)
      {
         tcout << " " << val.name() << T(" ") << val.valueAsString() << endl;
      }
   }
}
catch (CRegistryKey::Exception &e)
{
   e.MessageBox();
}

So that this article and code can be kept up to date more easily I've provided a link to where the article is located on my own web pages. Read the full article and download the source code.

Last updated: 3 July 1998




Comments

  • A little error.

    Posted by Legacy on 05/21/1999 12:00am

    Originally posted by: Laurent Kemp�

    Hi Len,

    I have found a little error in your code.

    In your CRegistryKey::Value constructor you allocate memory with
    _tcsdup that should be freed by free function because it's allocated
    with malloc (take alook into MSDN for "_strdup, _wcsdup, _mbsdup").

    CRegistryKey::Value::Value(const Value &rhs)
    : m_pName(_tcsdup(rhs.m_pName)),

    CRegistryKey::Value::~Value()
    {
    //ERROR
    // delete[] m_pName;
    free(m_pName);

    Best regards.

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Companies undertaking an IT project need to find the right balance between cost and functionality. It's important to start by determining whether to build a solution from scratch, buy an out-of-the-box solution, or a combination of both. In reality, most projects will require some system tailoring to meet business requirements. Decision-makers must understand how much software development is enough and craft a detailed implementation plan to ensure the project's success. This white paper examines the different …

  • Today's agile organizations pose operations teams with a tremendous challenge: to deploy new releases to production immediately after development and testing is completed. To ensure that applications are deployed successfully, an automatic and transparent process is required. We refer to this process as Zero Touch Deployment™. This white paper reviews two approaches to Zero Touch Deployment--a script-based solution and a release automation platform. The article discusses how each can solve the key …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date