These were in my "to comment on" list when, well, I stopped caring about commenting on them for a while.
First, a town in Italy with a really bad issue with Seasonal Affective Disorder (and a solution, of sorts): http://news.yahoo.com/s/nm/20061218/od_uk_nm/oukoe_uk_italy_mirror
A note from a senior engineer to others about solving a case where an older version of the Visual Studio locks up:
Visual Studio 6.0 creates two files with extension “opt” and “ncb”. These files keep track of dependencies, what windows were open the last time Visual Studio was open, where breakpoints were set, and so on. From what I’ve seen, these files continue to grow until Visual Studio has problems. Murphy’s Law dictates that the problem will occur after spending an hour or two editing seven or eight modules, whereupon Visual Studio hangs without writing out your changes. If you delete all the “opt” and “ncb” files, the Visual Studio will simply create new ones.
A quote from an IM session:
First, a town in Italy with a really bad issue with Seasonal Affective Disorder (and a solution, of sorts): http://news.yahoo.com/s/nm/20061218/od_uk_nm/oukoe_uk_italy_mirror
A note from a senior engineer to others about solving a case where an older version of the Visual Studio locks up:
Visual Studio 6.0 creates two files with extension “opt” and “ncb”. These files keep track of dependencies, what windows were open the last time Visual Studio was open, where breakpoints were set, and so on. From what I’ve seen, these files continue to grow until Visual Studio has problems. Murphy’s Law dictates that the problem will occur after spending an hour or two editing seven or eight modules, whereupon Visual Studio hangs without writing out your changes. If you delete all the “opt” and “ncb” files, the Visual Studio will simply create new ones.
A quote from an IM session:
This poor window is going to be validating itself very obsessively, though.
Like a bad self-help session for code.
no subject