You know, I didn't even think of PageBlaster for this, but it's perfect.  Mostly it seems to get used for search engine friendly URL's, but it can replace anything so it's an easy way to manage this.

Jeff

That's a good start, but it doesn't get us all the way there (see below).

Unfortunately, there's more to it than just changing the DocType.  At least for the 3.x code base, there's a bunch of end tags that are missing.  I think there's also a bad tag in there somewhere.  A missing end quote on something or other.  You need to run through the Default.aspx pretty carefully to be sure you catch everything.

The nice thing is -- once you do it the first time, it's easier with each succesive release.  Just use something like Beyond Compare to find the differences.

Personally, I think XHTML Strict is a pipe-dream.  Not only do you have to worry about the Core producing valid code, but every module has to produce valid code, and every Admin will puts an HTML module on the site as well.

I'll be happy with XHTML Transitional.  The real goal for me is to get every browser to render the web site consistently.  That means getting rid of quirksmode, which the DocType I list above will do.  Then if I can get the site the validate, that's great.

I'm not sure DNN will ever get to Strict.