BA 371 VC#.Net Assignment 1: Noughts & Crosses aka Tic-Tac-Toe

Program the game of Noughts and Crosses, aka Tic-Tac-Toe, the game played on a 3x3 board of squares where two players alternately claim a square by putting a nought or a cross in it. The player who gets three crosses or noughts in a row, either horizontally, vertically or diagonally, wins the game. In case all spaces are taken and there is no winner, the game results in a draw.

Please read all the material on this page and pay careful attention to the requirements stated below.

Click here for a demo version of the program (note: this is a command-line/console application; not a windows/graphics program! This means that you'll have to download the executable and run it on your local machine.)

Requirements

The program should exibit the following behavior and structure:

• Your program must run as a Console Application; i.e., do not!! implement it as a Windows Application.
• !!! The board must be held in memory as a 3x3 two-dimensional array of ints!!! (see your C#.Net lab exercises for how to hold data in a two-dimensional array.)
  (Your instructor is aware that enforcing this 3x3 int array requirement makes things a little harder than they have to be, but that's exactly the point of this exercise.)
• Before each move, the board and the currently free and occupied fields must be displayed (see image above). This should be abstracted in a function void display_board().
  

• A move is specified by typing the number 1-9 indicating the square to be occupied. Squares are numbered by row; i.e.,

  
  -------------
  | 1 | 2 | 3 |
  ------------- 
  | 4 | 5 | 6 |
  -------------
  | 7 | 8 | 9 |
  -------------
  
  

  A move is only valid if the square is not occupied and if the typed number is larger than 0 and smaller than 10. In case of an invalid move, generate an error and prompt for a new move. Make sure that your program does not accept nonnumeric input.
• After each move, check to see if there is a winner using the function:

  int check_for_winner()

  that returns either the winner or no winner.

• The program does not have to play multiple rounds of the game; a single game is all we ask for. However, a user should, of course, be able to run the program many times without ever running into an error.

• The program itself does not play! The program merely prompts for moves, keeps track of the board and diagnoses the validity and results of moves. For each move, the program prompts the player on turn.
• Player names are NOUGHTS and CROSSES.

Please Note!!

• You are expected to use some standard 'good programming' practices:
• Include sufficient commenting in your code so that others who are not familiar with your application can comfortably read your code and understand what it does. You will be asked to review each others' code; so you should make it legible and easily understandable.
• Use mnemonic variable names; i.e., use names that represent what they mean. For instance, if you have a counter of sorts, call it counter, rather than i or j.  (i and j for loop indexes are fine, however).
• Introduce a function naming convention that makes it easy for people reading your code to distinguish between functions that you wrote versus the ones that come supplied with C#.Net; e.g., start all your functions with an underscore; e.g., _myFunction(). (There exists a sizable literature on naming conventions, name spaces, etc. We do not need to detail any of this here, but it makes sense to introduce at least a few, simple conventions that increase the readability of your code). Make sure that you include your naming conventions in a comment block (there is little point in having the convention if you don't tell your reader what it is!).
• Thoroughly check for errors and exceptions. Colleagues reviewing your code will be asked to try and 'break it.' Make sure they cannot.