Visual C++.NET开发者指南

需积分: 0 192 浏览量更新于2024-08-01 收藏 9.16MB PDF 举报

"《Studio C++.NET Developer's Guide》是由John Paul Mueller编写的关于使用Visual C++.NET进行软件开发的专业指南。这本书由McGraw-Hill/Osborne出版，主要面向开发者，提供有关C++.NET Studio的深入知识和实践指导。书中可能涵盖了C++.NET的语法、类库、开发工具的使用、Windows应用程序开发、调试技巧等内容。在版权方面，本书受到2002年The McGraw-Hill Companies的版权保护，未经许可，任何部分不得以任何形式复制或分发，除非是为了在计算机系统中运行程序代码。但是，这并不禁止将程序列表输入、存储和执行在计算机系统中，只是禁止用于出版目的。该书的国际发行和翻译事宜可能需要联系McGraw-Hill/Osborne获取详细信息。此外，书中还提供了索引后的国际联系信息页面，以供需要的读者查询。书号为0-07-213262-0，配套CD的书号为0-07-213282-5，ISBN号为0-07-213281-7。出版社的高级副总裁和副主编是Brandon A. Nordin，编辑是Scott Rogers。作为一本开发者指南，本书的目标读者群体应该是有一定编程基础的C++程序员，想要学习或提升在.NET框架下使用C++进行开发的技能。通过阅读，读者可以掌握如何利用Visual C++.NET进行高效、高质量的软件开发，包括理解.NET框架的集成，以及如何利用Microsoft的开发工具进行项目管理、测试和部署。" 请注意，由于原始信息中并未提供具体内容的详细细节，以上分析基于对“Studio C++.NET Developer's Guide”这类图书的一般性理解和期望包含的主题。如果需要更具体的知识点，建议参考书籍的实际内容或提供更多详细信息。

DevEnv [<Solution File> | <Project File> | <Code File>] [<Switches>]

Microsoft designed DevEnv to work with large enterprise applications. As a result, you’ll find

a new term called the solution file. A solution file has a .SLN extension and contains all of

the information required to construct an enterprise-level application environment. A solution

consists of one or more projects. Each project defines the requirements for a single

application element, such as a component. As with previous versions of Visual C++, a

solution can contain just one project that may execute by itself outside of the normal

enterprise environment. Finally, you can also work with individual code files. As usual, if you

type DevEnv /? at the command line, you’ll see a list of available switches. Table 1-1 shows

the command line switches and their meanings.

Table 1-1: DevEnv Command Line Switches

Switch Description

/? Displays help for the DevEnv program. This includes usage

instructions and a list of command line switches. It doesn't include full

information on how to use the switch. For example, it doesn't say

which switches you need to use together or the arguments you must

supply with the switch.

/build Builds a solution; has the same effect as using the Build | Build

command within the IDE. You must provide a solution filename and a

configuration name. The valid configuration names depend on the

type of project. For example, you might use “Debug” as the

configuration name. You may optionally use the /project and

/projconfig switches with this switch.

/clean Removes the intermediary and output directories. You must provide a

solution filename and a configuration name. The valid configuration

names depend on the type of project. For example, you might use

“Debug” as the configuration name. You may optionally use the

/project and /projconfig switches with this switch.

/command Executes a command after the Visual Studio IDE starts. These

commands must fall within the range of predefined IDE commands or

custom macros you've created.

/debugexe Launches the debugger, loads an executable, and applies optional

switches to modify executable behavior. You must provide the name

of an executable to debug. The Visual Studio IDE ignores any

switches provided after this switch and applies them to the

executable you want to debug.

/deploy Deploys an application after a rebuild. You must provide a solution

filename and a configuration name. The valid configuration names

depend on the type of project. For example, you might use “Debug”

as the configuration name. You may optionally use the /project and

/projconfig switches with this switch.

/fn Use the specified font within the Visual Studio IDE.

/fs Use the specified font size within the Visual Studio IDE. The font size

is specified in points.

/LCID or /l Loads resource strings in the specified locale within the Visual Studio

IDE. You must provide a valid locale identifier number. For example,

specifying 1033 would load the English language resource strings.

Table 1-1: DevEnv Command Line Switches

Switch Description

/mdi Use the multiple document interface (MDI). This is similar to the

interface used by Visual C++ 6 (with obvious differences). For

example, the layout of the display still reflects the new Visual

Studio.NET view of the world. You’ll also get all of the enhancements

that Visual Studio.NET provides.

/mditabs Use tabbed MDI. This is the default interface used by Visual Studio

when you set it up.

/nologo Starts the Visual Studio IDE without displaying the copyright splash

screen.

/noVSIP Disables the Visual Studio Integration Program (VSIP) developer’s

license key for VSIP testing. VSIP allows developers to add new

capabilities to Visual Studio like new project types, a customized

editor, or advanced debugging capabilities.

/out Specifies an output file for errors during a command line compile.

You must provide the name of an output file. Visual Studio will

automatically clear the file if it exists, so that you see only the errors

from the current build.

/project Builds a project instead of a solution. You must provide a solution

filename, project name, and a configuration name. The valid

configuration names depend on the type of project. For example, you

might use “Debug” as the configuration name. You may optionally

use the /build, /rebuild, /deploy, and /clean switches with this switch,

but must select one of them to perform a task. This switch also works

with the /projectconfig switch.

/projectconfig Specifies the project configuration for the project specified by the

/project switch. You must provide a solution filename, project name,

project configuration, and a configuration name. The valid

configuration and project configuration names depend on the type of

project. For example, you might use “Debug” as the configuration or

project configuration name. You may optionally use the /build,

/rebuild, /deploy, and /clean switches with this switch, but must select

one of them to perform a task.

/rebuild Performs a combination of the /clean and /build switch tasks. You

must provide a solution filename and a configuration name. The valid

configuration names depend on the type of project. For example, you

might use “Debug” as the configuration name. You may optionally

use the /project and /projconfig switches with this switch.

/resetskippkgs Allows the IDE to load VsPackages that were previously marked as

having failures.

/run or /r Compiles and runs the specified solution or project configuration. You

must specify a solution or project name. The IDE will display any

error or change message boxes before it terminates the application.

/runexit Compiles and runs the specified solution or project configuration. You

must specify a solution or project name. The IDE terminates the

application without displaying any message boxes or allowing you to

Table 1-1: DevEnv Command Line Switches

Switch Description

save changes.

/safemode Loads only the default environment and services. This allows you to

maximize the stability of the development environment.

/sdi Use the single document interface (SDI). This is similar to the

interface used by Visual Basic 6 (with obvious differences).

One of the popular alternative IDE displays is the Single Document Interface (SDI) display.

Normally, Visual Studio .NET assumes you want to use the Multiple Document Interface with

tabs (/mditabs) display. You can access the SDI display by adding the /sdi switch. Figure 1-2

shows the same application shown before (Figure 1-1), this time loaded into the SDI IDE

display. Notice that you can enlarge any of the windows to consume the entire display area.

While this makes it easier to concentrate on a particular area (such as when you’re coding),

some developers feel it makes the IDE less accessible during the design process. Of course,

the choice of display is a personal matter, and you’ll need to decide which you like best.

Figure 1-2: The SDI style IDE is popular with many developers because it presents a

simple appearance.

Enhanced Debugging

Previous versions of Visual C++ relied on an entirely different IDE than the one used for

Visual Studio.NET. Therefore, one obvious debugging change is the environment you’ll use

to trace through your applications. Visual C++ .NET combines the flavor of both Visual C++

6.0 and Visual Basic 6.0. It allows you to use a single debugging environment for all of the

languages within your application. Of course, this debugging environment includes support

for all new features of Visual C++, including managed extensions. The use of an integrated

debugging environment means that debugging is less time-consuming and more convenient.

You’ll find that the debugger is also more robust. One of the more interesting features is the

ability to attach the debugger to a running application on a local or a remote machine. This

feature allows you to perform tasks like checking a user’s application while it’s still in an error

state. Instead of trying to re-create an error condition, you can attach the debugger to the

existing application and see the problem in a real world situation. Figure 1-3 shows the

Processes dialog box you use to attach it to another process. You access it using the Debug

| Processes command. Notice that the dialog displays all of the current processes for the

workstation listed in the Machine field. You can choose a new machine and even select the

protocol used to communicate with it.

Figure 1-3: The Processes dialog box allows you to attach the debugger to an

application that’s already running on a local or remote machine.

The ability to attach to a running application also comes into play with multiple- application

debugging. You can set this feature up by starting multiple applications within the IDE or by

attaching to existing applications. This feature is going to be very useful in a distributed

application environment, because it allows you to see how an application reacts when

multiple versions are running. For example, you could use this feature to verify that the

database locking mechanism for an application works before you even place the application

components on a test server.

The new version of the debugger also allows you to perform more checks on your

application. For example, you can perform runtime error checks. These checks help you look

for problems such as stack pointer errors, local array overruns, stack corruption, uninitialized

local variables, and data loss due to type casts. You’ll also find that the new checks help you

find buffer overrun problems—a difficult error to locate when it occurs during a call to another

DLL.

HTML Editing Environment

Visual Studio 6 included a language element called Visual InterDev. This product was

supposed to make it easier to create Web sites. However, many developers complained that

the tool relied too heavily on FrontPage and that it didn’t provide enough in the way of

generic editing features. One of the first things that many developers will notice about Visual

Studio.NET is that Visual InterDev is missing—at least as a separate language.

Visual InterDev is part of Visual Studio, and you can access the full power it provides from

within Visual C++. (You won’t see Visual InterDev mentioned because Microsoft has fully

integrated it with the rest of Visual Studio as part of their Web-based application

development emphasis.) What this means is that you, as a Visual C++ developer, will be

able to include Web elements within your application with greater ease than ever before. In

fact, Microsoft provides the following items for you to use within your applications.

§ HTML Page

§ ASP Page

§ ATL Web Service

§ MC++ Web Service

§ HTML Frameset Page

§ XML File

§ Stylesheet

Many of these items will convert to other items that you may need for a particular application.

For example, the XML File item is useful for various other file types, such as those used by

the Simple Object Access Protocol (SOAP). I used it to create a Web Service Description

Language (WSDL) file recently as well as an XML Data Reduced (XDR) file. Both of these

file types have uses within SOAP applications.

Task List

One of the new additions for Visual C++ .NET is the Task List. No longer will you have to

scout around for the little reminders left by wizards when you create an application. In

addition, you’ll be able to leave yourself “to do” notes and find them later. This is also an

excellent addition for team projects—project members can leave notes for each other, and

the team leader can make assignments directly in the source code.

Dynamic Help

Developers are under ever-increasing pressure to deliver applications quickly. Meanwhile,

development environments become more complex, forcing the developer to spend more

time learning new techniques. In short, a developer today has to know where to find specific

information in the shortest time possible. That’s one of the reasons that Dynamic Help is so

exciting. It automatically displays help information based on the current cursor position. Click

a method within your application and you’ll automatically see the appropriate help displayed

in the Dynamic Help window.

How good is Dynamic Help? Dynamic Help is better than anything else that I’ve seen in a

development environment so far. An experienced developer will find that help automatically

becomes available about 90 percent of the time. So, although you can’t throw out your

Microsoft Developer Network (MSDN) subscription, you’ll spend a lot less time looking for

the information you need. Obviously, this feature will help novice programmers more than

those with a lot of experience, but I think that everyone will benefit from this new feature.

Command Window

Some people really hate using the mouse. They want to use the keyboard—end of

discussion. Until now, most of us have had to put up with the mouse because it provides

functionality that you can’t otherwise obtain within the IDE. The Command Window feature

changes all of this. Now you can type in a command, press ENTER, and watch its execution

just as if you had used mouse clicks to perform the task. For example, typing Open

MyProg.CPP in the Command Windows and pressing ENTER will open that file—just as if

you had used the File | Open command with the mouse.

After trying this feature for a while, I can honestly say that it increases productivity. The

caveat is that using commands won’t replace the mouse in all situations. Sure, you can type

commands to perform every task, but the mouse is more efficient in some situations. On the

other hand, the Command Window is definitely more efficient in other situations. Even

though I’ll use the standard menu commands throughout the book, you can be sure that I’m

using the Command Window to perform certain tasks, such as opening files, while writing

this book. The Command Window fills a gap in IDE functionality.

剩余522页未读，继续阅读

seacsd

粉丝: 10
资源: 506

Visual C++.NET开发者指南

Visual C++.NET 开发手册

Visual C++.NET Developers Guide

McGraw Hill - Visual C++ .NET Developers Guide(1).pdf

Visual C++.NET开发者指南

Wireshark Developer’s Guide.pdf

Wireshark Developer’s Guide For Wireshark 2.1

Wireshark Developer's Guide For Wireshark 2.1

VeloView_Developer_Guide.pdf

Microsoft visual c++ 6.0 programmer's Guide 程序员指南

Windows_7_Developer_Guide_v1.5

最新资源