"Compile | build | debug" In the Visual Studio 2013 environment operating VC6/VC7/VC8 and other low-version platform projects

Modernization of the development environment, Microsoft has been introduced to upgrade, we are in a technological environment in the changing pace of change, but in China, the majority of people tired to catch up with the times, while adhering to their own knowledge of the tight bar of the book. The mastery of technical tools is not what they want, and everyone wants to use tools to achieve their goals. Therefore, for a period of time, who kicked out of the work, who won the opportunity to absorb a large number of people to drive the growth of their cause. But if only one time's work is cast out, and from then on it will not absorb the fresh technological atmosphere from the outside, it may end up one day.

From VC6 to VC2008, then to 2010, 2013, to now is 2015, not to mention the integration of some excellent features in the environment is constantly sharp, making development work more and more comfortable, and Microsoft is constantly in the follow-up technical language standards, C++14 has come out, the standard type system gradually grow up. Still chewing on some of the lower-level details? The new standard has already been structured to enrich the complete concept of the system, and provide a friendly interface, the use of development work more and more close to a variety of splicing, assembly work.

Aside from pointing too much, fortunately did not forget the matter. We will use the visual Studio 2013 version of the environment, how to operate the lower version of the target generation and debugging to expand the content bar.

Dependent environment:

Visual Studio 2010

Daffodil (Platform toolset content expansion based on 2010 environment)

Visual Studio 2013 (This is my desired work environment, with daffodil expanded platform options to complete the target platform selection we need)

Visual c++6.0 or the corresponding desired platform version

Problems that may arise

Because the daffodil tool itself is based on a 2010 environment extension, it is very smooth to complete the compilation chain and debug directly in the Visual Studio 2010 environment.

Unfortunately, I prefer to use 2013 of the environment, the process of generating goals is smooth, no situation occurs.

But in the breakpoint debugging process, found that the breakpoint can not be hit always prompt, the target does not contain debugging information or find debugging information file and can not load symbols. This is simply a big headache, the purpose of the use of integrated environment is to facilitate the integration of the process to bring convenience, compile, link birth, commissioning, the links are very seamless. And if it can't be debugged, it's not a night to go back to liberation.

Keep trying, think is the project attribute some setup problem, the result is always not satisfactory, cannot not generate debugging information, is why do not load these symbols.

The final question found is that the Visual Studio 2013 menu commands >> Debug | option found, edit and continue setting, tick the selection machine related options, sure enough breakpoint hit, happy!

From what we see there is a striking exclamation mark warning. It can only be considered that the VC6 version is really too low-level and does not involve these advanced debugging features.

"Compile | build | debug" In the Visual Studio 2013 environment operating VC6/VC7/VC8 and other low-version platform projects