Reorganized source, c1xx C1083

Question

I just reorganized my directory structure by moving a folder of source files, called stdsc, into a new folder cog, creating the path cog/stdsc. Visual Studio (2010) crashed after finishing moving the files, and after restarting it, I now get c1xx : fatal error C1083: Cannot open source file: 'stdsc\stdsc.cpp': No such file or directory for every .cpp file that used to reside in stdsc/, but now lies in cog/stdsc/.

I've tried doing "Clean project" and "Rescan solution", but still it tries to compile these files in their old location. The acual files in the new location are found and compiled, but still the error persists. How can I remove these references?

Answer 1

I noticed that the .vcxproj file was just XML, so I opened it and removed the lines which referred to the old locations. Seems to have worked without nasty side effects. I was a bit sceptical to doing this though, so if there are other solutions, I'd love to hear them.

Answer 2

I just had this problem too, in Visual Studio 2010.

The "Solution Explorer" has two modes, "Show All Files" and the "filter mode" or whatever it's called.
I usually work in all files mode, because there you see the files as they actually exist in the file system.

When switching back to the filter mode there were two references to the problem file. One of them was marked red and referred to the previous path. Right click it and "exclude from project" solved the problem for me.

Answer 3

Using Visual Studio 2012, I encountered this issue while changing the directory of some files in my solution. I found that some of my source files, which were seemingly unrelated to what I was changing, weren't being resolved properly. When I clicked on them in the Solution Explorer, they wouldn't open, again because VS was looking for them at the wrong path. I removed the files from my solution and drag-and-dropped them back into the solution from Windows Explorer. This fixed the issue. Based on the error message, it looked like the error was somehow related to the fact that VS was using a relative path to identify the source files.