Rotor Whidbey here we come..

style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> href="">Joel
confirms there will be a href="">Rotor
(SSCLI) release for Whidbey… What are you hoping to see with it? style="mso-spacerun: yes"> I just noticed that at least one of href="">Eric’s
readers uses it as opposed to our product documentation… What do others use it
for?  What would you style="mso-bidi-font-style: normal">like to use it for if only we’d add
xxx? />

Comments (7)

  1. Sam Gentile says:

    As you know already Brad from co-hosting the Rotor BOF with me at PDC I use it everyday for my documentation – thats how I figure out how things work in the CLR. I would like to see it more supported in the sense of hwaving the Rotor folks interact not only with the academic community but with us – the .NET devleopment community. I would like to see design previews, presentations, etc.

  2. What I would really like to see is enough of the runtime hosting API supported for me to do…

    <supportedRuntime version="SSCLI_v1.2.666" />

    This would mean I could prototype code using Rotor, and start porting it to the CLR simply by flipping a switch. I can’t emphasise enough how useful this would be. I’m salivating at the mere thought! ;o)

  3. Sam Gentile says:

    Yes to what Jamie said!

  4. I agree with Sam, more resources, demos etc for the development community would be great. I am currently having trouble sourcing info on Rotor beyond the docs and Rotor book so more info, docs etc would be very welcome.

  5. RichB says:

    I extract portions of ROTOR (eg System.Xml) into a VS.Net .csproj file so I can have source code debugging of a portion of .Net from within my IDE. Perhaps if you ship .msbuild files along with ROTOR, that would be helpful.

  6. I’m with Jamie.
    Also, being an MFC guy I really miss the source code and the debbuging capabilities of VC 6.0 (get into the MFC code..etc) so I use ROTOR to see how things probably work (I’m not very good at IL assembler yet…)

  7. Bill says:

    I find Reflector invaluable in figuring out what is actually going on. The C# decompiler does a pretty good job.