See TODO even if file is not open in editor

[Karsten Schramm]

Hi,

is there a way to see all TODOs in a project/solution even if the files
are not open in the editor frame?

It's kindo of user-unfriendly to open all code files in a solution just
to find all TODOs.

Thx
Karsten

 

[Peter Duniho]

is there a way to see all TODOs in a project/solution even if the files
are not open in the editor frame?

It's kindo of user-unfriendly to open all code files in a solution just
to find all TODOs.

I'm not sure what you mean. The "Find In Files" command in Visual Studio
doesn't open the files. It just displays the matching lines in each file in
the results window.

If that's not to your liking, perhaps you'd prefer using the "findstr"
command prompt command, or one of the many grep-like command-line utilities
that are available.

I don't understand why you think you need to open all code files just to
search them for a particular text string.

Pete

 

[Karsten Schramm]

Hi,

I'm not sure what you mean. The "Find In Files" command in Visual Studio
doesn't open the files. It just displays the matching lines in each file in
the results window.

Sorry, if I was unclear. I was referring to the VS.NET task list (View
-> Tasklist, filter "Comments"), not to the search function.

Best regards,
Karsten

 

[Chris Nahr]

I don't understand why you think you need to open all code files just to
search them for a particular text string.

He's not talking about "searching" the files. Visual Studio
automatically displays all TODO lines in the task window -- but only
for those source code files that are currently open. Pretty stupid
limitation of the Visual Studio IDE, and there's no way around it.

 

[Guest]

There isnt a way round it. I search in all files and spit the output to the
Find Results 2 window so they arent overwritten by later searches. You can
double click on the lines in the results to jump to the point in the code.

HTH

Ciaran O'Donnell

 

[Karsten Schramm]

Hi,

There isnt a way round it.

I was afraid of that.

I search in all files and spit the output to the
Find Results 2 window so they arent overwritten by later searches. You can
double click on the lines in the results to jump to the point in the code.

Thx

Karsten

 

[Peter Duniho]

Sorry, if I was unclear. I was referring to the VS.NET task list (View
-> Tasklist, filter "Comments"), not to the search function.

I see, thanks.

It does sound like using the "Find In Files" command would be a suitable
workaround though.