Brian Goldfarb links to the list of major changes between beta 2 and RTM. Finally we have directory names put back into namespaces, so two default.aspx files no longer clash.

It's a shame they've felt it necessary to default back to XHTML 1.0 Transitional though. What isn't clear (and of course you can't test yet) is what happens with DTDs. If you have an XHTML 1.1 DTD on your page does the <xhtmlConformance mode="transitional" /> setting in web.config ignore this and cause asp.net to spit out transitional code?

I wonder if we'll see more thought in Visual Studio around using Sql Server as opposed to Sql Express

[22-August] scottgu (yes, that scott) posted a reply to my comment on Brian's blog asking about XHTML 1.1.

You can still get XHTML 1.1 support -- it just isn't on by default (because we found it broke a lot of customers).

To enable it, just add strict mode to your web.config file, and then make sure you use the XHTML 1.1 DTD at the top of your .aspx pages.

Now lets hope we can set a default DTD on a per project basis, so I don't have to cut and paste the right DTD into every page. (And for those that validate, please try my .browser file which enables asp.net to serve XHTML to the w3c validator.)