.net app won't run. When compiling on dest machine (same sources) it does work. Why?

Posted by reinier on Stack Overflow See other posts from Stack Overflow or by reinier
Published on 2010-05-26T11:28:29Z Indexed on 2010/05/26 11:31 UTC
Read the original article Hit count: 260

I have a service which needs to be deployed on a clients machine.

The destination machine is 64bit. My dev machine is also 64 bit. The app is really simple, listens on a port and does some db things. It targets .net 3.5

When I deploy the Anycpu, the X64 or the X86 version, the thing won't install on the clients machine.

I checked dependencywalker and it lists: devmgr.dll ieshims.dll wer.dll

anyhow...I install visual studio 2008 on the clients machine... check out all the sources. I don't change a thing and compile. Copy the exe over to it's dest locations...and what do you know..it works.

Dependencywalker still lists the same dependency problems.

How can it be that the act of compiling it on this machine gives me a different exe?

© Stack Overflow or respective owner

Related posts about .NET

Related posts about dll