DOCSLIB.ORG

Creating a C Language Console Project with Microsoft™ Visual Studio C++ 5.0/6.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Creating a C Language Console Project with Microsoft™ Visual Studio C++ 5.0/6.0 CST8152 – Compilers Creating a C Language Console Project with Microsoft™ Visual Studio C++ 5.0/6.0 Creating a Console Project with MS-Visual C++ 5.0/6.0 MS-Visual C++ IDE in its many incarnations is the “de-facto” development tool for developing Windows applications. It supports 32-bit applications only. Our compiler will be 16-bit application, but you can still use MS-Visual C++ to develop it. To create a Console Project with MS Visual C++ 6.0 IDE follow the steps (rather clicks ☺) outlined bellow: S1. Launch the MS-Visual C++ 6.0 compiler (IDE) Integrated Development Environment (IDE) window will appears with an empty gray screen. S2. Create a Project 2. Select File, New from the main menu bar. The New dialog window will appear on your screen. It contains several tab-lists. The default tab is the Projects tab, which displays the type of projects you can create. Select Win 32 Console Application as the project’s type. Type the name of your project into the Project name text box. For example: cdtypes . Enter the location (the folder or directory) you want to store your project – you can type it or use … button to select it. For example: c:\compiler or better n:\compiler . Make sure that the check box in front of Win32 in the Platform text field is checked and the radio button Create new workspace is ”pressed” (contains a dot). When you click the OK button a new dialog window will appear: Win32 Console Application – Step 1 of 1 The default selection is An empty project . If not, select it. Click Finish and the New Project Information dialog window will pop up. The New Project Information text box must contain only the following two lines: + Empty console application. + No files will be created or added to the project. If everything seems, click OK . This completes the basic project creation. A new folder (directory) called cdtypes (the project name) will be automatically created on your hard drive inside the folder location that you have indicated as the Location: entry. This folder is called “project workspace” in MC Visual C++ IDE. The workspace folder will contain the project definition files, your source files, and another folder (directory) named Debug . The definition of the project is stored in a file with the extension .dsp (or .mak in some previous versions). CST8152 – Compilers Page 1 of 5 Additionally, the new workspace will automatically be opened in MS Visual C++ IDE. You will see that two tabs have been added to project Workspace window: Class View and File View . You are to use the C language to write your compiler and since C is a procedural language, the Class View is irrelevant. Click the File View tab and should see the following It shows your workspace - project name (cdtypes) the root of the project files ( cdtypes files ). Click the + to expand the tree. You will see tree folders: Source Files , Header Files , and Resource Files . All those folders are empty at this point. You can remove (select and press Delete) the Resource Files folder since it is not need for console type applications. S3. Specify the Project Options You can set a range of options for a project through Project, Settings … menu. These options determine how your source code is to be processed during the compile and link stages. When you create a new project workspace, MS Visual C++ IDE will automatically create configurations for producing two versions of your application. One includes information, which will help you to debug your program, and is called Debug version. The other, called Release version, has no debug information included and has the code optimization options for the compiler turned on. You can choose which configuration of your program to work with by selecting Build, Set Active Configuration . During the development and test phases of your application, you will be working with the debug configuration. Once your application has been tested and proven to be working correctly, you would typically rebuild the program as a release version. 3. Select (highlight) the Workspace or project files line in the Workspace window (for example: Workspace ‘cdtypes’: or cdtypes files ). Select Projects, Settings . The Project settings dialog window will appear. The default tab is General . The Microsoft Foundation Classes : list field must contain Not Using MFC . If not set it to that option. Click the C/C++ tab and make the following changes to the default settings: Category: General Warning Level: Level 3 Change to Level 4 . Category: Customize CST8152 – Compilers Page 2 of 5 Click the Disable language extensions checkbox (this will force the compiler to be ANSI C compliant). Category: Precompiled Headers Click the Not using precompiled headers radio button. Category: Listing Files Listing file type: No Listing Do not change anything but explore the options in the list box. No other default project settings need to be changed but you can click the other tabs and see the different settings they define. For example, the Link tab allows you to change the name of your executable target (in your case cdtypes.exe). Click OK to save the project settings. 4. Now you can save your project settings. Select File, Save Workspace . To open an existing project select File, Open Workspace , highlight the file with the extension .dsw , and click the Open button. S4. Add a Source File to the Project 5. To add a new file, select File, New . The New dialog window will show up with the File tab as a default. Select C++ Source File . If you want to add a new header file you should select C/C++ Header File . Click Add to project checkbox. Type the name (for example, cdtypes.c ) in the File name: text filed. The extension of the file MUST be .c in order to force MS Visual C++ IDE to switch to the C language compiler. Check the contents of the Location: field and click the OK button. You should see your c file as shown in the figure below: 6. To add an existing file ( .c or .h ), select Project, Add To Project, Files and use the Insert Files into Project dialog window to add the file. Alternatively, in the workspace window right-click the project name and select the Add Files to Project option or right-click the corresponding folder, for example Source , and use Add Files to Folder option. You should see your c file as shown in the figure above. 7. To remove an existing file from the project: in the workspace window select File view tab, click the + in front of the project files (for example cdtypes files ), click + in front of CST8152 – Compilers Page 3 of 5 the Source file folder icon, select (highlight) the file you want to remove end press the Delete key. This action will remove the file from the workspace - project but will not physically delete the file. Save the project (see step S3, item 4). S5. Write or Edit the Source Files 8. When you add a new file to the project the editor window will open automatically and you should see the file name displayed in the editor window title bar. You can begin writing your program. If the already exists and it has been added to the project, you can open it for modifications. To do so, find the file in the project workspace and double click on it, or use File, Open . S6. Compile and Build your Application 9. To compile and/or link your program, you can use the Build option in the main menu bar (to compile, the .c source code file window must be active), the BuildMiniBar floating tool bar (Hint: use the “bubble” help boxes to find out the functions assigned to the buttons), or you can click with the right button on the corresponding file in the workspace window. You should first compile your .c files one by one and after all errors and warnings are cleared, build the project. S7. Run the Application (Program) 19. To run the program, you should open a Command prompt or DOS window. Do not use the ! button. There are many ways to open a Command Prompt window: you can choose Start, Programs, Accessories, Command Prompt or alternatively, Start, Run, type cmd or command , and click OK; in our labs you can also click on the Windows Command Processor icon located on the right of the Start button on the Task bar. Once you have the command prompt window opened, use the cd command to navigate to your project Debug directory type the name of your executable (for example, cdtypes ) and press Enter. If your application requires command line arguments (and the compiler project will require some) you must type them separated with a space after the program name. Possible problems As indicated above MS-C++ generates only 32-bit applications (the size of the integer type is 4 bytes). We will work with a16-bit application. To avoid possible problems you must test your application with Borland 5.02 before submitting it. CST8152 – Compilers Page 4 of 5 MS-C++ does not support alloc.h. Use instead malloc.h or stdlib.h. You need these header files for the memory management functions: alloc(), realloc(), and free(). S^R, 2008 CST8152 – Compilers Page 5 of 5 .
Load more

Recommended publications
  • Using Microsoft Visual Studio to Create a Graphical User Interface ECE 480: Design Team 11
    Using Microsoft Visual Studio to Create a Graphical User Interface ECE 480: Design Team 11 Application Note Joshua Folks April 3, 2015 Abstract: Software Application programming involves the concept of human-computer interaction and in this area of the program, a graphical user interface is very important. Visual widgets such as checkboxes and buttons are used to manipulate information to simulate interactions with the program. A well-designed GUI gives a flexible structure where the interface is independent from, but directly connected to the application functionality. This quality is directly proportional to the user friendliness of the application. This note will briefly explain how to properly create a Graphical User Interface (GUI) while ensuring that the user friendliness and the functionality of the application are maintained at a high standard. 1 | P a g e Table of Contents Abstract…………..…………………………………………………………………………………………………………………………1 Introduction….……………………………………………………………………………………………………………………………3 Operation….………………………………………………….……………………………………………………………………………3 Operation….………………………………………………….……………………………………………………………………………3 Visual Studio Methods.…..…………………………….……………………………………………………………………………4 Interface Types………….…..…………………………….……………………………………………………………………………6 Understanding Variables..…………………………….……………………………………………………………………………7 Final Forms…………………....…………………………….……………………………………………………………………………7 Conclusion.…………………....…………………………….……………………………………………………………………………8 2 | P a g e Key Words: Interface, GUI, IDE Introduction: Establishing a connection between
    [Show full text]
  • Practical ASP.NET Web API
    Practical ASP.NET Web API Badrinarayanan Lakshmiraghavan Practical ASP.NET Web API Copyright © 2013 by Badrinarayanan Lakshmiraghavan This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Exempted from this legal reservation are brief excerpts in connection with reviews or scholarly analysis or material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work. Duplication of this publication or parts thereof is permitted only under the provisions of the Copyright Law of the Publisher’s location, in its current version, and permission for use must always be obtained from Springer. Permissions for use may be obtained through RightsLink at the Copyright Clearance Center. Violations are liable to prosecution under the respective Copyright Law. ISBN-13 (pbk): 978-1-4302-6175-9 ISBN-13 (electronic): 978-1-4302-6176-6 Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights.
    [Show full text]
  • Command Line Interface User Guide for Version 11.0 Copyright © 1994-2017 Dell Inc
    Command Line Interface User Guide for Version 11.0 Copyright © 1994-2017 Dell Inc. or its subsidiaries. All Rights Reserved. Contact Information RSA Link at https://community.rsa.com contains a knowledgebase that answers common questions and provides solutions to known problems, product documentation, community discussions, and case management. Trademarks For a list of RSA trademarks, go to www.emc.com/legal/emc-corporation-trademarks.htm#rsa. License Agreement This software and the associated documentation are proprietary and confidential to EMC, are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice below. This software and the documentation, and any copies thereof, may not be provided or otherwise made available to any other person. No title to or ownership of the software or documentation or any intellectual property rights thereto is hereby transferred. Any unauthorized use or reproduction of this software and the documentation may be subject to civil and/or criminal liability. This software is subject to change without notice and should not be construed as a commitment by EMC. Third-Party Licenses This product may include software developed by parties other than RSA. The text of the license agreements applicable to third-party software in this product may be viewed on the product documentation page on RSA Link. By using this product, a user of this product agrees to be fully bound by terms of the license agreements. Note on Encryption Technologies This product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when using, importing or exporting this product.
    [Show full text]
  • CA Plex C# Best Practices
    CA Plex C# Best Practices Example Document Creating packages and code libraries and managing C# source code and application artifacts CA Plex version 6.1 Created by: In collaboration with IIDEA Solutions and CCH, and assistance from CA. Published with the kind permission of the South Carolina Judicial Department . Packages and .NET Assemblies Best Practices for CA Plex. Contents 1. Introduction ......................................................................................................................................... 3 2. Use of assemblies and modules when creating code libraries ............................................................. 3 3. Creating and using assemblies ............................................................................................................. 4 4. Considerations when packaging your model ....................................................................................... 5 5. Software required on the build server .................................................................................................. 6 6. Modelling C# Code Libraries in Plex .................................................................................................. 7 7. Setting up the build server and installing Cruise Control .................................................................. 10 8. Development life cycle ...................................................................................................................... 20 Appendix ..................................................................................................................................................
    [Show full text]
  • Programming with Windows Forms
    A P P E N D I X A ■ ■ ■ Programming with Windows Forms Since the release of the .NET platform (circa 2001), the base class libraries have included a particular API named Windows Forms, represented primarily by the System.Windows.Forms.dll assembly. The Windows Forms toolkit provides the types necessary to build desktop graphical user interfaces (GUIs), create custom controls, manage resources (e.g., string tables and icons), and perform other desktop- centric programming tasks. In addition, a separate API named GDI+ (represented by the System.Drawing.dll assembly) provides additional types that allow programmers to generate 2D graphics, interact with networked printers, and manipulate image data. The Windows Forms (and GDI+) APIs remain alive and well within the .NET 4.0 platform, and they will exist within the base class library for quite some time (arguably forever). However, Microsoft has shipped a brand new GUI toolkit called Windows Presentation Foundation (WPF) since the release of .NET 3.0. As you saw in Chapters 27-31, WPF provides a massive amount of horsepower that you can use to build bleeding-edge user interfaces, and it has become the preferred desktop API for today’s .NET graphical user interfaces. The point of this appendix, however, is to provide a tour of the traditional Windows Forms API. One reason it is helpful to understand the original programming model: you can find many existing Windows Forms applications out there that will need to be maintained for some time to come. Also, many desktop GUIs simply might not require the horsepower offered by WPF.
    [Show full text]
  • For Mac OS X
    C More on Stata for Mac Contents C.1 Using Stata datasets and graphs created on other platforms C.2 Exporting a Stata graph to another document C.3 Stata and the Notification Manager C.4 Stata(console) for Mac OS X C.1 Using Stata datasets and graphs created on other platforms Stata will open any Stata .dta dataset or .gph graph file, regardless of the platform on which it was created, even if it was a Windows or Unix system. Also, Stata for Windows and Stata for Unix users can use any files that you create. Remember that .dta and .gph files are binary files, not text (ASCII) files, so they need no translation; simply copy them over to your hard disk as is. Files created on other platforms can be directly opened in the Command window; for example, you can load a dataset by typing use filename or by double-clicking on the file in the Finder. C.2 Exporting a Stata graph to another document Suppose that you wish to export a Stata graph to a document created by your favorite word processor or presentation application. You have two main choices for exporting graphs: you may copy and paste the graph by using the Clipboard, or you may save the graph in one of several formats and import the graph into the application. C.2.1 Exporting the graph by using the Clipboard The easiest way to export a Stata graph into another application is to use drag and drop. You can select the graph in the Graph window and drag it to the location you would like it in another open application.
    [Show full text]
  • C Add Web Reference to Console Application
    C Add Web Reference To Console Application Opposed Taylor escalading observantly while Frederic always garner his gyrations parody similarly, he pledging so impudently. Heliolithic and nihilism Zak gelatinizes her polyclinics blueing elect and triturated palewise. Liable Morse preplanned irretrievably, he territorializes his Leto very man-to-man. And once provided project reference is added we can extract the debugger and. Using the Web Service from Code Microsoft Visual C NET. Hi i am on console application i want to footing the wsdl file without service reference or web reference This XML file does then appear to. Net objects before actual visual studio with odata web services? Visual studio c console application template Code Example. You can reference and to add web reference console application project? Add bleed and assembly references in C Interactive. Using client certificates in much part 5 working with client. Visual basic code example. C Copy using System using SystemIO Renders a report located on. And web reference to create drive location. Now welcome you want are doing HTTP requests in another console application in NET 4 then I. Azure SQL Azure-IoT c-sharp C Cloud Cloud Computing Cloud DataBase csharp CSS. In business Solution Explorer right-click on YourSolutionYourProjectReferences Select permanent Service Reference. Visual C using System using SystemData using MySqlDataMySqlClient. I have added a method CheckArgs which checks if the application is called with command line parameters. C Windows AzureWebSitesnet. The WSDL document actually tells a client application what consider the types. Comen-usdotnetcoreadditional-toolswcf-web-service-reference-guide I'm. NET Client C 11242017 7 minutes to read 11 In quality article by Mike Wasson and Rick Anderson.
    [Show full text]
  • Installation Manual for Oracle Application Server 10.1.3.3 on Unix for Agile E6.1
    Oracle® Agile Engineering Data Management Installation Manual for Oracle Application Server 10.1.3.3 on Unix for Agile e6.1 Part No. E13352-02 February 2009 Installation Manual for Oracle Application Server 10.1.3.3 on Unix for Agile e6.1 Copyright and Trademarks Copyright © 1995, 2009, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Console Command Line Shell Guide
    Red Hat Gluster Storage 3 Console Command Line Shell Guide A guide for installing and using the Command Line Shell for Red Hat Storage Console. Last Updated: 2017-10-18 Red Hat Gluster Storage 3 Console Command Line Shell Guide A guide for installing and using the Command Line Shell for Red Hat Storage Console. Pavithra Srinivasan Red Hat Engineering Content Services [email protected] Legal Notice Copyright © 2013-2014 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent.
    [Show full text]
  • Application Programming Interfaces
    ERserver zSeries Application Programming Interfaces SB10-7030-06 Level 06a, November 2004 ER s er ver zSeries Application Programming Interfaces SB10-7030-06 Level 06a, November 2004 Level 06a, November 2004 Note! Before using this information and the product it supports, be sure to read the general information under Appendix F, “Notices,” on page F-1. Seventh Edition (October 2004) ™ ® | This edition, SB10-7030-06, applies to zSeries Processors and S/390 Processors. | This edition replaces SB10-7030-05 and -05a. A technical change to the text or illustration is indicated by a vertical line to the left of the change. ™ There may be a newer version of this document in PDF format available on Resource Link . Go to http://www.ibm.com/servers/resourcelink and click on Library on the Navigation bar. A newer version is indicated by a lower-case, alphabetic letter following the form number suffix (for example: 00a, 00b, 01a, 01b). © Copyright International Business Machines Corporation 2000, 2004. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Level 06a, November 2004 Contents Safety and Environmental Notices . vii Laser Safety Information . vii Laser Compliance . vii Environmental Notices . vii Product Recycling and Disposal . vii Refrigeration . vii Battery Return Program . vii IBM Cryptographic Adapter Card Return Program . viii Cable Warning . viii Preface . .ix Message Event Notification . .x Load Command Support . .x Hardware Message Refresh Command Support . .x Hardware Message Event Data . .x Activation Profile Support . .x Hardware Message Delete Command Support . .x Reset Clear Command Support . .xi || Security Log Event Support .
    [Show full text]
  • Airconsole User Manual
    User Manual Version 2.5 1 Welcome to Airconsole ......................................................................................... 4 1.1 Airconsole Features ..................................................................................................................................... 4 1.2 Package Contents .......................................................................................................................................... 4 2 Quick Setup ........................................................................................................... 5 3 Hardware and Connectivity Overview .................................................................... 9 4 Airconsole Web Configuration ............................................................................... 9 4.1 Serial Settings .............................................................................................................................................. 11 4.1.1 Advanced Serial Settings......................................................................................................................... 12 4.2 LAN Settings ................................................................................................................................................. 13 4.2.1 Setup Page ..................................................................................................................................................... 14 4.2.2 Static IP Address ........................................................................................................................................
    [Show full text]
  • Advanced Management Console Installation and Configuration Guide
    Java Platform, Standard Edition Advanced Management Console Installation and Configuration Guide 2.20 F38329-01 January 2021 Java Platform, Standard Edition Advanced Management Console Installation and Configuration Guide, 2.20 F38329-01 Copyright © 2014, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer
    [Show full text]