I hope you'll both look at this and tell me if you think I should still post
this where you suggested, Kevin.
My explaination of the situation is confusing because I know just enough to
be dangerous. People are explaining it to me and I don't know that they're
using the right words. Now I know more information.
As you suggested it is not the strong keys that are needed; they're compiled
into the code. Apparently we're using three components, and the securitiy
policy (machine level usually) needs to be set with the "public key." Or is
this more correctly called the GUID? Anyway, from the MS Security Policy
config tool one can either point to the dlls or with the poliicy setting tool
put in the "keys" (which we supply them). Having to do this manual process
on each machine is not nice!
We'd like to be able to automate this process to it can be pushed out to
clients (SMS?) or otherwise made as easy as possible for administrators.
We did create an MSI script from one machine and ran it on another, and this
did the job! The bad news is it blows away other secccurity policeis on the
target machine! Not good! Is there a way to have the MSI do just "our"
changes?
Hope this makes more sense than what I previously wrote. Thaks for your
help, guys.
"Kevin Yu [MSFT]" wrote:
Hi,
Yes, I agree with Richard, that the strong named assemblies contains their
own information on key(public key token). If the deployment requires
ditribute the key from the vendor, it's not the strong name key. In this
case, I suggest you try to post in the microsoft.public.sms.admin newsgroup
for more information on how to distribute the keys.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."