strong name validation failed problem

5 Oct 2006 12:29 AM

Darren Mar-Elia (MVP)

I've written a .net 2.0 Winforms app that contains a reference to a GPMC
(Group Policy Management Console) DLL. The DLL is distributed with the app.
When I install the app an attempt to invoke an operation that uses the DLL,
I get a strong name validation failed error on that DLL. The DLL is signed
by MS, so I guess I'm trying to figure out where I'm going wrong? What else
do I need to do to ensure that this works?

--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy
http://www.gpoguy.com -- The Windows Group Policy Information Hub:
FAQs, Training Videos, Whitepapers and Utilities for all things Group
Policy-related
Group Policy Management solutions at http://www.sdmsoftware.com

8 Oct 2006 6:14 AM

Joseph Bittman MVP MCSD

October 7, 2006

Is the MS dll strong named? ... if so, then only other strong named
assemblies can call it (assuming MS doesn't have custom permission
demands)... so is your assembly strong named?

If your assembly isn't strong named while the MS one is, then that
definitely could be the problem... although if the MS isn't strong named or
it is but so is yours... then it could be that MS's dll has a strong named
permission demand that only certain other DLLs containing a certain strong
name can call it. (which would be a problem because there isn't a very good
way at determining this)

--

Joseph Bittman
Microsoft Certified Solution Developer
Microsoft Most Valuable Professional -- DPM

Blog/Web Site: http://CactiDevelopers.ResDev.Net/

Show quoteHide quote

"Darren Mar-Elia (MVP)" <dmanonym***@discussions.microsoft.com> wrote in
message news:B95406CE-ECAE-4EE1-BA02-4B0A6AD82F82@microsoft.com...
> I've written a .net 2.0 Winforms app that contains a reference to a GPMC
> (Group Policy Management Console) DLL. The DLL is distributed with the
> app. When I install the app an attempt to invoke an operation that uses
> the DLL, I get a strong name validation failed error on that DLL. The DLL
> is signed by MS, so I guess I'm trying to figure out where I'm going
> wrong? What else do I need to do to ensure that this works?
>
>
>
> --
> Darren Mar-Elia
> MS-MVP-Windows Server--Group Policy
> http://www.gpoguy.com -- The Windows Group Policy Information Hub:
> FAQs, Training Videos, Whitepapers and Utilities for all things Group
> Policy-related
> Group Policy Management solutions at http://www.sdmsoftware.com
>
>

9 Oct 2006 10:13 PM

Nicole Calinoiu

"Joseph Bittman MVP MCSD" <RyanBitt***@msn.com> wrote in message
news:C7CDBF9B-3512-4B7E-87DF-42FBE64C9130@microsoft.com...
> October 7, 2006
>
> Is the MS dll strong named? ... if so, then only other strong named
> assemblies can call it (assuming MS doesn't have custom permission
> demands)... so is your assembly strong named?

That's the wrong way around. If an assembly is strongly named, it cannot
call into weakly named assemblies, but it can definitely accept calls from
weakly named assemblies. If this weren't the case, weakly names assemblies
wouldn't be able to use the .NET framework assemblies, which are all
strongly named.

Show quoteHide quote

>
> If your assembly isn't strong named while the MS one is, then that
> definitely could be the problem... although if the MS isn't strong named
> or it is but so is yours... then it could be that MS's dll has a strong
> named permission demand that only certain other DLLs containing a certain
> strong name can call it. (which would be a problem because there isn't a
> very good way at determining this)
>
> --
>
> Joseph Bittman
> Microsoft Certified Solution Developer
> Microsoft Most Valuable Professional -- DPM
>
> Blog/Web Site: http://CactiDevelopers.ResDev.Net/
> "Darren Mar-Elia (MVP)" <dmanonym***@discussions.microsoft.com> wrote in
> message news:B95406CE-ECAE-4EE1-BA02-4B0A6AD82F82@microsoft.com...
>> I've written a .net 2.0 Winforms app that contains a reference to a GPMC
>> (Group Policy Management Console) DLL. The DLL is distributed with the
>> app. When I install the app an attempt to invoke an operation that uses
>> the DLL, I get a strong name validation failed error on that DLL. The DLL
>> is signed by MS, so I guess I'm trying to figure out where I'm going
>> wrong? What else do I need to do to ensure that this works?
>>
>>
>>
>> --
>> Darren Mar-Elia
>> MS-MVP-Windows Server--Group Policy
>> http://www.gpoguy.com -- The Windows Group Policy Information Hub:
>> FAQs, Training Videos, Whitepapers and Utilities for all things Group
>> Policy-related
>> Group Policy Management solutions at http://www.sdmsoftware.com
>>
>>
>