CODEWITHSUNDEEP
c#installation
UnderPaidIntern
UnderPaidIntern

Reputation: 59

Nothing happens when I run my application after setup

I'm aware that a lot of topics about similar problems exists but none of them solved my issue.

So I have an aplication, which works perfectly.I added to the solution the installShield-wizard-setup-something for me to be able to install it everywhere. I tried on my computer (the one with whom I created the program) and it worked!

I installed it on another PC and after the installation (which was fine) when I cick to run the .exe, there is a quick loading (the cursor turns into a blue circle) and then nothing..

Nothing in the processes, nothing in the logs, running it as admin didn't work. I tried to install it elsewhere but same thing happens. I also checked the .NET version and it's the right one.

I don't know what other informations to tell, so please feel free to ask me if you have a clue. I'm running out of solution here.

EDIT : Actually in the processes I see my application during the quick load. enter image description here The result of Dependency Walker

Upvotes: 3

Views: 887

Answers (1)

Nik Bo
Nik Bo

Reputation: 1410

It could be that your application uses some Dll's which needs other Dll's and so on. I got this problem sometimes. For me the Dependency Walker is very useful to find every dependency of your program and the sub dependencies. Dependency Walker is a free tool which you can download. Just open dependency walker, select your program exe (on your development Computer where the program works) and check the shown dependencies with the files on your destiny computer (where the program don't works). Maybe you find some missing Dll's.

Here an example for AMSI.dll:

Here an example for AMSI.dll

At first check on the destiny computer this dll's. Are one of them are missing, copy manually the Dll from your development System and make a note that you copied this dll.

If all Dlls on the computer and your program still not works, continue with the next layer. Open the dll's and check their dependencies:

Layer 2

Ignore the red crossed ones. Just look for the dll's with "normal" names.

Just continue with the other dll's layer for layer. In my cases the second layer was enough to run the program.

Ps. Normally it's enough to check the first listed Dll's like Kernelbase.dll and not Dll's like API-MS-WIN-CORE-PROCESSTHREADS-L1-1-3.DLL ... you will see what I mean. (Look at picture 2 (Layer2))

Upvotes: 1

Related Questions