Thread: Custom Skins

When creating a custom skin, what are the naming guidelines.

I don't see any mention of this in the tutorial, other than skin_ID

in other words can I name my skin:
CustomName

or

do I need to name it:
skin_#

or

will this work?
CustomName_#


Really I don't care what it is called I just want to know the implications of creating a custom name before I make a change

I think they all have to be skin_# as the code looks specifically for that structure.

It really depends. There are naming conventions to the skins directories (eg. Skin_1, Skin_2, Skin_45, etc...). Once inside these skin directories, the templates should be named based on what they are for.

For a homepage template, you can name this whatever you want (generally should be an intuitive name, like HomeTemplate.ascx). Then just enter the name of this into the HomeTemplate appconfig parameter.

For the default skin for the rest of the site, this should be named template.ascx.

If you are using template switching, you can name the file whatever you'd like because you have to enter the name of the file into the entity that you are using it for.

If you are using the feature where you skin individual pages, the file can be named whatever you like because you must create specific appconfig parameters and enter the name of that file there.

All of these files should reside within the same skin_# directory that you want to use, where # will interpreted as the skin ID (eg. if the directory was called skin_45 you would enter 45 into the DefaultSkinID appconfig parameter, and you could directly invoke this skin by passing a SkinID=45 query string parameter in any of your URLs.

I am trying to used the skinid in my url but it is not showing the skin i want....

http://www.biasboating.com.au/default.aspx?SkinID=2

and this is the default skin...
http://www.biasboating.com.au/default.aspx


please help

dan