This might be a stupid question but it is not covered in any materials I
have been reviewing.
Basically, I am consuming a COM component using interop in my .ASP.Net
application. When I move code over to production and run the project, I get
the following error:
COM object with CLSID {4A395049-408D-4B74-B810-36009887FE16} is either not
valid or not registered
the class ID of my component in production is different from the one in my
development environment.
Question:
Does .Net COM Interop cares about Class ID. Does he keep track of Class
ID's in the Metadata?
Robert Jordan - 08 Nov 2005 10:23 GMT
Ali,
> Basically, I am consuming a COM component using interop in my .ASP.Net
> application. When I move code over to production and run the project, I get
[quoted text clipped - 10 lines]
> Does .Net COM Interop cares about Class ID. Does he keep track of Class
> ID's in the Metadata?
Of course it does.
Robert
Ali Elhamdi - 08 Nov 2005 14:39 GMT
Second Question:
If the question is Yes. And most likely it is a yes. Meaning that the RCW
has to know the CLSID of the unmanged component, then where do I find that
CLSID in my assembly. I've tried ildasm and looked at teh manifest and
could not see anything that looks like a CLSID.
How can I see that information? What tool do I need to use?
Ali
> This might be a stupid question but it is not covered in any materials I
> have been reviewing.
[quoted text clipped - 13 lines]
> Does .Net COM Interop cares about Class ID. Does he keep track of Class
> ID's in the Metadata?
Robert Jordan - 08 Nov 2005 14:51 GMT
> If the question is Yes. And most likely it is a yes. Meaning that the RCW
> has to know the CLSID of the unmanged component, then where do I find that
> CLSID in my assembly. I've tried ildasm and looked at teh manifest and
> could not see anything that looks like a CLSID.
>
> How can I see that information? What tool do I need to use?
It is in the interop assembly.
Rob