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.

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

>>I don't know about you guys but I like to put in //TODO: as reminders for myself. The only problem I see is that unless I have that particular cs file open the task does not show in the task list tab.
>>Now what I have done so far is open all the cs files and then go looking for TODOs, but I am realizing that the chance of me forgetting to open even just one cs file is greater than 0.
>>
>>Is there a way I can see all my TODOs for the entire project without opening all cs files in the project?
>>
>>Einar
>
>I don't know, but:
>
>Being able to put "todo" comments within the source code itself, and finding them quickly, may be interesting. But it may also help to have a separate document that contains all pending work - which may include notes that are not related to one particular method, and therefore not easy to put within the source code. At Bata, I use Microsoft Word to create a hierarchy of topics, which I can expand and contract. (Just use outline view, and a document that consists only of headers!)