Hi Jean-Marc,
Thanks for the response :)
I did what you suggested and looked at my dll under dependency walker.
The only function that's being exported is NSGetModule. Should I be
exporting something else that XPCOM is looking for before it will load
my dll?
Thanks,
Damo
Oops - 1 other thing...
I also took a closer look at compreg.dat and xpti.dat thinking that
there may be some clues here as to why my component isn't being loaded.
Below are the entries for my component in these files.
One thing I noticed in the CLASSIDS section is that with most similar
entries to mine, at the end of the contractID piece, there is a ;1 or
;2 e.g. comparing my entry with GoogleDesktop [CLASSIDS]
{b23cb38b-b82e-4f6a-9769-d8b37a3c05f5},@google/googledesktopwebcapture;1
,,GoogleDesktopWebCapture,rel:GoogleDesktopMozilla.dll
{82b9ab1d-7169-43b6-b6bb-9870ed36f7c7},@dobrien/testpageload,,TestPageLo
ad,rel:TestPageLoad.dll
My entry doesn't have this ;1. Any ideas what this signifies? Is not
having it an indication that I'm missing something in my registration
code? Could it be why my dll isn't being loaded?
Similarly in the categories and contractids sections. Most entries have
this ;1 but mine doesn't e.g. [CONTRACTIDS]
@google/googledesktopmozilla;1,{b088432c-b090-4223-bbe5-90b040fb1fc8}
@dobrien/testpageload,{82b9ab1d-7169-43b6-b6bb-9870ed36f7c7}
[CATEGORIES]
xpcom-startup,GoogleDesktopMozilla,@google/googledesktopmozilla;1
xpcom-startup,TestPageLoad,@dobrien/testpageload
Thanks,
Damo
compreg.dat entries for my component
------------------------------------
[COMPONENTS]
rel:TestPageLoad.dll,1112888214197
[CLASSIDS]
{82b9ab1d-7169-43b6-b6bb-9870ed36f7c7},@dobrien/testpageload,,TestPageLo
ad,rel:TestPageLoad.dll
[CONTRACTIDS]
@dobrien/testpageload,{82b9ab1d-7169-43b6-b6bb-9870ed36f7c7}
[CATEGORIES]
content-policy,TestPageLoad,@dobrien/testpageload
xpcom-startup,TestPageLoad,@dobrien/testpageload
xpti.dat entries for my component
----------------------------------
[Files,74]
2,TestPageLoad.xpt,0,122,1112893396439
[Interfaces,998]
667,iTestPageLoad,{82b9ab1d-7169-43b6-b6bb-9870ed36f7c7},2,-1,0
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Jean-Marc Desperrier
> Sent: 08 April 2005 09:52
> To: [email protected]
> Subject: Re: XPCOM component not being registered by regxpcom
>
>
> Damien O'Brien wrote:
> > So... At the moment I'm concluding that my dll is being opened by
> > mozilla, but not actually loaded. Maybe I (we ;-)) are missing
> > something in our dll that causes mozilla not to load the dll? Any
> > ideas?
>
> It seems to me that the most likely is that you are not exporting the
> right function names. Check with Dependency Walker what the
> exports are. _______________________________________________
> Mozilla-xpcom mailing list
> [email protected]
> http://mail.mozilla.org/listinfo/mozilla-xpcom
>
_______________________________________________
Mozilla-xpcom mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-xpcom
