CS260 - Handout 0

Using the Computers In The Math/CS PC Laboratory

The computers in Math/CS PC laboratory will allow you to access the Microsoft Visual C++ Integrated Development Environment (IDE). The computers are attached to the ESU network and allow access to software for computer science courses as well as Internet access. The lab machines use the Windows NT operating system.

Using Microsoft Visual C++

Step 1. Double click on the icon. This will start the development environment.

Step 2. To create a project for an application, first select New... from the File menu to display the New dialog.

Click the Projects tab and highlight Win32 Console Application. Select the directory in which the program should be stored by clicking the button to the right of the Location field. (The temp directory is a really good place to temporarily store your projects. You also may wish to use storage.cs.emporia.edu to store your projects.). Name the project myProject. Notice that the name of the project is added to the directory path in the Location field. Each project is normally stored in its own directory. Click the OK button to create the project. Note that the OK button is disabled unless a name is specified in the Project Name field.

Next the Win32 Colsole Application dialog box appears. Make sure "an empty project" radio button is selected and click on Finish and then OK.

Step 3. Next, create a new C++ Source File to display a source window in which to type your program. Select New... from the File menu to display the New dialog. Click the Files tab and highlight C++ Source File.

Enter the name of the file in the File name box. Save the file by clicking OK.

Step 4. You can now enter your program into the program window. When you've entered your program be sure to select Save All... from the File menu to save your work.

Step 5. Now you are ready to compile and execute your program. Select Execute from the Build menu. Your program will now execute if it does not contain compilation errors. You should see the console window:

If this window does not appear, check the messgae box at the bottom of the screen for error messages.

Files Createed in the Compilation Process

The compilation process in Visual C++ generates a number of files. Thses files are created in the project folder and a debug subdirectory within the project folder. The two most important files when starting programming are:

• .exe - A program file created from one or more source code files translated into machine code and linked together. The MS-DOS, Windows, and Windows NT operating systems use the .EXE filename extension to indicate that the file is a runnable program.execution character.
• .cpp - A text file containing C language code you have input.

The other files created are:

• .dsp - This is the project file used within the development environment.It stores the information specific to your project. There will be a separate .DSP file for each project you create.
• .dsw - When you create a project workspace, a project workspace file ProjectName.dsw is created to store information at the workspace level.
• .ncb - It contains information generated by the parser which is used by ClassView, WizardBar, and Component Gallery. If the file is accidentally or deliberately deleted, it is automatically regenerated.
• .opt - This is the workspace options file used within the development environment. It stores all the user options you create for your workspace, so that each time you open the project workspace it has the look and feel you want and includes any customizations you have made.
• .htm - contains the Build Log for the compilation.
• .obj - A file containing object code and/or data generated by a compiler or an assembler from the source code of a program.
• .ilk - When linking incrementally, LINK updates the .ILK status file that it created during the first incremental link. This file has the same base name as the .EXE file or .DLL file, and it has the extension .ILK.
• .pch - A file containing compiled code for a portion of a project. Subsequent builds combine this file with the uncompiled code, thus shortening the overall compile time.
• .pdb - The .pdb (program database) file holds debugging and project state information. The .pdb file provides the information needed for incremental linking of debug program versions.
• .idb - The compiler (when an appropriate switch is set) compiles only those functions that have changed since the last compile. The compiler saves state information from the first compile in the project�s .IDB file