I've spent the last couple of days redesigning an old tables based skin into a CSS skin using the ASCX method.  It works on the local development server.  However, when I package the skin and install it to a staging server, it fails to pick up the skin.css even though the css file is successfully copied.  It's as if DNN itself doesn't see it.  Has anyone else ever had this problem and possible able to point me in the right direction?  When I install the skin package it creates exactly the same directory structure as exists on the dev server.  I can't understand what the difference is.  I'm attaching the package.  Maybe someone can tell me what I've done wrong.

I found that if I were to simply copy the files to directories in the Portals/_default/Skins and Portals/_default/Containers directories, that I could select the skins and containers and that all was just fine.

From that, I conclude that there is something in your manifest file that needs to be changed.  I haven't figured out what it is, though.

My suggestion is that you read this blog entry, and follow Timo's advice.  First, package up your skins and containers in the old style format, and install the skin.  You can then use the tools in DotNetNuke to package the skins and containers in the new format, letting DotNetNuke build the manifest files.

------------
I did that, and was able to install the newly packaged skin correctly.  Oddly, I really cannot see any difference between the manifest file in your skin and the one that DotNetNuke generated for me.  I'm completely baffled.

But, it does work.

Thanks for taking a look. Apparently it didn't like the directory name I had K4GDW.CSS.Skin. I changed it to use underscores instead of dots and installed it on another DNN instance and it worked.

Interesting.