File or assembly name or one of its dependencies, was not found...

  • Thread starter Thread starter Rudolf Dvoracek
  • Start date Start date
R

Rudolf Dvoracek

Hi,

we have some web solutions still running on old ASP 3.0 Platform. So I
created .NET component in c# with COM interoperability and registered it on
server. But when i try to create a new instance in asp page, server show
following message:


File or assembly name HPTronic.Advertise, or one of its dependencies, was
not found.


Operations with this component goes at my machine without any warning
messages or errors, I can create new instances, access to their properties
and methods, so I mean here should be problem with user-access rights to
some directories on deployment machine. HPTronic.Advertise.dll file is placed
in same directory, where are other dll files, which we use as ActiveX objects
too.


Thank you for any valuable advice,

Rudolf DvořáÄek.
 
Not yet, but I registered dll with tlb and codebase option. When I run
similar *.vbs script with my own account, instance would be created correctly.

Rudolf.
 
Try adding it to the gac then :)

Rudolf Dvoracek said:
Not yet, but I registered dll with tlb and codebase option. When I run
similar *.vbs script with my own account, instance would be created
correctly.

Rudolf.
Click to expand...
 
Why? Here is no reason to add dll to GAC. Due to knowledgebase
recommmendations you can add dll to GAC or register it with /codebase option.
You have two choices. Both of them can be used.

R.D.
 
Why? Here is no reason to add dll to GAC. Due to knowledgebase
recommmendations you can add dll to GAC or register it with /codebase option.
You have two choices. Both of them can be used.

R.D.
 
Why? Here is no reason to add dll to GAC. Due to knowledgebase
recommmendations you can add dll to GAC or register it with /codebase option.
You have two choices. Both of them can be used.

R.D.
 
It probably is finding the dll ok anyway, otherwise you'd get a different
error message.

If it works from a vbs script then I'd look at permissions, maybe it needs
access to a dll it doesn't have permissions to read when called via an aspx
page. Does the dll reference anything else?
 
Back
Top