views:

30

answers:

2

I built a windows service on my local machine. when I install and run it locally it works perfectly fine. When I try to move it to my production machine I get a null reference exception error.

I've created an installation package that also works perfectly fine on my machine, but when i run it on the production machine the service still fails.

The service references a .dll that in turn has references to 3 other dlls. when i build the project it pulls all of the dlls into the debug folder for the project... I've even installed the service from that folder and it works localy on my machine.

I know this has to have something to do with the references, but this is beyond me. Any tips/hints would be appreciated.

A: 

Make sure the machine you are installing it has the same machine has the same .dll your expecting installed. For example if you are using .NET, and wrote the service in 3.5 and the target machine only has 2.0 that could be an issue, especially if the installer didn't try to install it.

David Basarab
I made sure that as one of the dependances for the service that 3.0 was installed... the server that this is going to also houses 4 - 5 other web apps that are written in anything from 2 - 3.5.
Patrick
A: 

if you take a look at the comments you'll see what the issue was.

Patrick