When in doubt, peek at the ROTOR sources

I often find myself in situations where knowing a .NET class internal implementation would be very helpful.  Will CollectionBase be performant for me? What internal data structure does it use?  Why is my Regex expression so damn slow?  How much overhead is my reflection loop incuring, and why?

When faced with that type of questions, you can often find an answer by peeking into the ROTOR codebase and seeing for yourself how things are implemented.  There is a convenient online index at: http://dotnet.di.unipi.it/Content/sscli/docs/doxygen/fx/bcl/classes.html

Note that ROTOR includes only the framwork and the basic BCL objects – no ASP.NET, ADO.NET, etc.  But it is still a fascinating resource for drilling down into the internals of .NET.

P.S.  It seems that everyone on earth except me and Robert McLaws is at TechEd. So I guess it is up to us to keep the world economy running until everyone returns. No more coffee breaks!

Comments (3)

  1. Anonymous says:

    I use anakrino as a decompiler. Works better than peeking at Rotor, because Rotor is not 1:1 compliant with the .NET installment in the SDK. The rotor source does give some interesting ideas though, especially on attributed programming 🙂

    ps: I’m also not at teched. 🙂

  2. Anonymous says:

    lol Addy. Lets start a TechEd non-attendees blog. We can be just as cool as they are. <chuckles> Man we’re such nerds.

  3. Anonymous says:


    The thing which really gets me is how much my position has changed in the past 6 months. Last year Microsoft Israel flew me over to the TechEd in Eilat where I gave 3 great presentations and chatted with the likes of David Chappel. But since then I moved to the other side of the world (NYC), changed jobs, and basically left behind everyone who knows how good I am 🙂

    Which leaves me here at work – while I rebuild my reputation from scratch everyone else is out having fun at TechEd…