Rotor Whidbey here we come..

Joel confirms there will be a Rotor (SSCLI) release for Whidbey… What are you hoping to see with it?  I just noticed that at least one of Eric’s readers uses it as opposed to our product documentation… What do others use it for?  What would you like to use it for if only we’d add xxx?

Published 13 December 03 02:25 by BradA
Filed under:

Comments

# Sam Gentile said on December 13, 2003 7:59 AM:
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.
# Jamie Cansdale said on December 13, 2003 8:43 AM:
What I would really like to see is enough of the runtime hosting API supported for me to do... <configuration> <startup> <supportedRuntime version="SSCLI_v1.2.666" /> </startup> </configuration> 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)
# Sam Gentile said on December 13, 2003 9:26 AM:
Yes to what Jamie said!
# Andrew Stopford said on December 13, 2003 8:08 PM:
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.
# RichB said on December 17, 2003 10:52 AM:
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.
# Juan Felipe Machado said on December 18, 2003 3:19 PM:
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...)
# Bill said on December 18, 2003 3:28 PM:
I find Reflector invaluable in figuring out what is actually going on. The C# decompiler does a pretty good job. http://www.aisto.com/roeder/dotnet/
New Comments to this post are disabled

Search

Go

This Blog

Syndication

Page view tracker