Yes, theres no difference in the skinning architecture. The only potential impact is the framework itself. If you've tested a skin in 3.2.2 under asp.net 1.1 (it can be ran under 1.1 and 2.0), and then try it in 4.03 then the html emitted by the .net framework will be more xhtml compliant. It's unlikely that ill affect the look of the skin, but you will probably end up with a site that's more standards compliant.

Cathal

Theres no particular support for CSS skins, though there are some areas of the framework that can be changed to better suit CSS e.g.you can change the actions menu from being one that uses postbacks to one using a dropdown list by changing the skin object token from [ACTIONS] to [DROPDONACTIONS]. It's possible to make CSS only skins , take a look at http://www.thinkofdesign.com/Downloads/tabid/54/Default.aspx for some examples. The popular cssskins product is also used by some people to help with their CSS efforts (his site also has a nice free DNN CSS editor you may want to look at as well)

Please note, we will also be taking a look at making a few changes to help make DNN skins more compliant. Some of this may also include changing various TABLE tags to be DIV's which should help this area also.

Cathal