1

I have a c++ project (acrobat pdf plugin) that uses a com visable c# dll. On my pc everything is working perfectly but on my deployment server I get the error "Unable to create object". I have registered the dll on the deployment machine using regasm and created the .tlb file on the same location of the dll. I used comxplorer and I compared the clsid of the components between my machine and the deployment machine, and they match.

this com dll does use other dlls (it's a pretty big project)

Can late binding or something like that help me? How can I begin to investigating this issue?

Please advise

David
  • 5,403
  • 15
  • 42
  • 72
  • `procmon` filtered on CreateFile failures is one way, albeit somewhat manual. – WhozCraig Jan 29 '14 at 08:11
  • @WhozCraig what do you mean? – David Jan 29 '14 at 12:31
  • 1
    I mean use sys internals [Process Monitor](http://technet.microsoft.com/en-us/sysinternals/bb896645) to capture events related to failed CreateFile calls for your process. The missing mystery DLL(s) will be in the list. there are other ways, but that is pretty straight up (and its a helluva tool, btw). – WhozCraig Jan 29 '14 at 12:33
  • You are right this is great. It shows that I have no idea how com works – David Jan 29 '14 at 14:13

1 Answers1

1

When I register the com dll I need to add /codebase e.g.

...\regasm.exe "c:\foo.dll" /codebase
David
  • 5,403
  • 15
  • 42
  • 72