Alpha 3.0 passes my normal QA test for a release however I am adding XHTML compliancy to modules before I make a formal release.  Anyone, however may go download Alpha 3.0 through anon SVN access over at novell.  You will have to grab Jons code [ as it is the latest] from his folder :  Current Directory: rainbow / sandboxes / Jminond / trunks / dev /    I have been doing a lot of studying on the internet and even asked Scott Guthrie on good html to XHTML tips.  He informs us that we are pretty much on our own until someone makes a better tool.  Ive tried tidy but its not really good with ASP.NET eventhough it claims that.  I would love a tool that can just iterate through all my aspx files and make corrections much like tidy sorta does with coldfusion.  Last night, I converted tidy to .NET 2.0 but got limited results of " you have errors here..bailing out" when I tried on some aspx files.  So I did some specific searching for 2.0 and found some good links.

  I am also preparing Rainbow 2.0 for IE 7 and Ive been doing some testing and rainbow fudges in a lot of areas in IE 7 [ thanks ms for more work].  Jon has updated the beta scripts so far so we are working on it ;).

Dont fret, Ive found some cool suggestions that I want to employ into rainbow.  The first is to use VS 2005 to go through each aspx | ascx page [ yes one by one - if you would like to help ramseur@gmail.com] and use the validator to check.  It took me anywhere from 7-20 minutes per module.  [Ive already converted desktopDefault.aspx] Some modules were written by good html authors and dont even need changing.  I am trying to get rainbow XHTML stamp approval from the service so we can use the web service [ in a module] to check your current page for XHTML compliancy which is GREATLY needed for cross browser support and legacy support. 

Second, I have found some links that can force all pages to go through an ASP.NET implementation of a reponse fliter.  The default fliter implementation looks easy and I plan to add this to Jons framework where all pages will go through this filter.  The current method is to put it in every pages page_load but Ill find a better way that you can just turn on|off your modules to use the filter.

 I have also added the file from here that jon suggested that will fix some issues.  Alpha 3.0 will include this file in app_browsers.  There is also a web.config way which I found here.

Here are some links I have found to help me:

http://www.charon.co.uk/content.aspx?CategoryID=28&ArticleID=53
http://www.aspnetresources.com/articles/HttpFilters.aspx

If you have any other suggestions dont hesistate to hit the email as I need all the help I can get doing this pretty much by myself until we get some XHTML devs.  This is a contribution in itself and I would greatly appreciate an XHTML admin to make sure all releases are in accordance with standards.  I also plan to do both level 1 and 2 compliance [ including section 508] that will allow rainbow to be deployed in the Government and other compliant institutions like colleges and hospitals.