What they don't tell you (or I couldn't figure out) is that to set the default value, you add an unnamed value, not a value named "(Default)". As far as the permissions, I wasn't asking for Write permissions, and of course, the exception is misleading...
Sheesh. Anyway, many thanks, for the help. Chris Szurgot -----Original Message----- From: Marsh, Drew [mailto:[EMAIL PROTECTED]] Sent: Friday, May 24, 2002 12:24 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Adding assemblies to VS.NET "Add References" Dialog Chris M. Szurgot [mailto:[EMAIL PROTECTED]] wrote: > I got that far, but the problem is that any time I try to > manipulate the registry, it's throwing > "System.UnauthorizedAccessException: Cannot write to the > registry key." even though I'm an Administrator. (Note that > this is with Microsoft.Win32) and as I stated in the original > message, the Registry key created by the installer is a > duplicate of the (Default), not updating the default. As an Administrator, I can't imagine why you're getting an access exception. I do mine with the installer package, I just added the key "\MyAssembly" and set the default value of the key to "[TARGETDIR]" which expands to wherever the user has chosen to install my components. Everything works just as expected. Later, Drew You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
