Referenced assembly 'interop.WbemScripting' doesn't have a strong

11 May 2006 2:25 PM

ShrimpBoy

Hi!

I'm using a Strong Name Key to create our assemblies, this key has the Full
Trust security so we can use those "mini tools" from network drives...

I'm trying to use WMI to get access to data in our SMS Server...

Now, when I tried to create my assembly I got this message...

"Unable to emit assembly: Referenced assembly 'interop.WbemScripting' does
not have a strong name"

What is the problem?

How can I use WMI as required in the way I need?

Is there another way to get access to this data?

Thanks!

ShrimpyOne

12 May 2006 2:15 PM

Dragon

Hi,

AFAIK, if an assembly have a strong name, all assemblies it depends on
should also have it. It seems you can use the technique described in
"How to link to an ActiveX Control from a Strongly Named Assembly"
(http://blogs.msdn.com/shawnfa/archive/2005/01/13/352636.aspx) but using
TlbImp instead of AxImp.

HTH,
Roman

"ShrimpBoy" <Shrimp***@discussions.microsoft.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ ×

ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
Show quoteHide quote

news:24F1A3DF-3DCF-4490-8D22-1529D7FA7C7E@microsoft.com...
> Hi!
>
> I'm using a Strong Name Key to create our assemblies, this key has the
Full
> Trust security so we can use those "mini tools" from network drives...
>
> I'm trying to use WMI to get access to data in our SMS Server...
>
> Now, when I tried to create my assembly I got this message...
>
> "Unable to emit assembly: Referenced assembly 'interop.WbemScripting'
does
> not have a strong name"
>
> What is the problem?
>
> How can I use WMI as required in the way I need?
>
> Is there another way to get access to this data?
>
> Thanks!
>
> ShrimpyOne