Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • 4
    "or one of its dependencies" Commented Feb 13, 2014 at 19:58
  • @HansPassant Since the only dynamic libraries referenced are the ones I've listed, wouldn't that suggest that it's not due to a dependency? Commented Feb 13, 2014 at 20:35
  • That assumes that you know what the dependencies are for nbis.dll. You don't know. The vendor or author knows. Commented Feb 13, 2014 at 21:01
  • @HansPassant I compiled nbis.dll from the author's source. The assemblies listed in the nbis project properties were: System, System.Data, System.Drawing, System.XML. All other dependencies were static libraries. Is there somewhere else dependencies might be hiding? Commented Feb 13, 2014 at 21:14
  • 4
    Use SysInternals' Process Monitor. You'll see your program searching for the DLL and not finding it. Commented Feb 13, 2014 at 21:15