Reputation: 35557
I've got a small, very simple, winforms which calls one class and is writing it's results to a console in Visual Studio's console window - the console called Output
found in VSs Debug
menu.
Some messages are automatically generated on the console and I am interested to understand what they mean; the following appears immediately after the information that the winforms wrote to the console - is this the thread that was doing the processing?
The thread '<No Name>' (0x2280) has exited with code 0 (0x0).
Screenshot of what I see in VS...
Upvotes: 2
Views: 1591
Reputation: 37566
Code 0 is good, its debug infoirmation that the process end as expected withno exceptions.
Upvotes: 0
Reputation: 106826
The message means that a thread has ended but that shouldn't be a surprise.
I guess you want to know why threads are ending in your application even though you didn't create any new threads in your code. When using a framework like Windows Forms the framework will use threads to perform some additional work. These threads are normally taken from the .NET thread pool. What the thread has been doing before ending requires a bit more research though.
Upvotes: 3
Reputation: 5801
It show the threads currently being used to run your applycation as well as the threads running for the debugger. While the application is running the debugger can spawn new threads as well as end threads. When you see the thread exited with code 0, it means a normal exit was achieved that implied no errors.
Upvotes: 1
Reputation: 62246
It means that there was a thread, that correctly executed and returned 0
.
That is.
Upvotes: 0
Reputation: 4697
Exited with code 0 usually means completed successfully (with no errors).
Upvotes: 0
Reputation: 451
regarding the Thread
message, a Thread
that exists with code 0
has succesfully completed all procedures. any other code would indicate unhandeled exceptions
the headfirstPage204Farmer.vshost.exe
message is the executable which Visual studio
uses to run the application
Upvotes: 0