>I see your point but that involves updating an "external" document, which I am somewhat moving away from with //TODOs. In the heat of coding you sometimes don't have time to open another file to write verbose text. Sometimes my //TODO comment will simply say:
>

>//TODO: if above looks iffy
>

>If I was maintaining an external document I would have to state what cs file the if was in and around what line and maybe tell a little about why it was iffy.

Sure, it is convenient to have the TODO in the code itself. On the other hand, there are cases where the to-do comment can't be attached to a code element, as in: "To do: create a form [or report] that does such-and-such".

>I suppose I could write a small app to scann all the files in the project and return all //TODOs.

For a quick solution, you can just search through the files. The built-in search in Windows is fubar [1], at least in Windows 98, but you can use the free search tool, Agent Ransack. It has the capability of searching through ALL files, not just those with specific extensions, and it shows a summary of the search results in one of its windows (so you can see the "TODO" text in context).


[1] fubar: fouled up beyond all repair (or recognition)