Is there a built in string I can use that will point to the path of the ascx page that the tempalte is executing from?

For instance, if I have a resource on the page element:
<img src="right_overlay.png" border="0 alt="">

then when the page is rendered, this image src will be relative to the page that the skin is loaded on - e.g. /default.aspx, whereas the actual resource called "right_overlay.png" actually exists in the skin folder, in my case:

/Portals/_default/Skins/corporate/right_overlay.png

The only way I've found of referencing this actual file is like this:

<img src="<%=Me.AppRelativeTemplateSourceDirectory.Replace("~/", "/")%>right_overlay.png" border="0 alt="">

Is there a property I can access in the page which gives the actual path to the same folder as the ascx is loading from, or do I just do what I have above?

Also, when I need to reference things within the css file for the skin in the same way (e.g. css behviours), am I able to make the skin.css file actually skin.aspx, so that I can put server-side code in my skin for generating it dynamically? I need to do this because the paths inside the css file are relative to the page that is executing, not to the css file. The only way I seem to able to do that now is having this code in the skin.css file:

@import url(skin.aspx);

and setting the content type to "text/css" inside skin.aspx

SkinPath is the bit I needed.

With my CSS if I put the skin.css file in the folder, I can reference images (for backgrounds etc) that exist in the same folder, using something like:
.myelement {
background-image: url(my_file.png);
}

However, if I use a behaviour on my element I need to put in the whole path to the behaviour.

.myelement {
behaviour: url(mybehaviour.htc);
}

doesn't seem to work, whereas

.myelement {
behaviour: url(/portals/_default/skins/corporate/mybehaviour.htc);
}

does work properly.  So I need a way of specifying the same SkinPath property in the css file.

 

By the way.  The answer to the question about getting the path that the .ascx is in is

Me.TemplateSourceDirectory 

for Skins, this is actually what is being used in the code-behind for the SkinPath property that is exposed, but it works in any .ascx page or .aspx page.

And, just as a general good practice, you don't wan't to inlude imports that are actual .aspx pages because those pages can be executed directly which may pose a risk.

---