First of all, the possible reason is that your application has an exception, but. The net is not caught or can't be caught, resulting in the following situations:

1, double-click the executable program, no response.

2. At this time, if you go to the task manager, you will see a process of DW20.exe, which will disappear automatically soon.

3. In the event viewer, you will find an error message similar to the event type CLR20R3P 1 ... P2...PN.

Second, the solution:

1, the specific problem may have different solutions, but the error in the event viewer still gives some suggestive information.

2. There is a pn in the p 1 ... error message, where p is followed by the namespace that caused the exception. You need to find out whether spaces are used in the code, especially at the beginning of the program, such as Program.cs

3. For me, it is a system. Throwing a Remoting error, my program uses Remoting, so considering that the port may be occupied, the program can start normally by changing the port.

4. In addition, it is best to add a global exception capture to the program, so that when an exception occurs, there will be detailed prompt information, which will not be confused.