The next Rotor rev…

I figured I'd write a small, somewhat unofficial post about Rotor V2 (Rotor Whidbey).
For those that missed the PDC this year, there was a Rotor BoF (Birds of Feather)
session in which Brad Abrams talked a little about the next Rotor release. Yes, there
is going to be a Rotor Whidbey that's based on the Whidbey CLR sources. Yes, there
is a team of people dedicated to shipping and supporting Rotor. Yes, the CLR team
owns it.
We're expecting something similar to the Rotor V1 release: a cross platform implementation
of the ECMA CLI standard and the ECMA C# standard (the new generics stuff included).
It is hoped that we ship Rotor some small delta of time after the official Whidbey
product release. What we'll ship is still somewhat loosely defined, but I'll make
sure I keep this blog up to date with the latest.  

Hopefully this is as exciting for you guys as it is for me. With Microsoft investing
so heavily in managed code, it's a perfect opportunity to see ``under the hood'' to
what will be the basis of so many of our products.

If you've ever wondered how the magic happens, you can now just: "use the source Luke"... 
Sorry 😉

Comments (4)

  1. Use the source I will


  2. Roshan James says:


    We were really hoping for one.




    Roshan James

    Microsoft MVP .Net




  3. Peter Evans says:

    Great POST IN Shared Source CLI now I’m going to have to go an try and build it in the morning. 🙂

    I saw some perl scripts in there. You don’t happen to know if they are still perl 5.0? Ah! Never mind I will fiddle with it to see if they work.

    Gosh wish I had seen rotor earlier.

    However, come to think of it I wouldn’t have gotten and intro to Haskell or functional XSLT if I had.

    Oh well the world needs more personal agent software to help us manage our limited input capabilities.

    One can only hope that rss will help make this a tipping point for User Agent Services.

    Loved the pun.

Skip to main content