1#LPPQRRS=/2!89Visual C++ 2.0 Q&A - April 13March 31, 1994Page
Microsoft Corporation
Microsoft Visual C++ 2.0
Most Commonly Asked Questions

April 13March 31, 1994
When will Visual C++ 2.0 be available, and what will the price be?
Visual C++ 2.0 will be available summer 1994. We have not made the pricing available, but our goal is to keep it competitive with the current Visual C++ pricing.
Whats new in Visual C++ 2.0?
Visual C++ 2.0 is designed to help move developers quickly to Win32 OLE 2.0 which is the basis of the next generation of Microsoft Windows operating systems, code names Daytona, Chicago and Cairo. Visual C++ contains numerous enhancements including the Microsoft Foundation Classes 3.0, a new more tightly integrated development environment, a faster and better optimizing 32-bit compiler with support for templates and exceptions, and a new incremental linker.
Whats in the Microsoft Foundation Classes 3.0?
The Microsoft Foundation Class Library (MFC) 3.0 supports both the Win32 application programming interface, OLE 2.0 and the ODBC database technology which are key components of upcoming operating systems from Microsoft. MFC 3.0, to be released along with Visual C++ 2.0, is a framework designed for writing C++ applications for Windows. MFC 3.0 is the 32-bit version of MFC 2.5, recently introduced with Visual C++ 1.5. MFC is central to simplifying OLE 2.0 development because it provides new classes that allow developers to quickly create OLE 2.0 applications with full visual editing and OLE automation capabilities. MFC 3.0 also includes database classes that facilitate building C++ applications through ODBC (open database connectivity)..

The MFC 3.0 framework also gives current developers for Visual C++ the ability to migrate completely from 16- to 32-bit development, and enables rapid porting of MFC 2.0 or MFC 2.5 features to 32 bits without code changes.
How can I get a beta of Visual C++ 2.0?
If you are interested in joining our Visual C++ beta program please submit a letter expressing your interest to the "Visual C++ Coordinator" at Microsoft. The letter should contain:
- System configuration including operating systems, networks, and memory-resident software.
- Development tools that you are currently using/
- Types of applications being developed.
- Reasons why you want to be a beta tester, including experience you have using the product and any previous experience you have in doing beta testing.
The letter should be written on the individual's business letterhead and addressed to:
Microsoft CorporationAttn: Visual C++ 2.0 Beta Test CoordinatorOne Microsoft WayRedmond, WA 98052-6399
What about 16 bit development, will Visual C++ 2.0 also target 16 bit?
For people that need to develop 16 bit Windows-based applications today, we offer Visual C++ 1.5, the shortest path to creating reusable OLE components and high performance database applications for Windows 3.1.
What build tools performance gains will I see with the new Visual C++ 2.0?
Visual C++ 2.0 introduces a new incremental linker that significantly reduces the time spent linking by only linking code that has changed since the last build cycle. Thus if only one source file has been modified since the last build, only the object code and debugging information affected by the change is relinked into the executable, dramatically speeding up the build process. Thus rebuild times are dependent on the size of change, not the size of the application.
What is your plan for 16 bit Visual C++?
Since developers will be moving from 16 bit to 32 bits with the release of Chicago, we are concentrating our efforts on 32 bit development tools and thus most of our innovations will be available for 32 bits only. We will continue to maintain our 16 bit Visual C++ 1.5 and make it available so that our customers can maintain their 16 bit code bases.
Will Visual C++ 2.0 and MFC also include support for Win32s?
Yes. Visual C++ 2.0 will include tools to allow developers to create applications that target the Win32s application programming interface, including the new OLE 2.0 support in Win32s.
Im going to eventually target Chicago. Since I cant get Visual C++ 2.0 now, what should I use?
If you are/can still targeting 16 bits, we recommend you use Visual C++ 1.5 so you can get a headstart creating OLE 2.0 applications with the Microsoft Foundation Classes. If you need to target Win32 today, we also offer Visual C++ 32-bit Edition. In both cases, all the code you write with MFC will be fully portable to Visual C++ 2.0 and Chicago.
I just heard about OLE Custom Controls, will Visual C++ 2.0 support them?
Visual C++ 1.5 and Visual C++ 2.0 will allow you to build OLE controls with the use of the Control Development Kit. Future versions of Visual C++ will also include design-time tools to make it even easier to use the new OLE controls in your applications.
Will Visual C++ host on Windows 3.1?
No. Visual C++ 2.0 is a Win32-based application. It requires Windows NT or Chicago to run.
What is the Visual C++ Cross Development Edition for Macintosh (VCMac)?
The Visual C++ Cross-Development Edition for Macintosh enables Windows developers to leverage their existing Win32 source code and tools expertise in porting applications from Windows to the Macintosh. This Macintosh edition of Visual C++ is an add-on to Visual C++ 2.0. It contains all of the tools needed to build high performance, native Macintosh-based applications. In addition, the toolset includes a portability library that maps Win32 API calls to the equivalent Macintosh Toolbox functionality. This static linked library enables a single set of source code, written to either MFC or directly to the Win32 API, to target both Windows and the Macintosh. The ported application has the native Macintosh look and feel.
Is this product part of the Visual C++ 2.0 for Windows product?
The Visual C++ Cross-Development Edition will be sold as an add-on to Visual C++ 2.0. The add-on extends the Visual C++ environment to include additional menu items, dialogs and tools needed for building and debugging Macintosh executables from the Windows NT host machine. Users have access to all of the powerful features of Visual C++ 2.0 for creating Macintosh-based applications.
Whats the availability and pricing for the Cross Development Edition?
The Cross Development Edition will ship in Summer 1994. Pricing has not been finalized.
Is there a Macintosh version of MFC?
The Visual C++ Cross-Development Edition includes a Macintosh edition of of the Microsoft Foundation Classes, version 3.0. Programming to MFC is the way to achieve the maximum percentage of common code between the Windows and Macintosh versions of an application.
What do I need to do to my Windows source code before I can port it using this product?
The first step in preparing to use this toolset is to move your sources to the Win32 API. As the Mac is a 32-bit platform, the portability libraries are based on the Win32 API. Programming to Win32 enables multiplatform targeting of Windows 3.1 (through Win32s), Windows NT, Chicago and now System 7.x.
What about portability to other platforms?
Our strategy is to support developers targeting the Windows family of operating systems and the Macintosh while allowing other tools vendors to provide solutions for other platforms. There are currently several ISVs supplying portability tools for migrating code from Windows to UNIXto UnixUNIX. For example, both Bristol Technology and Mainsoft offer tools that enable applications written to MFC or the Windows API to be ported to UnixUNIX/Motif.
When will Visual C++ 2.0 be available on MIPS?
The MIPS version of Visual C++ 2.0 will be available in summer 1994. It is hosted on MIPS and builds native MIPS applications. The MIPS version uses the same Visual C++ development environment, C++ language implementation and MFC 3.0 to let you leverage your existing source code and tools expertise when developing multiplatform applications. We are currently working with the other NT OEMs to port Visual C++ to their RISC hardware platforms.




Information in this document represents the current view of Microsoft Corporation on the issue discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED IN THIS DOCUMENT.

1994 Microsoft Corporation. All rights reserved. Printed in the United States of America.

Microsoft, Windows, Windows NT, Win32, Win32s, ODBC, and Visual C++ are either registered trademarks or trademarks of Microsoft Corporation in the United States of America and other countries.
wrnjgc_c[W&SO'K @'w!s
o@kgac<_f[WSO"K"wsokgQc_u[W:SOKw
sfokgc_#[\\YYYYc&'!!7k4


@afy { } s"u"""##=/2!;(u"""##2?#(#u"""##2?n
D0SymbolTimes New Roman ArialTimesu"""##