Assembly could not be resolved

  • Thread starter Thread starter Fred
  • Start date Start date
F

Fred

Hello,

When I use Reflector on some computers, I have this message when trying
to expand some dll references.
«Assembly could not be resolved ...»
Reflector show me a path, I just validate and it's ok.

Do you know where I can search to solve this problem ?

(it's not a problem in reflector but in a .NET com visible class I
developped, even with a simple Hello World class)
 
in Alvin Bruney
[ASP.NET MVP] wrote :
your com visible class needs to be registered on the machine. Have you
checked to see that this is the case?
Click to expand...

The installer do it for me. I checked the keys in the registry and every
things seems ok. The error message is not «An active X could not be
created» but «the assembly or one of its dependencies could not be
loaded».

What makes me think it is a default in the framework installation is the
strange behavior of Reflector. This behavior appears on the framework's
dll. Wether my com class is installed or not.

It seemes to have «broken» links, or missing paths. I don't know enough
about the details of framework installation.
 
in Alvin Bruney
[ASP.NET MVP] wrote :
your com visible class needs to be registered on the machine. Have you
checked to see that this is the case?
Click to expand...

I finally found that it is probably a problem with Office installation.
It works fine in a simple vbs.
I will try to solve the problem considering this. It's not any more a
framework problem.
 
Back
Top