.NET - VB - VS 2005 - Noob questions: Does "exited with code 0" indicate an error?

In VS, I ran (clicked on "Start Debugging") what I believe is the main portion of a project I've inherited and some stuff came up in the *debug out window* (*terminology?) which I've pasted in part (edited for length) below. Does any of this indicate an error? Or anything else, for that matter?





= = =





'load3.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly... blah, blah... .dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.


(** about a dozen lines similar to the one above **)


The thread 0x38c has exited with code 0 (0x0).


(** three lines similar to the one above **)


'load3.vshost.exe' (Managed): Loaded 'C:\...blah, blah...\load3.exe', Symbols loaded.


'load3.vshost.exe' (Managed): Loaded 'C:\...blah, blah...\amqmdnet.dll', No symbols loaded.


The thread 0x142c has exited with code 0 (0x0).


The thread 0x5e8 has exited with code 0 (0x0).


The program '[5836] load3.vshost.exe: Managed' has exited with code 0 (0x0).





= = =





Thanks!





Scott

.NET - VB - VS 2005 - Noob questions: Does "exited with code 0" indicate an error?
Depends on the software. Usually, it is good practice to write code like:





int main(){


//do stuff


if (someweirderror) return errorcode;


// do more stuff


return 0;


}





Good practice indicates that if your program terminates correctly, it should return 0, otherwise it should return an error code. Given your output there, it should have terminated correctly, given that good practice has been followed.
Reply:When things exit with code zero (0x0), it means that it didn't return anything (like an error). This is normally a good thing in the .Net environment.
Reply:A return code of 0 normally indicates successful completion.