Can't find dll

  • Thread starter Thread starter Alberto
  • Start date Start date
A

Alberto

A program written in C# has some reports done with the Crystal Reports
included in VS.Net.
I did an instalation (instalation proyect) but the customer, after install
the program, when tries to see a report, the program says that can't find
the KeyCodeV2.dll. I installed the dll with the regsrv32 , but the program
says the same.

What's happening?
Thank you.
 
Alberto said:
A program written in C# has some reports done with the Crystal Reports
included in VS.Net.
I did an instalation (instalation proyect) but the customer, after install
the program, when tries to see a report, the program says that can't find
the KeyCodeV2.dll. I installed the dll with the regsrv32 , but the program
says the same.

What's happening?
Thank you.

Did you check the registry to see that it registered OK? Make sure the user
is logged in as local Administrator while you register the dll.

/Fredrik
 
Yes, he is local administrator but, anyway, why the instalation proyect
doesn't include it?
Did I do something wrong?
 
Alberto said:
A program written in C# has some reports done with the Crystal Reports
included in VS.Net.
I did an instalation (instalation proyect) but the customer, after install
the program, when tries to see a report, the program says that can't find
the KeyCodeV2.dll. I installed the dll with the regsrv32 , but the program
says the same.

It's not necessarily the KeyCodeV2.dll that's missing - it could be another
assembly that KeyCodeV2.dll references.

I had a similar problem with an app that was using MySQL: mono complained that
could not find my dll, but it was there: infact the missing assembly turned out
to be MySqlData.dll...
 
Fabio said:
It's not necessarily the KeyCodeV2.dll that's missing - it could be another
assembly that KeyCodeV2.dll references.

I had a similar problem with an app that was using MySQL: mono complained that
could not find my dll, but it was there: infact the missing assembly turned out
to be MySqlData.dll...

True. Check the KeyCodeV2.dll dependencies. There is in fact one more thing
you can do. It is possible that the dll made some changes in the registry
but not all. This has happened to me. The solution was to first unregister
and then register.

/Fredrik
 
Back
Top