I believe that many Visual C ++ programmers who use Visual Studio as development tools will fall in love with Visual C ++ 6.0. Visual C ++ 6.0 works with Visual Assist as an auxiliary tool, making it the best choice for C ++ programmers to develop tools.
With the upgrade of Visual Studio, IDE introduces some new features, but it makes the entire IDE very bloated and inefficient. Currently, Visual Studio 2010 has done a lot of work on IDE efficiency to improve our development efficiency:
Header file editing
In Visual Studio, If we edit a header file referenced by multiple source files, Visual Studio will have to interrupt your work because it takes a long time to reprocess the entire project. Now, in the New Visual Studio 2010, when we edit the header file, we can continue to work, while Visual Studio will process the new header file in the background, at the same time, the intelliisense will be updated soon to reflect the changes to the correct file.
Change project configuration
Similar to editing of the first file, in Visual Studio, when we change the configuration of the project, Visual Studio interrupts our work to handle the changes in the project configuration. For example, after we switch the current project configuration from Debug to Release, Visual Studio takes a long time to process the changes in the project configuration.
However, during this period, Visual Studio is like a dead object. We can't do anything but wait. (I once reluctantly regard it as a user-friendly design of Visual Studio, and deliberately let our long-sitting programmers get up and walk while waiting, so they can relax .) In the New Visual Studio 2010, after modifying the project configuration, we can continue working without waiting.
Physical Distribution of configuration items
Is your project very large and contains many source files? In Visual Studio, when it processes all files in the project, it will appear very slow. To solve this file, we often have to split a project into multiple projects, so that the source files in each project will be much less.
Visual Studio processes fewer files each time, and it looks faster. In the New Visual Studio, it improves the efficiency of processing source files. Even if your project has many source files, When Visual Studio processes these files, you can still maintain the activity without the "false" phenomenon. This feature allows us to reconfigure the source files originally needed to be distributed across multiple projects as needed to make the physical distribution of the project more reasonable.
More intelligent intelliisense
As the most complex programming language, C ++ has always been a difficulty in Visual Studio. In the past, in Visual Studio, C ++'s intelliisense was based on the compiler and can understand complex C ++ code. However, for some advanced Visual C ++ 6.0.
Especially for macro-related content, intelliisense is powerless. In the New Visual Studio, the improved intelliisense is more intelligent and can understand almost any complex form of C ++ code. With the new intelliisense, it is estimated that the Visual Assist favored by many programmers will be unpopular.
Enhanced MFC
Although we are all saying that MFC is outdated, there are still a lot of MFC running in the world, and there are also a lot of MFC-based programs under development. We can say that with the launch of new frameworks such as. NET Framework, MFC is no longer the only choice.
However, with the launch of Visual C ++ Feature Pack, the ability of MFC in interface development has been greatly enhanced, and MFC is also keeping pace with the times, far from obsolete. In Visual Studio 2010, apart from the many features released with Visual C ++ Feature Pack, MFC has brought two important features:
Task dialog box CTaskDialog
To improve user experience, Microsoft uses the Task Dialog Box (Task Dialog) in Vista to replace the widely used Message Box ). Compared with message boxes, the task dialog box not only displays messages to users, but also custom buttons, command line options, and richer auxiliary information.
The new CTaskDialog class provides many simple and practical functions that can be easily used by programmers. The task dialog box is used to improve the user experience of the application, make the UI style of your application consistent with that of the Vista system. The following short code creates a simple task dialog box to ask the user's attitude towards the task dialog box.
Restart Manager Support
In the new Vista Studio 2010, the MFC program starts to support Restart Manager ). The restart manager is an important new feature introduced by Vista. It can protect users' unsaved document data when the program crashes unexpectedly.
- Seek the mysteries of Visual C ++ 6.0
- A comprehensive analysis of the C ++ Language
- C ++ standard library learning Summary
- Major difficulties in splitting the C ++ standard library
- Is it true that the C ++ template is missing?
When our program unexpectedly crashes for various reasons, the restart manager can restart the application and allow the user to choose whether to restore unsaved data. The restart manager can effectively reduce the risk of data loss and greatly improve the program's anti-risk capability. In Visual C ++ 6.0, we can simply add several lines of code to the program initialization so that our application has the function of restarting the manager.
Release and deployment of Visual C ++ programs
The New Visual Studio 2010 changes the publishing method of applications dependent on C ++ code. Applications dependent on the Visual C ++ library no longer need Fusion (WinSxS) Manifest, which means that when we deploy the application to a local folder, there will be no more small Manifest.
You only need to copy the mfc100u. dll and msvcr100.dll dll files of the MFC and C ++ runtime libraries to the Release folder. In addition, Visual Studio 2010 also supports various previous deployment mechanisms, such as merging modules (. msm) and VCRedist.
These old methods will install the Visual C ++ library in the System32 directory. In short, Visual C ++ 6.0 is easier to publish and deploy. We will introduce the specific release process in more detail in the following articles. The support for new C ++ standards and improvements in IDE are like the neighborhood of Visual C ++. Who is fighting!