That "File XXX not found in current source file's directory or in build system paths"

I am so sick and tired of this bug. I right click on a file that the compiler knows how to find, then select "Open Document XXX" and then I receive "File XXX not found in current source file's directory or in build system paths". Was this ever fixed in 2005 I have been (im)patiently waiting and waiting for a new service pack to address some of the major flaws in VS.NET 2003. Is one ever coming out Was this bug finally fixed

Microsoft, you have a serious problem that spans multiple products that relates to making it easy for the user to find things. You'll hide paths by needlessly inserting an ellipse into the path thus making a path field totally useless. The "Open document" feature in VS.NET barely works, the "Find in Documents" feature (though vastly improved over the previous version of VS) is still poor, searching for emails in Outlook is a mess, and sometimes the search in files feature of Windows Explorer will often breeze right over files that it should have caught.

I know much thought has been going into creating totally new ways to store data, but damn it! The existing storage method would be just fine if you'd make a few minor tweaks to your existing tools to make them simple and reliable.

JEEZE!!!!!!!

Now back to painstakingly searching manually for my file that Visual Studio failed to find. Guess I'll have to go to Windows Explorer, find the file, then drag it to Visual Studio. Gee, thanks for making this software a breeze to use.

Answer this question

That "File XXX not found in current source file's directory or in build system paths"

JRandJame

Please report this issue on http://msdn.microsoft.com/productfeedback. It's the best way to directly report bugs to the team. That way, you can also be kept in the loop on when it's fixed.

Thanks,
Kelly7018
At least one of the problems is when a space is on the path.

(I'm sure you know how to reproduce it by now, but just in case)

Let's say we have following structure:

C:\sandbox\source\code.cpp

C:\sandbox\folder with space\header.h

C:\sandbox\solution.sln

C:\sandbox\project.vcproj

code.cpp includes header.h and project have "Additional Include Drectories" set to "C:\sandbox\folder with space".

So, if we click on #include "header.h" and do Open Document "header.h", it will complain:

File 'header.h' not found... bla-bla-bla

Build system path: "C:\sandbox\folder with space";
mediterian
Thanks for the feedback and I'm looking forward to our eventual move to 2005 for that feature. Sorry about the previous outburst nature but I just got fired up the last time the bug occurred to me and ran here to vent!
CKa

We have improved this feature in VS2005. I don't know if your particular source base will work flawlessly. I'm sure you can still write code that would confuse our IDE parser.

I totally agree with you that we should know it since the compiler knows it. Unfortunately, we'll only be 100% correct when we share the exact same compiler data with the IDE (which is currently not the case and is both non-trivial and expensive to do). You should still find a good improvement over VS2003 in that respect, though.

As for Service Packs, please see: http://msdn.microsoft.com/vstudio/support/servicing.

Thanks.
captainahab
Done. I made a comment in Steve's original bug (which is closed as Not Reproduced).

I hope it will be reopened eventually :).
Flashx

I understand and share your frustration. Bugs of this nature irritate me as well :)

Thanks.
That "File XXX not found in current source file's directory or in build system paths"

Answer this question