External headers not shown in list about workingfileslist HOT 2 CLOSED

If I understand correctly, what you’re describing doesn’t sound like it was intentionally by design as such.

Working Files List uses the Visual Studio automation object to both find out about any files that are open, and to manipulate (e.g. open in the editor/close) them. The file groups are the names of the parent projects, as discovered though the automation object; if a file does not belong to any project, it will belong to Miscellaneous Files. [For example, if you open a text file in Visual Studio from Windows Explorer, it should open in a new instance of Visual Studio under the group Miscellaneous Files].

Occasionally there are some files that Working Files List cannot manipulate (e.g. maybe the file was deleted externally from Visual Studio while the solution was still open). In order to avoid having orphaned entries in Working Files List, it removes any entries that might be problematic.

This does seem different from issue #14, as from what I understand iostream does not reappear. It seems more like, for whatever reason, Working Files List cannot find/access iostream. I haven’t worked much with C++ lately so sorry if the answers to these questions are obvious; could it be that iostream is in a system folder (e.g. Program Files) that Visual Studio doesn’t have access to [maybe try running Visual Studio as an administrator]? Alternatively, could it be that iostream doesn’t exist as a file on disk [e.g. it might be a file within memory, extracted from a .dll library]?

from workingfileslist.

Closing issue after eight days of inactivity; will reopen if necessary.

from workingfileslist.