Mike,
This has nothing to do with mm and everything to do with how assemblies are signed when built in Dot net and VS. It applies to your work as well if you protect your assemblies.
Timothy
>Great catch, and ongoing kudos for your contributions here in general. But this makes me really, really glad not to be an MM user.
>
>>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
Timothy Bryan