Visual studio thinks my project is up-to-date - c++

So, I have a template function in my C++ header files, and when I make changes to it, Visual Studio 2013 still thinks that the project is up-to-date. So when i run my project, it runs like I didn't make any changes.
I can replicate this situation with any header file and template function, and only way to resolve it seems to be rebuilding. Is this just a bug in Visual Studio or do I have some settings wrong?

Related

Visual studio 2015 not compile changes c++

from some time visual c++ compiler not compiling my code, I tried to do things that are there: Visual Studio 2013 C++ not compiling changes
Cleaning soultion works in my case, but after compilation i must do it again and so always. I saw also Build solution options and build configuration and there are OK. I moved project, delete execute file but it also not helped me.
What I can do to fix it? :(

Visual studio does not detect changes in header files

I have recently installed Visual Studio 2013 Update 2 and I realized changing the header files does not trigger a build. I have to "touch" the corresponding ".cpp" file, or rebuild the whole project so the changes in ".h" file are considered. I did not have this problem before in Visual studio 2013 Ultimate. I tried disabling precompiled headers since I am not using it, but the problem still exists. I can clean and rebuild every time, but it is very time-consuming since the project is relatively large.

How to move a project from Visual Studio 2005 to Visual Studio 2012

I want to move my C++ project to Visual Studio 2012; I solved problems and can build and create the exe. But an error, msvcp80d.dll missing happens. I think that's a Visual Studio 2005 dll so I want to remove the dependency on that and get past the error. How can I do that?
Fastest way is to search your intermediate build folder for string msvcp80d.dll to see which file picks it up. If all, then look in your .vcxproj file and the .props files it imports.
If it's not found at all then you have an indirect tie, use depends.exe on your executable to see which other dll depends on this one. (You may do it right at start.)

use msbuild to compile a vcxproj created by vs2010 on a computer without vs

I have created a large Visual C++ 10.0 project which builds nicely within the visual studio ide as well as within the "special" Visual Studio Command Prompt using msbuild with a vcxproj file.
However this project needs to be compiled by computers that do not have the vs ide, but only have the msbuild tool and the vc++ 10.0 runtime files.
The problem is that the vcxproj (created by the vs ide) file contains references to files such as Microsoft.Cpp.Default.props and Microsoft.Cpp.targets which clearly won't be available in a computer without visual studio.
Since all the compile and link command line options are available and fixed (no changes will be necessary), how is it possible to create a new vcxproj file to implement the compiling and linking of the project using these options?
I was finally able to make some tests on a "clean" computer. These are the results:
First, I installed .NET Framework 4.0 from http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718. Along with it, MSBuild 4.0 was also installed automatically. When I tried to compile I got the following error:
error MSB4019: The imported project "H:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
which means that extra files are needed to compile the vcxproj and these files were missing. Note that simple project files written by hand (and not by the VS IDE) are expected to compile without problems since they contain no references to theses files (I did not test it for certain).
Next, I installed Windows SDK 7.1 from http://www.microsoft.com/download/en/details.aspx?id=8442. The error about missing files disappeared, but I got a new one. This new error (along with the way I overcomed it) is described in http://www.damirscorner.com/CommentView,guid,9121bd6b-876c-4051-8487-de1b95a7e919.aspx.
Doing the above successfully allowed me build my vcxproj file on a computer without vs2010.
I think that the files that you mention are not part of Visual Studio. They are part of MSbuild.

VS 2010 intellisense not working for upconverted project

We have a very big C++ solution with several projects for which intellisense works perfectly in Visual Studio 2008, but not at all in Visual Studio 2010 (not even for structs defined in the same file where they are used). I've verified that intellisense does work in VS 2010 for other projects on my machine. I've tried importing one of the problematic projects from a brand-new solution with no success. Re-building the project files from scratch seems promising, but it would require days of work to follow that path, with no guarantee of success at the end. Any alternative suggestions are welcome. The actual error message I get is:
"Intellisense: 'No additional information available'(See 'Troubleshooting IntelliSense in C++ Projects' for further help.)
I've tried that, but there's basically only one suggestion on the MSDN webpage, to make sure "stdafx.h" on the include path, but we're not using precompiled headers and don't include it from anywhere, so I'm pretty sure that's not the problem.
Have you deleted all of the generated database (.ncb and .sdf) files? Corrupted database files is the most likely cause of Visual Studio failing to display IntelliSense.
Intellisense was not included as a component of Visual Studio 2010 for C++/CLI. Unfortunately, it seems they are not going to support it soon either. This is an incredible detriment, as i find myself having to open VS2005 on occasion to simply find an object member.
Here is Microsoft's release on the subject:
http://blogs.msdn.com/b/vcblog/archive/2011/03/03/10136696.aspx