If you are wondering about the numerous other items and tab sheets that have been ignored by the proceeding paragraph, just explore them at your leisure. For the purposes of this tutorial, please keep the experimentation at a minimum. Instead, let's move on to debugging a simple Microsoft.NET C# executable named Wilderland.EXE. (Some of you might be familiar with another article I published at www.codeproject.com/ aka "The Code Project" entitled "There and Back Again or Stepping Through the JIT Thunk Layer" and the sample program featured there. This is the same executable with one minor modification.) By selecting File/Start Debugging (or Ctrl+S), navigating through your system and selecting the executable, you will eventually fill in the "Start Debugging" dialog box with something like what is found in Figure 3:
Figure 3
This dialog box allows you to add any command line parameters and additional environment variables to the current debugging session. For now, press "OK". A display will show much like what you see in Figure 4:
Figure 4
(Note - the system on which I am writing this tutorial is Windows XP with SP1 installed and v1.1 of the .NET framework. Images and listings for this same program produced with SP2 applied to my system can be found by looking for SP2 in the name of the file.) We are seeing this breakpoint on account of our decision to "Break on process initialization?" made in the configuration Debug tab sheet.
 prev page | 1st page | next page  |