Hello,
ma***********@gmail.com!
RegistryPermission won't help you, since they're regulate registry
permissions within your code, and not in the OS.
IMO the only way left is the unmanaged way (see link 2 from the previous
answer)
You wrote on Mon, 03 Sep 2007 04:43:58 -0700:
mOn 3 Sep, 12:33, "Vadym Stetsiak" <vadm...@gmail.comwrote:
>Hello, marcussilf...@gmail.com!
>To secure separate registy key, you need to setup Access Control List
(ACL)
on that key.
>Here's the example how to set ACL on the files
-http://west-wind.com/weblog/posts/4072.aspx.
The same is valid for registry keys.
>Here's also the example in MC++
-http://www.codeproject.com/dotnet/SecureRegistryKey.asp
mThanks for answering, however I have to use .Net 1.1 so the solution
mdescribed in the first link is not available to me unfourtunately.
mI have not looked so much on the 2nd link yet, but I guess I could
muse that unmanaged code for the task.
mI rather do it purely in c# though (if possible)
mIs there a way to enable a limited user to write to a certain
mregistrykey in c# in .Net 1.x or do I have to resort to unmanaged
mcode for this when developing .Net 1.x applications?
mRegistryPermission class exist in .Net 1.x could this class solve
mthis issue?
--
With best regards, Vadym Stetsiak.
Blog:
http://vadmyst.blogspot.com