Shulou(Shulou.com)06/02 Report--

This article mainly introduces the vs2010 prompt project has expired solutions, the article is very detailed, has a certain reference value, interested friends must read it!

What if vs2010 prompts that the project has expired?

Always prompt the solution that this project has expired when you start debugging

First of all, if the compilation fails in Visual Studio, then this prompt is normal.

Because this project has expired means that you have changed some files or project configuration or did not compile successfully last time, you need to recompile, otherwise debugging will make an error.

If you passed the compilation last time and press F5 to debug this prompt, there may be a problem.

If you have this problem every time, then this solution is right for you.

Of course, the solution is not to choose "do not display this dialog box again", this is just not displayed, but each debugging will compile once and then start.

What we want is to stop compiling and just start debugging.

First of all, this prompt indicates that visual studio found that some files were out of date, but no files were compiled at compile time, and even the output files were not regenerated. Don't you fool me.

Well, in fact, it is a trick to me, this is Visual studio's bug. This problem generally does not occur on Visual studio 2005, but it occurs on Visual studio 2010, and other versions are not clear.

Although it is bug, it can be solved.

The reason for this bug is that Visual studio 2010 thinks that the deleted file in the project is out of date, such as a header file in the project, the header file has been deleted, and Visual studio 2010 can not find the header file, it is considered to be expired, so every time debugging VS thinks that the project is expired and needs to be compiled first.

So why didn't you find any files compiled at compile time? the reason is that this header file is not used by any CPP or C files, so no files need to be recompiled at compile time.

The principle of Bug is understood, and the solution is to delete that header file in the VS project.

One stupid way is to click on the header files in VS to find the ones that can't be opened.

A smart way is to write a script to parse the project file and then verify that the file exists.

Another way is to look at it through DebugView.

Here is an example of this scheme.

1. Open the devenv.exe.config file (this file is in% ProgramFiles%\ Microsoft Visual Studio 10.0\ Common7\ IDE\ or% ProgramFiles (x86)%\ Microsoft Visual Studio 10.0\ Common7\ IDE)

two。 Add before this line

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.