It has been improved in the latest few versions (although I haven't upgraded to the latest latest one). Also, running on a quad core, 64-bit Windows 7 box with 8 GBs of RAM doesn't hurt either! :-D

Know how to protect yourself from this? Use ReSharper! As soon as you type the "Foo.", ReSharper adds "Crash." in front of it and prevents Visual Studio from having fits! ReSharper, best developer tool, EVER! (possibly even better than Visual Studio! ;) )

I Agree with everyone else. Ever since they revamped the layout earlier this year, the easiest way to find something on MSDN is to use Google (and then probably use a non-MSDN link).

-------------- Henry Manager, Software Engineering and Professional Angry Monkey Slayer

We're using PostSharp[^] too. I find it nice to be able to add one line of (attribute) code on top of a method, and have performance counters captured for that method. Open up PerfMon and see how may times my method is being hit. Attributes are a good way to abstract out the "non-method specific" functionality of a method. (I.e. If your method is called GetUser(), it's nice to be able to put performance tracing, error handling, entry/exit validation, etc., all without having to "spaghetti up" the code!) As far as reflection/performance, the good thing about PostSharp[^] is that the overhead is at compile time, not runtime!

-------------- Henry Manager, Software Engineering and Professional Angry Monkey Slayer