OK - I have a problem.
I hate VB - and I want to change the:
<%@ Control Language="VB" Explicit="true" AutoEventWireup="false" Inherits="DotNetNuke.UI.Skins.Skin" %>
to:
<%@ Control Language="C#" Explicit="true" AutoEventWireup="false" Inherits="DotNetNuke.UI.Skins.Skin" %>

Why cant I do this?

Hmmm, I would think that you could do that. What happens if you do it?

It messes up the skin pretty bad

Are you writing something in the code-behind for your skin or container?

If you change the language here, you may need to change it other places (I don't know where, though!)

What is the motivation for changing? I'm not arguing, but want to understand the context in which you are asking the question.

I want to add a script tag with runat server to make some changes.
I want to use C# - not VB.
I thought DNN changed everything over to C# a while back?

I do have one example of a skin that uses c# in the language tab. Not sure what else may need to be changed, but that skin does work!

DNN is written in c#. Of course, you're still able to use VB or any other .NET language.

Here is at least one tiny reference to using c#: http://stackoverflow.com/questions/...g-tutorial

Not sure why this is messing you up ...

Have you tried it?

Yes. I edited a couple of the skin files in Gravity. I didn't see any changes or problems on a test site.

OK it dosnt like my skinpath.
Does the syntax change for that when you change over to C#?

And if you try to add script tags with runat= server it will not accept the C# code.
It will with VB?

I wouldn't expect the skinpath syntax to change.

As for the script, no idea and I haven't tried that. Have you tried adding a c# code behind page to your skin file?

This probably is a good topic for the skinning and/or developer forums at dnnsoftware.com.