CLR looking for assembly in wrong location

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am installing 2 windows services from the command line. When I go to
install the first one it installs fine and starts up. The second one installs
but won't start. The error message indicates that there was a failure to load
an assembly. This is happenning because the GAC seems to be looking for the
assembly in the same directory as where the first service was installed from.
The services both use one of the same assemblies (and there is a copy of that
assembly in both install locations).

Why is the CLR looking for the assembly in the wrong place? How can I fix
this?

I am running .NET 2.0 in Windows 2003 server.

Thanks,
IP
 
I assume you are not the developer of the services.

It may be due to the choice (or not) of "Copy Local" by the developer. This
is one of the properties of the "reference". If this is the case you may have
to go back to the developer...
 
Thanks Brad!

I am the developer on the project (although new to this code base). I take
it that the 'Copy local' applies only when debugging the app and services.
The same problem seems to be occuring with release code. Any thoughts on that?
 
Back
Top