I had a few spare minutes today, so I decided to try compiling one of my C# apps under Rotor. (This app is what generates the API quickrefs in books like C# in a Nutshell.)
I tried just typing
make, but I had a call to
MessageBox.Show() that won’t compile under Rotor. When I commented that out (as well as the
using System.Windows.Forms; line), I was amazed that the whole app compiled without a single error, warning, or tongue of flame ejecting from my Macintosh’s Firewire port.
What was even more surprising was that it was able to run without a single error; I asked it to reflect over System.dll, mscorlib.dll, and System.Xml.dll, and it gave me an XML document that I ran through our production tools, giving me this lovely PDF.
So even though Rotor includes only a subset of the .NET Framework Class Library, it’s a pretty useful subset!
|src="http://www.oreilly.com/catalog/covers/sscliess.s.gif" align="right">||Learn more about Rotor in the upcoming Shared Source CLI Essentials (sample chapters are available online).|
Somehow, I managed to write a somewhat complex application that only used the types in the SSCLI. How lucky is that?