Hi Bob,

The assemblies from OakLeaf are signed with a keypair.snk file when they were built by OakLeaf. They are not typically shipped with commercial products. Since you have the ability to rebuild those projects, they need to have a keypair file. If you create a new keypair, then the public key token value will change and need to be changed in the applications where you use those assemblies. You do not need to create a keypair for your own project if you don't wish.

On the other hand, if you create a keypair as you have for the MM assemblies, then later you rebuild them again, reuse the same keypair you already created last time and the public token will not change again. But if Oakleaf gives you a new build, the public token would change back to what it was the last time you got a buidl from them.

I am not sure what the risk is if Oak Leaf would ship the keypair for us so we can rebuild the assemblies without this changing since the source is shipped anyway. This is typically only an issue in ASP such as your project because the value is in the web.config file.

I hope that all makes sense.
Timothy

>Tim,
>
>I did create the new keyPair.snk file in the MM Telerik web controls project, But the token key that I manually changed was in the web.config file for the application. Are you saying that I needed to create a new keyPair.snk file in the web application project as well? If not, then at what point does the public token key get updated in the application config file?
>
>Bob
>>Bob,
>>
>>Did you create a new keyPair.snk when you rebuilt the mm project? This will change the public token key. If you use the same one every time then you won't have to worry about it in the web.config unless the version also changes.
>>Timothy
>>
>>>Tim,
>>>
>>>After an exhaustive search I changed the public key token in the web.config file to what I saw in the properties of the file in the GAC.
>>>
>>>It would certainly help if the documentation was updated properly for this type of situation. There are alot of cut and paste errors in the documentation that was leftover from previous versions.
>>>
>>>Thanks for your help.
>>>
>>>Bob
>>>>Yes,
>>>>
>>>>Dot net 4.0 GAC is in a different location.
>>>>
>>>>Check C:\Windows\Microsoft.Net\Assembly\GAC_MSIL\ You should find folders for OakLeaf.MM2010.Framework plus all the others and in each one is a folder for the assembly with the assembly in it.
>>>>
>>>>Dot Net 3.5 used the old GAC