C# 程序不会作为 .EXE 在 visual studio 之外启动

Question

I have created a small program in C# winforms that runs fine when i start it in visual studio 2017. But when I build the solution and doubleclick the.exe, nothing happens, no screen appears, even task manager doesn't see it. No errors. It's like it doesn't do anything, My only guess is that I build it wrong because I used Nuget to install newtonsofts JSON.NET in te solution? do I need to do anything different or should just building the solution work?

[solved]

today i learned the difference between the bin and obj folder, thanks to everyone for helping

Answer 1

Based on your comment:

it is in the obj/debug folder of the project

It sounds like you're running the wrong .exe. The obj folder is used for temporary/misc. files from the build process (see What is obj folder generated for? ).

Instead, you want to run the exe within bin\\Debug , if "Debug" is the configuration you're building for. You can see which configuration at the top of VS.

Like others have also mentioned, make sure that Newtonsoft.Json.dll is being copied to that output directory as well. Programs and their dependencies need to be together, generally speaking. Otherwise, your exe will not know where to find the JSON code it needs to function.

99% of the time, you should pretend the obj directory isn't even there.

If that still isn't pointing you in the right direction, run the app from a command window. Any exception should get printed to it and the window will remain open for you to examine (and this has the benefit of not needing any additional logging or exception handling code to see this error).
For example, I wrote up a bad application that get a NullReferenceException in a method called Test that is called from Main . As you can see, the stacktrace is easily visible, even though my app has crashed (credit to ColinM for bringing this up originally).

Answer 2

I believe that there's a problem with the startup module. Follow the steps below

1. Open your Solution in visual studio

2. Double click on properties

   

3. Select output type to Windows Application

4. Make sure to set the startup object as follows

   

I hope it helps

Answer 3

I think there is only one reason

There is a command line argument predefined in Visual Studio. Your application uses this argument to be executed, without it, it closes itself too quickly and you even can't see your application opened.

Right click on your project in VS -> Properties -> Debug and see if there is a value in command line arguments

Answer 4

exe and their supporting files should be in the bin folder. Do not copy only exe from bin folder and try to run it. It is a good idea to write some exception code to get the detail.

Answer 5

For future reference, yet another reason (that I have experienced) can be

System.Diagnostics.Debug.Assert();

statements. In my case, the program executed normally when started from VS but when I run it by clicking its.exe (created in the Debug Mode) then it hung/freezed. No exceptions, no printed logs. Frustrating. Then I checked the Windows Event Viewer (Our true friend). It explicitly displayed the problem and the culprit was a Debug.Assert() statement.

The lesson learned again: Check

Windows Event Viewer > Windows Logs > Application

especially when your app hangs/freezes/deadlocks or when no app logs are available.