C + + IDE enhancements in Visual Studio 2010

If support for the new C + + standard provides a solid foundation for the development of Visual C + +, her enhancements to the IDE will make her more radiant.

Many Visual C + + programmers love to eat tomatoes (visual Assist). Why? Because it can compensate for VC (Visual C + +). Although Visual C + + is very powerful in C + + libraries, compilers, MFC, and so on, her IDE has been criticized by C + + programmers. In particular, after entering Visual Studio 2000, the IDE for Visual C + + has not changed much, but it has become less efficient, making programmers have to eat more "tomatoes" and add some VC.

Microsoft is trying to create Visual Studio 2010 as a classic development tool like Visual Studio 6. So, in addition to supporting the latest C + + standards at the language level, Microsoft has also made a lot of effort in the IDE and the MFC libraries, among other things. Visual C + + not only improves the efficiency of the IDE, but also introduces a number of new features that are expected to enhance the programmer's development efficiency.

Visual C + + enhancements in Visual Studio 2010 mainly include the following:

Improved project system support

In previous versions of Visual Studio, MSBuild did not support the Visual C + + project well, and Microsoft instead offered an alternative, specialized solution: VCBuild. In Visual Studio 2010, Microsoft has finally improved this by integrating many of the unique features of VCBuild into MSBuild, and using MSBuild instead of vcbuild. Although VCBuild has many practical features for Visual C + + projects, the new MSBuild not only inherits these features, but also offers additional features that attract users to upgrade to this new build platform:

Diagnostics: MSBuild enhances its diagnostic capabilities to help users find and debug build errors more easily. For example, MSBuild can help you decide how to compile some source files in a particular order, because MSBuild can detect dependencies between those files.

Scalability: With MSBuild, users can build different solutions for specific platforms. Alternatively, you can use different versions of the compiler during the build process. Connectors and so on, making our solution more scalable.

Integration: We can add our Visual C + + project to an existing MSBuild environment. For example, we can integrate a new Visual C + + project into an existing MSBuild environment, although this MSBuild environment contains Visual C # and Visual Basic projects that use the. NET framework.

Multi-targeting has been an important feature of Visual Studio and has been widely promoted by Microsoft. Because it makes it possible to "encode once, run multiple platforms." This feature has brought great convenience to programmers and no longer has to be bothered by the chaotic platform of the target machine. However, in previous Visual Studio, the Multi-targeting attribute is supported only in managed languages and can be used for different. NET Framework versions. Now in Visual Studio 2010, with the application of MSBuild, the multi-targeting of native code is also possible.

In Visual Studio 2010, we have the option of using the Toolset for Visual Studio 2010 or the Toolset for Visual Studio 2008. When we don't want to upgrade to Visual Studio 2010 prematurely because of some compatibility or other reasons, we can benefit from the multi-targeting feature, select the Visual C + + libraries and compilers that use Visual Studio 2008, The IDE with Visual Studio 2010 is also used. This will achieve the "fish and bear cake". When we finally decide to upgrade to the library and compiler for visual Studio 2010, just make a simple setup in MSBuild or in the project properties. The following illustration shows the compilation records for the project under different toolset settings.

Multi-targeting: Target tool Set is V90

Multi-targeting: Target tool Set is V100