Using Rotor SSCLI to Express Your Ideas

Recently one of the other XML MVPs and I were discussing some of the new XML parsing ideas that have been making the circuit lately, and we were lamenting the fact that we were having a hard time communicating some of our ideas to others, and we aren't even trying to bridge a language barrier.  The XML MVPs have been throwing around a bunch ideas that would require major design changes to the System.Xml namespace.  That isn't something I would expect Microsoft to do without knowing the benefits of those changes, and without access to the System.Xml code and the ability to play with it openly, we would have a hard time expressing our ideas.  Then it hit me, why don't we use the Rotor code?  It was created with the idea of using it as a teaching tool, so why couldn't we use it to help "teach" others about some of our ideas.  Another problem with the different ideas we had was that we couldn't easily determine the ease of use of some of our proposed designs, which is even more important than just making things run faster and better. 

So, I downloaded the Rotor source code, and pulled the System.Xml namespace classes into VS.Net 2K3.  Unfortunately, the way the code was written, you can't just add the source files in the System.Xml directories, and compile the code.  For whatever reason, I had to add the System namespace to several classes, and I couldn't find the static class that the System.Xml classes use to get the error messages out of the resource file.  So I had to write the utility class, and then write a quick project to that would read the resource file and generate all the static members of the utility class.  But now we have the Rotor System.Xml namespace as a complete VS.Net project.  If you want to see how  System.Xml does some of its magic, or if you have some ideas you want to try out, go ahead and download the project.  We added it to the Mvp-Xml project that is hosted on SourceForge, and will use it as our code base, and fork the different ideas off of it.