Replace my custom Utility.SetRegistryValue() with Registry.SetValue()


I was researching Work Item 11729 (UnauthorizedAccessException) and stumbled across a reference to the Registry.SetValue() method.  I compared it to what I've built in the Utility class, and it looks like (other than a bit of trace logging I've added for debugging 11729) there's no functional difference.  Why did I build this myself?  I have no idea.
I'll clear out that re-implemented function ASAP.
Closed Nov 29, 2008 at 11:26 PM by MikeSL


wrote Nov 29, 2008 at 8:50 PM

Note: MSDN states that Registry.G/SetValue() will not perform as well as the RegistryKey class, since Registry.?etValue() will open & close the Key immediately, rather than leave a handle open for multiple reads/writes.  I must've started out with a series of Registry reads/writes, and then refactored them down to atomic transactions.

wrote Nov 29, 2008 at 11:26 PM

Resolved with changeset 24538.

wrote Feb 12, 2013 at 9:59 PM

wrote May 15, 2013 at 2:32 AM