Build #236 is still locking out VS2005 on my machine, though now I get 2
to 3 minutes of edits where previously it was often only 1 or 2 edits
with the last two or three builds!
There is no real pattern to the problem, however editing using
statements invariably causes VS2005 to go to 50% processor (which is
effectively 100% of the processor it is running under) and sit there. I
have even left it over night just to see if it ever reaches an "end"
point but to no avail.
I have rebuilt my machine creating the cleanest environment I possibly
can whilst continuing to be able to work but this has made no
As I have to kill the process there is no debug/diagnostic data I can