R# is fantastic. I am hooked, even though I am finding R# 'crashing' quite
often. I wonder if this is related to me having a dual CPU machine? Also, I
just found the web based forums so I should be able to give better feedback
now from my "news-disabled" client site.
I am experiencing quite a lot of R# 'crashes' and it is fantastic,
absolutely fantastic, that they do not bring down the IDE. I am currently
using R# at my client's site, sat behind some big corporate firewall.
Whenever I get an R# bug, your software fails to send the bug report : "the
connection has been dropped" (or similar - I will update with the exact text
next time it occurs).
Is there any way of stopping R# from displaying its memory usage in the
status bar? I find that it is most intrusive when I am cycling compiler
errors (F8 from output window - not a big fan of the task window). When I
move to the next error that is in a new source file, VS places the error
text in the status bar and R# immediately overwrites the useful text with
its memory usage.
I lost all of my shortcuts recently too - found your post to fix them,
I am also experiencing occasions when the IDE locks up for maybe 30 seconds
(it certainly feels that long anyway). Our current project is in its infancy
and very small (3 small C# projects in the solution). I will try to give
better feedback on when this occurs.
Some (invalid) code constructs are causing R# to enter a 'crash' loop.
Unfortunately this last occurred at my client site (with no news access)
before your web mirrored forum was accessible. Again, I will endeavour to
give better feedback if this occurs again.
Still, despite these various glitches (it is EAP after all), I already would
not want to be without this tool.
Keep up the great work